Find the right workflow with ak:help

Use ak:help when you know what you want to accomplish but do not know which installed Skill or CLI command fits. The Skill discovers the live catalog, filters it to relevant candidates, and gives you a precise route instead of a copied inventory.

Choose ak:help for routing

Use ak:help when

• You want to know which installed Skill fits a task.
• You need a concise explanation of how to use AgentKit.
• You want to confirm whether a named Skill is actually installed.
• You need the current CLI help for a command rather than remembered syntax.

Choose another workflow when

• You already know the Skill and need its actual workflow. Invoke that Skill directly.
• You need architectural advice. Use ak:ask or ak:advise.
• You need an exhaustive published CLI command reference. Use the CLI reference rather than treating help prose as a registry.

Prepare the project and runtime

Before you start:

• Complete Onboarding, and confirm Engineer Kit is installed for the runtime and scope you are using.
• Describe the outcome you want, not only a guessed Skill name.
• Identify whether you need an assistant Skill or an ak CLI command.
• Keep the active project and user Skill scopes available so discovery reflects the current installation.

Run the Skill

/ak:help "I need to compare a proposed migration with the current code, but I do not want implementation yet."

/ak:help "I need to compare a proposed migration with the current code, but I do not want implementation yet."

$ak:help "I need to compare a proposed migration with the current code, but I do not want implementation yet."

The Skill accepts a help request. It has no published mode flag or file output.

Understand what happens during a run

1. The Skill reads the live catalog. It uses the runtime's installed-Skill catalog when one is available.
2. The Skill falls back to scoped discovery. It finds current SKILL.md files in active project and user Skill roots and reads frontmatter for relevant candidates.
3. The Skill narrows the candidates. It summarizes only Skills that fit the requested outcome.
4. The Skill checks availability. It says plainly when a referenced Skill is not installed.
5. The Skill verifies CLI syntax when needed. It reads ak --help or the relevant command help rather than reconstructing a command from prose.
6. The Skill recommends one route. A clear task receives the most specific installed Skill or command that matches it.

Keep discovery current and scoped

The workflow reads catalog metadata and command help. It does not install a Skill, edit the project, run the recommended workflow, publish data, or require an external provider. Discovery should stay within the active project and user Skill roots.

Verify the result

A complete result should give you:

• A short restatement of the requested outcome.
• Only the relevant installed candidates.
• One recommended Skill or CLI command when the task is clear.
• The exact invocation spelling for the active runtime.
• A plain statement when a requested Skill is unavailable.
• Current command help when the request concerns the CLI.

Troubleshoot or continue

Know the current limits

• The result reflects only Skills visible in the current project and user scopes.
• Help routes a task; it does not perform the routed workflow.
• Help prose is not an exhaustive command registry.
• Cursor slash invocation is user-verified evidence, not proof of catalog or chooser parity.
• Stable and beta package the same ak:help workflow.