VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:help

Installed skill help router

Open the AgentKit help index, discover the currently installed skills from runtime catalogs or live SKILL.md frontmatter, and route the user to the most specific workflow.

01

Read request

02

Use live catalog

03

Discover frontmatter

04

Filter candidates

Rule 01

Installed state beats remembered skill lists.

Rule 02

Help should route to the most specific usable skill, not advertise everything.

Rule 03

Command examples come from current command help or relevant SKILL.md metadata.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Read request Determine whether the user asks how to use ak, what skills exist, whether a named skill is installed, or which workflow fits.
  2. 2 Use live catalog Prefer the runtime installed-skill catalog when available.
02

Work

Agent / skill execution

  1. 3 Discover frontmatter If no catalog exists, discover current SKILL.md files from active project and user skill roots, reading frontmatter only for relevant candidates.
  2. 4 Filter candidates Summarize only skills that fit the request instead of dumping the entire registry.
03

Verify

Gate, review, validation

  1. 5 Route specifically When the task is clear, recommend the most specific installed skill and say plainly when a referenced skill is not installed.
  2. 6 Read command help When the user needs syntax, read current ak --help or the relevant command help rather than relying on prose as a registry.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:help [topic|skill|command]

Arguments

[topic|skill|command]

Topic, skill, or command

Optional topic, named skill, or CLI command to route against the currently installed AgentKit catalog. Bare /ak:help opens the help index.

/ak:help which workflow should I run for a bug with unknown root cause?

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Open help index Recommended 
/ak:help
Use when:
The user asks how to use AgentKit or wants a starting point.
Expected:
Opens with the installed AgentKit help context, prefers the live skill catalog, and gives a concise index or next best route without dumping every skill.
Choose a topic 
/ak:help debugging unknown root cause
Use when:
The user names a topic but does not know which installed skill fits.
Expected:
Filters installed candidates to the debugging topic, routes to the most specific investigation skill, and briefly explains the fit from the live catalog.
Check a named skill 
/ak:help docs
Use when:
The user asks whether a named skill exists in the current installation.
Expected:
Uses the runtime catalog or relevant SKILL.md frontmatter, reports whether the docs skill is installed, and says plainly if a referenced skill is missing or shadowed.
Need command syntax 
/ak:help ak skills
Use when:
The user needs an exact CLI command shape rather than a broad skill recommendation.
Expected:
Reads current ak help or the relevant command help before giving syntax, and keeps examples scoped to the installed kit instead of treating prose as a registry.

Handled Scope

  • Installed skill discovery
  • Workflow routing
  • Frontmatter-only candidate lookup
  • Command help summarization

Artifacts Produced

Help answer

Pattern

Relevant installed skills, why they fit, exact command shape only when verified from current help or metadata.

The output is a routing answer, not a static command registry.

Next