--- name: ck-skill-creator description: Create or update Antigravity-format skills. Use for new skills, skill references, skill scripts, optimizing existing skills, and extending capabilities with SKILL.md, references/, and scripts/. --- # Skill Creator (Antigravity Format) Guidance for creating effective skills in Antigravity format. ## When to Use - Creating a new skill from scratch - Updating or optimizing an existing skill - Adding reference files or scripts to a skill - Converting skills from other formats to Antigravity ## Don't Use When - Task is better handled by writing a one-off script (not reused) - Knowledge is project-specific and not reusable across projects ## Antigravity Skill Format ### SKILL.md Structure ``` skills/ └── skill-name/ ├── SKILL.md # Required: frontmatter + instructions ├── references/ # Markdown docs loaded as needed ├── scripts/ # Executable code (Node/Python) └── assets/ # Templates, images, fonts ``` ### Frontmatter Rules (CRITICAL) ```yaml --- name: ck-skill-name # ck- prefix, colons → hyphens description: > # ≥3 trigger phrases, under 200 chars What it does. Use for X, Y, Z. Triggers on A, B, C tasks. --- ``` - **ONLY** `name` and `description` in frontmatter — no version, license, model - Add `ck-` prefix to all skill names - Replace `:` in names with `-` (e.g., `plan:fast` → `ck-plan-fast`) ### SKILL.md Body Rules - Under 200 lines - Must include **"Don't Use When"** section - Description must contain ≥3 trigger phrases - Replace CK tool names (Task tool, AskUserQuestion) with generic prose - Use imperative/verb-first instructions throughout ## Creation Process 1. **Understand the skill** — what tasks trigger it, what knowledge it provides 2. **Write SKILL.md** — frontmatter + core instructions under 200 lines 3. **Add references/** — detailed docs split into <150 line files each 4. **Add scripts/** — reusable executable code with tests 5. **Validate** — check description has ≥3 triggers, "Don't Use When" exists, under 200 lines ## Progressive Disclosure Three-level loading system: 1. **Description** (always in context) — triggers activation 2. **SKILL.md body** (when triggered) — core instructions 3. **references/ and scripts/** (loaded as needed) — detailed knowledge Keep SKILL.md lean. Move detailed examples, schemas, and API docs to `references/`. ## Quality Checklist - [ ] Frontmatter has only `name` + `description` - [ ] Name has `ck-` prefix - [ ] Description ≥3 trigger phrases, under 200 chars - [ ] "Don't Use When" section present - [ ] SKILL.md under 200 lines - [ ] No CK-specific tool names (use generic prose) - [ ] Reference files each under 150 lines - [ ] Scripts have tests and work cross-platform