Skip to content

@tank/skill-creator

2.0.0

Create, evaluate, and improve AI agent skills from books and research. Covers skill anatomy, progressive disclosure, research workflow, writing conventions, evaluation (test cases, grading, iteration), description optimization, quality agents, and validation. Triggers: create skill, new skill, build skill, write skill, update skill, improve skill, evaluate skill, validate skill, SKILL.md, reference file, skill template, domain expertise.


name: "@tank/skill-creator" description: | Create skills that extend AI agent capabilities with synthesized domain expertise. Covers skill anatomy, progressive disclosure, research workflow (books + web), writing conventions, and ecosystem patterns.

Trigger phrases: "create a skill", "new skill", "build a skill", "skill about", "make a skill for", "update skill", "improve skill", "write a skill"

Skill Creator

Transform general-purpose agents into domain specialists by synthesizing knowledge from authoritative books, web research, and reusable resources.

Core Philosophy

  1. Context window is a public good — Agent is already smart. Only add information it lacks. Challenge every paragraph's token cost.
  2. Synthesize, never summarize — Extract frameworks, decision trees, actionable patterns. Never copy verbatim.
  3. Progressive disclosure — SKILL.md under 200 lines. Deep knowledge in references/, deterministic code in scripts/, templates in assets/.
  4. Match freedom to fragility — Text instructions for flexible tasks, pseudocode for preferred patterns, exact scripts for fragile operations.
  5. Understand before building — Collect concrete examples before research. Skills from real examples outperform skills from abstract knowledge.
  6. Save research to disk — Skill creation generates massive context. Save to /tmp/{skill-name}-research/ immediately.
  7. Write your own work — Read existing skills freely to learn what works (structure, length, patterns). But always write your own content from your own research. Never copy-paste text from other skills.
  8. Explain the why — Reasoning beats rigid rules. LLMs understand intent; MUST/NEVER in all caps is a yellow flag. Reframe as reasoning.

Skill Anatomy

skill-name/
├── SKILL.md              # Entry point: frontmatter + workflow + file index
├── skills.json           # Permissions: filesystem, network, subprocess
├── references/           # Docs loaded on demand (250-450 lines each)
├── scripts/              # Executable code for deterministic tasks
└── assets/               # Templates, images (not loaded into context)

Quick-Start: Common Problems

"Skill doesn't activate"

  1. Check description field — must include trigger phrases + scenarios
  2. Add 10-15 trigger phrases covering user phrasings
  3. Include specific file types, tools, tasks in description
  4. The body loads AFTER triggering — "When to Use" sections are wasted
  5. Make description slightly "pushy" — Claude tends to under-trigger
  6. Test with references/evaluation-workflow.md trigger eval queries

"Agent gives generic advice"

  1. Reference files need more specific, actionable content
  2. Add decision trees, frameworks, concrete tables
  3. Replace prose with step-by-step procedures
  4. Verify agent is loading the right reference file

"Reference files wrong length"

  1. Target 250-450 lines per file
  2. Split large files, merge small ones
  3. Each file covers distinct subtopic — no overlap

Workflow

Phase 1: Scope and Research

  1. Define scope — Ask: domain, tasks, triggers, style reference
  2. Study ecosystem — Browse skills.sh leaderboard. Read top skills to learn what works — structure, triggers, file layout. Use them as inspiration but write everything yourself from your own research.
    • anthropics/skills (frontend-design, skill-creator)
    • vercel-labs/agent-skills (react, web-design)
    • obra/superpowers (debugging, tdd, planning)
  3. Collect examples — Concrete queries skill should handle
  4. Research books — 6-10 authoritative books (2018+)
  5. Acquire books — Purchase or access through library/publisher
  6. Extract frameworks — Use look_at on books. Save to /tmp/
  7. Quality gate — 4+ books extracted before Phase 2

Phase 2: Plan Structure

  1. Plan reference files — 5-9 files, each from 2+ books
  2. Analyze resource types — Script vs reference vs asset

Phase 3: Write Content

  1. Write reference files — Parallel agents, books as primary source
  2. Verify — Format, length, sources, no overlap

Phase 3.5: Evaluate & Iterate

  1. Create test cases — 3-5 realistic prompts + assertions
  2. Run with/without skill — Baseline comparison via delegation
  3. Grade results — Use references/quality-agents.md grader
  4. Human review — Get feedback on output quality
  5. Improve and repeat — Fix issues, rerun until satisfied
  6. Optimize description — Test trigger accuracy with eval queries
  7. Validate — Run scripts/quick_validate.py

See references/evaluation-workflow.md for detailed procedures.

Phase 4: Deploy

  1. Write SKILL.md — Under 200 lines
  2. Create skills.json — Minimal permissions
  3. Git commit and push

See references/research-workflow.md for detailed procedures.

Decision Trees

Resource Type Selection

ContentTypeLoaded?
Domain knowledge, frameworksreferences/Yes, on demand
Deterministic code, automationscripts/No, executed
Templates, images, boilerplateassets/No, output
Core workflow, triggersSKILL.mdYes, on activate

SKILL.md Structure

Skill TypePatternExample
Sequential processesWorkflow-basedEditor: Create → Edit → Export
Multiple operationsTask-basedPDF: Merge, Split, Extract
Standards/rulesGuidelinesBrand: Colors, Typography, Voice
Interrelated featuresCapabilitiesPM: Context, Updates, Comms

Instruction Freedom Level

SignalFreedomFormat
Multiple valid approachesHighText instructions
Preferred pattern + variationMediumPseudocode
Fragile operation, exact sequenceLowSpecific script

Tank-Skill Patterns

Observed in 20 skills:

PatternLinesExample Skills
Best practices47-115react, typescript, python, clean-code
Methodology143-291systematic-debugging, planning, tdd
Operational137-382playwright, security-review, gmail
Integration100-250notion, slack, google-calendar

skills.json Permissions

{
  "network": [],
  "filesystem": {
    "read": ["**/*"],
    "write": []
  },
  "subprocess": false
}

Only add permissions when actually needed.

Reference Files

FileContents
references/skill-design-patterns.mdContext window principle, degrees of freedom, progressive disclosure, resource types, SKILL.md patterns, what NOT to include
references/research-workflow.mdScope definition, ecosystem study, book research, framework extraction, scratch file protocol, parallel writing delegation
references/writing-conventions.mdFrontmatter rules, body structure, reference file format, quality standards, instruction philosophy, completion checklist
references/ecosystem-patterns.mdskills.sh leaderboard analysis, top publisher patterns, tank-skills conventions, supported agents
references/evaluation-workflow.mdTest case creation, grading, iteration loop, description optimization, evaluation schemas
references/quality-agents.mdGrader and blind comparator agent prompts, delegation templates, output schemas

Command Palette

Search skills, docs, and navigate Tank