skill-writer
Skill Writer
Create and optimize Claude Skills following best practices and validation rules.
Core Principles
- Context is scarce — Claude is already smart. Only add what it doesn't know. Challenge each paragraph: "Does this justify its token cost?"
- Description is the trigger — Description determines WHEN a skill loads. It MUST describe triggering conditions, NEVER summarize workflow.
- Progressive disclosure — Three-level loading: metadata (~100 tokens, always loaded) → SKILL.md body (<5000 tokens, on trigger) → references/scripts/assets (on demand, unlimited).
- English-first — Write descriptions in English for reliable LLM matching. Body can be bilingual.
- Directive-style — Use
MUST,NEVER,CRITICAL RULEfor hard constraints (not just "should" or "try to"). - No duplication — Information lives in EITHER SKILL.md or references, never both. Keep core workflow in SKILL.md; move detailed reference material out.
Skill Types
| Type | Purpose | Naming Convention | Example |
|---|---|---|---|
| Reference | API docs, CLI guides, tool documentation | <tool>-cli-guide, <lib>-sdk |
argocd-cli-guide |
| Pattern | Reusable code patterns and architecture | <name>-pattern |
zustand-mutative-pattern |
More from wenerme/ai
glab-cli
Use when interacting with GitLab via the glab CLI: creating/reviewing merge requests, managing issues, monitoring CI/CD pipelines, making API calls, or performing any GitLab operation from the terminal. Triggers on glab, gitlab cli, merge request, MR create, pipeline status, ci lint.
34mikro-orm-v6-to-v7
Use when upgrading @mikro-orm packages from v6 to v7, fixing v7 runtime/type errors (decorator SyntaxError, persistAndFlush removed, nativeInsert not found), adapting knex to kysely or better-sqlite to new SQLite drivers, running MikroORM in Edge/Bun/node:sqlite environments, or choosing between defineEntity vs decorator entity definitions. Triggers on "mikro-orm v7", "persistAndFlush", "@mikro-orm/decorators", "@mikro-orm/sql", "defineEntity", "bun:sqlite mikro-orm".
31orpc-implementation-sops
Use when building, updating, or refactoring oRPC contracts, server handlers, clients, or React Query integration
30zustand-mutative-pattern
Use when implementing React state management with Zustand, including context-scoped stores, mutative updates, or actions namespace patterns
25tmux-session-manager
Use when executing commands, running builds, starting services, or monitoring logs in a visible tmux pane
25wode-db-schema-pattern
Use when designing, creating, or modifying PostgreSQL table schemas in the Wode project, including ID strategy, multi-tenant isolation, or naming conventions
24