Fix branch naming and simplify frontmatter example

- Change `feat/` to `feature/` to match repo conventions
- Simplify SKILL.md frontmatter example to show only required fields
- Add note about optional license and metadata fields

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Corey Haines
2026-01-26 17:32:09 -08:00
parent f98eded89c
commit 07744d9d37
2 changed files with 4 additions and 6 deletions

View File

@@ -132,7 +132,7 @@ See [Claude Code plugins documentation](https://code.claude.com/docs/en/plugins.
### Branch Naming ### Branch Naming
- New skills: `feat/skill-name` - New skills: `feature/skill-name`
- Improvements: `fix/skill-name-description` - Improvements: `fix/skill-name-description`
- Documentation: `docs/description` - Documentation: `docs/description`

View File

@@ -22,10 +22,6 @@ Every skill needs a `SKILL.md` file with YAML frontmatter:
--- ---
name: your-skill-name name: your-skill-name
description: When to use this skill. Include trigger phrases and keywords that help agents identify relevant tasks. description: When to use this skill. Include trigger phrases and keywords that help agents identify relevant tasks.
license: MIT
metadata:
author: "[Your Name](https://your-website.com)"
version: "1.0.0"
--- ---
# Your Skill Name # Your Skill Name
@@ -33,6 +29,8 @@ metadata:
Instructions for the agent go here... Instructions for the agent go here...
``` ```
Optional frontmatter fields: `license` (default: MIT), `metadata` (author, version, etc.)
### 3. Follow the naming conventions ### 3. Follow the naming conventions
- **Directory name**: lowercase, hyphens only (e.g., `email-sequence`) - **Directory name**: lowercase, hyphens only (e.g., `email-sequence`)
@@ -70,7 +68,7 @@ skills/your-skill-name/
## Submitting Your Contribution ## Submitting Your Contribution
1. Fork the repository 1. Fork the repository
2. Create a feature branch (`git checkout -b feat/new-skill-name`) 2. Create a feature branch (`git checkout -b feature/new-skill-name`)
3. Make your changes 3. Make your changes
4. Test locally with an AI agent 4. Test locally with an AI agent
5. Submit a pull request using the appropriate template: 5. Submit a pull request using the appropriate template: