Skill Creator
Help create Claude Code Skills that comply with Testany's specifications.
Testany Skill Specifications (Mandatory)
Naming and Structure Conventions
| Item | Specification |
|---|
| Naming Language | English, kebab-case (e.g., ) |
| Directory Structure | Flat structure |
| Required Files | Only SKILL.md |
| references Naming | English |
Review Standards
| Review Item | Requirement |
|---|
| Frontmatter | Must include trigger phrases |
| Line Limit | SKILL.md < 500 lines |
| Boundary Check | Must pass + manual review |
| Language | Must be Chinese (technical terms can remain in English) |
| Examples | Must include usage examples |
Directory Structure
skill-name/
├── SKILL.md (Required)
└── references/ (Optional, reference documents loaded on demand)
Do not create extra files like README.md, CHANGELOG.md, etc.
Core Principles
Simplicity First
Context window is a shared resource. Only add information that Claude doesn't know.
Default Assumption: Claude is already smart. Use concise examples instead of lengthy explanations.
Progressive Loading
- Metadata (name + description) - Always in context
- SKILL.md body - Loaded after triggering
- references/ - Loaded on demand
Skill Creation Process
Step 1: Understand Requirements
Understand the skill's usage scenarios through specific examples:
- What functions should this skill support?
- How will users use it?
- What phrases will trigger this skill?
Step 2: Plan Content
Analyze each example to identify required resources:
| Resource Type | Purpose | Example |
|---|
| references/ | Reference documents, loaded on demand | Templates, specifications, API documents |
| scripts/ | Executable scripts | Validation, initialization tools |
| assets/ | Output resources | Images, template files |
Step 3: Initialize Skill
bash
scripts/init_skill.py <skill-name>
The script outputs to the
directory by default and creates:
- SKILL.md template
- Example directory structure (scripts/, references/, assets/)
Step 4: Write SKILL.md
Frontmatter (Required)
yaml
---
name: skill-name
description: Trigger phrase 1, Trigger phrase 2. Function description, explain when to use this skill.
---
Important: The description must include trigger phrases, which are key to activating the skill.
Body
- Write in Chinese
- Concise and clear, < 500 lines
- Include usage examples
- Explain when to read references when citing them
Step 5: Validation
bash
scripts/quick_validate.py skills/<skill-name>
Check items:
- Frontmatter format
- Line limit
- Presence of trigger phrases
Step 6: Manual Review
After passing validation, submit for manual review:
- Functional completeness
- Document clarity
- Example validity
Reference Example: prd-writer
is an example of a skill that complies with Testany's specifications:
prd-writer/
├── SKILL.md (233 lines)
└── references/
├── new-feature-ui.md
├── new-feature-backend.md
├── integration.md
├── refactoring.md
└── optimization.md
Frontmatter Example:
yaml
---
name: prd-writer
description: Write PRD, write product requirement document, PRD template, new feature requirements. Help write high-quality product requirement documents, supporting multiple types: new features (with/without UI), third-party integration, function refactoring, performance/security optimization.
---
Note the trigger phrases at the start of the description:
Write PRD, write product requirement document, PRD template, new feature requirements
Frequently Asked Questions
Q: What's the difference between references and assets?
- references/: Documents for Claude to reference, loaded into context
- assets/: Output resources (images, templates), not loaded into context
Q: What if SKILL.md is too long?
Split content into references/, and cite and explain when to read them in SKILL.md.
Q: How to test a skill?
- Run to verify format
- Test functions through actual usage
- Iterate and improve based on feedback