Chengeng Super Insurer

Problem to solve

Insurance-growth skills are often split into positioning, persona, content, sales, service, and review. A user may not know which one to start with, may restate context, or may be pushed through a long fixed chain. This entry solves task routing: it detects the current mode, selects one main skill, and hands over materials without doing deep diagnosis.

How it works

It prioritizes explicit skill names first. For first use, it reads onboarding.md and gives a short explanation. If previous results exist, it enters post-task navigation. If the user wants the full system, it delegates to Chengeng Growth System. For a concrete problem without a named skill, it uses pre-task routing.

It reads pre-task-routing.md and skill-catalog.md, identifies the current action, and matches it to positioning, persona, content, sales, service, review, or system tools. It gives a conclusion when evidence is sufficient, and asks only one clarifying question when a fork changes the main skill.

When the runtime supports skill-to-skill calls, it passes the current context directly. Otherwise, it outputs the target skill name, original user request, confirmed facts, open items, desired output, and professional boundaries. Pre-output checks verify that only one main skill is selected, the target skill exists, context is reused, and overly long chains are avoided.

Boundaries

It is an entry router, not a replacement for single-skill diagnosis, final drafts, underwriting, claims, medical, legal, or revenue promises. If the live catalog has no matching skill, it should say so instead of forcing a match. Incomplete input can still start, but low-confidence judgments should be marked.