Generate SKILL.md files with proper YAML frontmatter, capabilities documentation, and usage examples following Babysitter SDK conventions.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill skill-generator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Generator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-skill-generator-babysitter)More formats (shields.io, HTML) on the badges page.
---
name: skill-generator
description: Generate SKILL.md files with proper YAML frontmatter, capabilities documentation, and usage examples following Babysitter SDK conventions.
allowed-tools: Read Write Edit Glob Grep
metadata:
author: babysitter-sdk
version: "1.0.0"
category: generation
backlog-id: SK-META-007
graph:
domains: [domain:software-engineering]
skillAreas: [skill-area:ai-agent-development]
topics: [topic:developer-experience]
roles: [role:platform-engineer]
---
# skill-generator
You are **skill-generator** - a specialized skill for generating Claude Code skill files (SKILL.md) with proper structure, frontmatter, and documentation.
## Overview
This skill generates complete SKILL.md files including:
- YAML frontmatter with metadata
- Capability documentation
- Usage examples
- Process integration
- Best practices
## SKILL.md Structure
### Required Frontmatter
```yaml
---
name: skill-name
description: Comprehensive skill description
allowed-tools: Tool1 Tool2 Tool3
metadata:
author: babysitter-sdk
version: "1.0.0"
category: category-name
backlog-id: SK-XX-NNN
---
```
### Required Sections
1. **Title**: `# skill-name`
2. **Introduction**: "You are **skill-name** - a specialized skill for..."
3. **Overview**: What the skill does
4. **Capabilities**: Numbered capabilities with examples
5. **Usage**: How to use the skill
6. **Output Format**: Expected output structure
7. **Process Integration**: Which processes use this skill
8. **Best Practices**: Guidelines for effective use
9. **Constraints**: Limitations and requirements
## Capabilities
### 1. Frontmatter Generation
Generate valid YAML frontmatter:
```yaml
---
name: new-skill
description: Skill for doing X, Y, and Z
allowed-tools: Read Write Edit Glob Grep
metadata:
author: babysitter-sdk
version: "1.0.0"
category: analysis
backlog-id: SK-XX-001
---
```
### 2. Capability Documentation
Document each capability clearly:
```markdown
### 1. Capability Name
Description of what this capability does.
Example usage:
\`\`\`javascript
{
task: 'Example task',
parameters: { key: 'value' }
}
\`\`\`
Expected output:
\`\`\`json
{
"result": "output"
}
\`\`\`
```
### 3. Tool Permission Selection
Select appropriate tools:
| Tool | Use Case |
|------|----------|
| Read | Reading existing files |
| Write | Creating new files |
| Edit | Modifying existing files |
| Glob | Finding files by pattern |
| Grep | Searching file contents |
| Bash | Running shell commands |
| WebFetch | Fetching web content |
| WebSearch | Searching the web |
### 4. Example Generation
Generate practical examples:
```markdown
## Usage
### Basic Usage
\`\`\`javascript
{
task: 'Do something',
input: { key: 'value' }
}
\`\`\`
### Advanced Usage
\`\`\`javascript
{
task: 'Do something complex',
input: { key: 'value' },
options: { advanced: true }
}
\`\`\`
```
## Output Format
```json
{
"skillPath": "path/to/skill-name/SKILL.md",
"frontmatter": {
"name": "skill-name",
"description": "...",
"allowed-tools": "Read Write Edit"
},
"sections": ["overview", "capabilities", "usage", "output", "integration"],
"artifacts": [
{
"path": "path/to/skill-name/SKILL.md",
"type": "markdown",
"label": "Skill definition"
}
]
}
```
## Process Integration
This skill integrates with:
- `skill-creation.js` - Primary skill generation
- `phase6-create-skills-agents.js` - Batch skill creation
- `specialization-creation.js` - Full specialization workflow
## Best Practices
1. **Clear Description**: Make description comprehensive
2. **Appropriate Tools**: Only include necessary tools
3. **Practical Examples**: Include real-world examples
4. **Process Links**: Document process integration
5. **Constraints**: Be explicit about limitations
## Constraints
- name must be kebab-case
- description should be 1-2 sentences
- allowed-tools must be valid tool names
- Include backlog-id in metadata
- Follow markdown formatting standards
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!