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:
@@ -22,10 +22,6 @@ Every skill needs a `SKILL.md` file with YAML frontmatter:
|
||||
---
|
||||
name: your-skill-name
|
||||
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
|
||||
@@ -33,6 +29,8 @@ metadata:
|
||||
Instructions for the agent go here...
|
||||
```
|
||||
|
||||
Optional frontmatter fields: `license` (default: MIT), `metadata` (author, version, etc.)
|
||||
|
||||
### 3. Follow the naming conventions
|
||||
|
||||
- **Directory name**: lowercase, hyphens only (e.g., `email-sequence`)
|
||||
@@ -70,7 +68,7 @@ skills/your-skill-name/
|
||||
## Submitting Your Contribution
|
||||
|
||||
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
|
||||
4. Test locally with an AI agent
|
||||
5. Submit a pull request using the appropriate template:
|
||||
|
||||
Reference in New Issue
Block a user