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

Marketing Kit

Beta only

/ak:skill-creator

Skill Creator

Creates or updates Claude skills through intent capture, research, progressive-disclosure planning, scaffolding, SKILL.md/resources, evals, description optimization, packaging, and optional Kongming advice.

01

Capture intent

02

Research patterns

03

Plan resources

04

Initialize structure

Rule 01

Skills are practical instructions, not documentation

Rule 02

Metadata triggers first; details load progressively

Rule 03

Validation and evals drive iteration

Rule 04

Keep SKILL.md below 300 lines and references focused

Execution Map

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

01

Start

Input, scope, route

  1. 1 Capture intent Use human-in-the-loop clarification to define what the skill does, when it should trigger, and what it should output.
  2. 2 Research patterns Use docs-seeker and research guidance to ground skill best practices before drafting.
  3. 3 Plan resources Choose which instructions stay in SKILL.md and which details belong in scripts, references, agents, or assets.
02

Work

Agent / skill execution

  1. 4 Initialize structure Create the skill folder with required SKILL.md and optional scripts, references, agents, and assets.
  2. 5 Write instructions Keep instructions imperative, concise, pushy in metadata, and free of duplicated material across references.
  3. 6 Test and evaluate Run validation and evals, then compare baseline behavior with and without the skill.
03

Verify

Gate, review, validation

  1. 7 Optimize description Refine pushy metadata, standard terminology, examples, and scope language for trigger accuracy and benchmark scoring.
  2. 8 Package Validate metadata, token use, script dependencies, structure, portability, and marketplace readiness before producing a zip.
  3. 9 Iterate from feedback Generalize from failures or user feedback instead of adding one-off workaround instructions.

Syntax, arguments, subcommands

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

Syntax

/ak:skill-creator [skill-name or description] [--advice]

Arguments

[skill-name or description]

Skill name or description

Names the Skill to create or update, or describes the repeatable workflow that should become a Skill. Include scope, triggers, expected output, and non-goals when known.

/ak:skill-creator "Create a project-scoped release-notes Skill that validates headings and never publishes"

Shared options

--advice

Advisory supervision

Requests Kongming advisory review after planning, after the SKILL.md draft and evaluation results, before packaging or distribution, or when repeated failures block progress. It does not transfer decisions or bypass validation and security checks.

/ak:skill-creator "Create a project-scoped release-notes Skill that validates headings and never publishes" --advice

Sample Prompt

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

Create a project skill Recommended 
/ak:skill-creator project-scoped release notes skill
Use when:
A repeatable workflow should become a versioned Claude Skill in the current project.
Expected:
Captures tasks, triggers, outputs, scope, refusal behavior, and test cases; scaffolds the project skill directory, writes concise SKILL.md/resources, validates structure, and packages only when requested.
Refine trigger accuracy 
/ak:skill-creator improve the deployment skill description
Use when:
An existing skill undertriggers, overtriggers, or has vague discovery metadata.
Expected:
Audits when-to-use language, sharpens pushy description wording, adds clear use and non-use boundaries, preserves progressive disclosure, and checks eval coverage against the intended trigger contexts.
Add packaging readiness 
/ak:skill-creator package the data-cleaning skill for Claude Code distribution
Use when:
A skill needs validation evidence and a reviewable distribution zip.
Expected:
Runs the bundled quick validator, reviews metadata, token use, script dependencies, structure, portability, placeholder files, and output destination before producing or replacing any distribution archive.
Advised authoring 
/ak:skill-creator browser automation skill --advice
Use when:
The skill design, eval results, packaging step, or distribution target needs advisory supervision.
Expected:
Adds advisory-only Kongming checkpoints after intent capture and planning, after the SKILL.md draft and eval results, before packaging or distribution, and when repeated failures block progress.

Handled Scope

  • skill anatomy
  • progressive disclosure
  • eval design
  • metadata optimization
  • packaging
  • marketplace portability

Next