Agent skill
skill-quality-standards
When creating or validating skills. Reference for SKILL-CREATOR and SKILL-VALIDATOR.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/skill-quality-standards
SKILL.md
When to Use
When creating or validating skills. Reference for SKILL-CREATOR and SKILL-VALIDATOR.
Patterns
Size Limits
Target: 400-1000 tokens (optimal)
Maximum: 1500 tokens (hard limit)
Per task: max 3 skills loaded
Estimation:
1 word ≈ 1.3 tokens
1 code line ≈ 10 tokens
Full skill ≈ 100-150 lines
Confidence Levels
HIGH:
- 2+ authoritative sources (Tier 1-2)
- Patterns tested in production
- Official docs cited
MEDIUM:
- 1 authoritative source
- Community-validated patterns
- Reputable tech blog
LOW:
- Blog posts only
- Experimental/unverified
- No official source
Required Sections
---
[YAML frontmatter with metadata]
sources:
- [URL or internal path]
---
## When to Use
[1-2 sentences - clear trigger]
## Patterns
[2-3 patterns with code examples]
[Each with source citation]
## Anti-Patterns
[What NOT to do + why]
## Verification Checklist
[Actionable checks]
Skill Types
Generic: .claude/skills/generic/
Tech-agnostic, reusable anywhere
Domain: .claude/skills/domain/
Industry-specific (fintech, healthcare)
Project: .claude/skills/project/
Repo-specific patterns
Anti-Patterns
- Skills over 1500 tokens (split them)
- Patterns without source links in frontmatter
- Vague "When to Use" triggers
- Theory without code examples
- Missing anti-patterns section
Verification Checklist
- Under 1500 tokens
- Every pattern has source in frontmatter
- "When to Use" is specific
- 2+ patterns with code
- Anti-patterns included
- Checklist is actionable
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?