common-skill-creator
Tool for auditing and creating high-quality agent skills.
Install
mkdir -p .claude/skills/common-skill-creator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12740" && unzip -o skill.zip -d .claude/skills/common-skill-creator && rm skill.zipInstalls to .claude/skills/common-skill-creator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf). Ensures skills achieve high Activation (specificity/completeness) and Implementation (conciseness/actionability) scores. Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce redundancy and maximize token ROI.Key capabilities
- →Draft SKILL.md using a template
- →Test skills with parallel subagents
- →Evaluate skill performance and token usage
- →Optimize skill description for trigger accuracy
- →Audit existing skills against quality checklist
- →Improve SKILL.md by fixing violations and compressing content
How it works
This skill provides a structured workflow for creating and refining agent skills, focusing on specificity, conciseness, and test-driven evaluation.
Inputs & outputs
When to use common-skill-creator
- →Optimizing a new skill
- →Auditing skill trigger accuracy
- →Refactoring existing skill documentation
About this skill
Agent Skill Creator Standard
Priority: P0 (CRITICAL)
Applies to every skill in this registry. Maximize Token ROI. Every line in SKILL.md must provide specific procedural value. Activation (how it triggers) and Implementation (how it helps) primary quality metrics.
Three-Level Loading System
- Level 1 Frontmatter:
name+description(Activation Anchor), ≤100 words. - Level 2 SKILL.md body: Core Rules + Workflows (Implementation Core), ≤100 lines.
- Level 3 references/: Detailed examples, schemas, and "TESTS.md" (On-demand).
Workflow (New or Existing Skill)
New skill:
- Research — web-search domain best practices, checklists, and standards; extract key terms → triggers, workflows → guidelines, mistakes → anti-patterns. See Web Search Research.
- Capture intent — what it , when it trigger, expected output format?
- Draft the SKILL.md — draft using TEMPLATE.md
- Test — spawn parallel subagents: one with-skill, one without-skill (baseline)
- Evaluate — grade assertions, review benchmark (pass rate, tokens, time)
- Iterate — rewrite based on feedback, rerun into next iteration dir, repeat
- Optimize description — run trigger eval queries, target ≥90% accuracy (matching release readiness)
- Pressure-test — for discipline skills, capture agent excuses, red flags, and stop conditions Existing skill:
- Audit — run Quality Checklist below; identify violations
- Snapshot —
cp -r <skill-dir> <workspace>/skill-snapshot/before any edits - Improve SKILL.md — fix violations, compress, move oversized content to
references/ - Test — spawn parallel subagents: one with-new-skill, one with-snapshot (baseline)
- Evaluate & iterate — same as steps 4–5 above
- Optimize description — re-run trigger eval if description changed
- Harden — add rationalization counters where agents still fail under pressure See Eval Workflow for full testing + iteration details.
Description Quality (Activation)
- Third-Person Voice: Use
Standardizes...,Audits...,Encrypts.... Avoid "I will" or "This skill helps to". - What + When Structure:
- What: Define 5–8 specific capabilities (e.g., "Generates JWT tokens, rotates keys").
- When: Explicitly define triggers (e.g., "Use when user says 'rotate keys'").
- Specificity: Avoid vague verbs like "manage" or "handle". Use "Validate", "Inject", "Refactor", "Sanitize".
- Trigger Hint: Include
(triggers: *.ext, keyword)suffix for technical skills.
Content Quality (Implementation)
- No Redundant Knowledge: Do NOT explain concepts AI already knows (e.g., standard HTTP codes, common language syntax, basic SOLID definitions). Focus strictly on project-specific rules and constraints.
- Readable Compact Style: Size is an editorial budget, not a behavioral quality claim. Prefer readable, compact, imperative language over filler words, conversational phrasing, or speculative prose.
- Actionability: Examples must be copy-paste ready and executable.
- Workflow Clarity: Use sequential ordered lists for multi-step processes.
- Progressive Disclosure: Move code blocks >10 lines to
references/. - Pressure Hardening: Discipline skills must name red flags, common excuses, and exact stop/restart conditions.
Evidence Tiers & Guardrails
- Three Evidence Tiers: Distinguish (1) structural checks, (2) textual transcript evidence, and (3) executable outcomes.
- Oracle & Pressure Hardening: Pressure
behavior_assertionsare positive contains/token checks, not semantic safety guarantees. Regular typed assertions + finite decision-shape controls must reject keyword-stuffed refusal-plus-violation answers; do not claim keyword presence alone establishes compliance. Oracles must test valid paraphrases, quoted unsafe text in refusals, keyword stuffing, partial compliance, and routing negatives; never encode a decision as a bare substring ban on wording a compliant refusal may quote. - Digest Binding & Thresholds: Bind scorer, evals, and generated metadata digests to candidate checkout; no engine-mismatch waiver. Target ≥90% trigger rate (recall & specificity per
readiness.ts). Retain host guardrails until verified deterministic runtime enforcement replaces them. - Discovery & Publication Preflight: Distinguish search failure/checkout absence from absent capability (search authorized refs/worktrees first). When publishing registry or native export packages, verify final canonical→host ID-set and resource parity and real consumer discovery; review private paths/links and one-way manifests; separate warnings/skips/NOT RUN. Keep publication separate from activation.
Anti-Patterns
- No "AI-splaining": Do not explain why a pattern is good unless it is a unique project constraint.
- No Answer-Anchor Padding: Do not insert arbitrary keywords solely to satisfy string-match tests or fake compliance.
- No Search-Absence Conflation: Do not assume missing local search = absent capability; search authorized refs/worktrees.
- No Vague Triggers: Never use
src/**or**/*. Keep triggers surgical. - No Description Bloat: If description exceeds 100 words, move capabilities to body.
- No Long Code Blocks: Blocks >10 lines must be extracted to
references/. - No Untested Guardrails: Rules not validated against baseline failure are unverified speculation.
Quality Checklist (Tessl-Aligned)
- Activation ≥ 90%: Description covers capabilities ("What") and triggers ("When").
- Implementation ≥ 90%: No general-purpose explanations; all examples executable.
- Structural Compliance: SKILL.md ≤ 100 lines; code blocks moved to
references/. - Trigger rate ≥90% on should-trigger queries (recall and specificity per readiness gate).
- Guardrail skills include rationalizations, red flags, behavior eval fields, and should/should-not trigger cases.
References
- Skill Template — load when starting new skill from scratch
- Anti-Patterns Detail — load when fixing or reviewing anti-pattern format
- Size & Limits — load when SKILL.md approaches 100 lines
- Resource Organization — load when deciding where to place content (scripts/, references/, assets/)
- Testing & Trigger Rate — load when writing evals or measuring trigger rate
- Eval Workflow — load when running parallel subagent tests
- Full Lifecycle — load for complete phase-by-phase creation guide
- Web Search Research — load when creating skill for unfamiliar or non-engineering domain
When not to use it
- →When explaining concepts the AI already knows
- →When using vague verbs like 'manage' or 'handle'
- →When using vague triggers like 'src/**' or '**/*'
Limitations
- →Does not explain concepts AI already knows
- →Does not permit vague verbs in descriptions
- →Does not permit vague trigger patterns
How it compares
This workflow uses a standardized, iterative process with parallel testing and specific quality metrics to ensure high-density and actionable skills, unlike ad-hoc skill creation.
Compared to similar skills
common-skill-creator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| common-skill-creator (this skill) | 0 | 4mo | No flags | Intermediate |
| prompt-optimize | 13 | 1y | No flags | Advanced |
| ai-cost-optimizer | 9 | 8mo | Caution | Intermediate |
| self-improving-agent | 12 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by HoangNguyen0403
View all by HoangNguyen0403 →You might also like
prompt-optimize
YYH211
Expert prompt engineering skill that transforms Claude into "Alpha-Prompt" - a master prompt engineer who collaboratively crafts high-quality prompts through flexible dialogue. Activates when user asks to "optimize prompt", "improve system instruction", "enhance AI instruction", or mentions prompt engineering tasks.
ai-cost-optimizer
ScientiaCapital
Save 40-70% on AI costs with intelligent multi-LLM routing. Automatically selects the optimal model based on task complexity across 40+ models from 8 providers.
self-improving-agent
alirezarezvani
Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to enforced rules, (3) turning a debugging solution into a skill, (4) checking memory health and capacity.
ccs-delegation
kaitranntt
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
skill-from-notebook
GBSOSS
Extract methodologies from documents or examples to create executable skills
prompt-factory
alirezarezvani
World-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.