Files

Corey Haines 07744d9d37 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>

2026-01-26 17:32:09 -08:00

2.5 KiB

Raw Blame History

Contributing

Thanks for your interest in contributing to Marketing Skills! This guide will help you add new skills or improve existing ones.

Requesting a Skill

You can also suggest new skills by opening a skill request.

Adding a New Skill

1. Create the skill directory

mkdir -p skills/your-skill-name

2. Create the SKILL.md file

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.
---

# Your Skill Name

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)
Name field: must match directory name exactly
Description: 1-1024 characters, include trigger phrases

4. Structure your skill

skills/your-skill-name/
├── SKILL.md           # Required - main instructions
├── references/        # Optional - additional documentation
│   └── guide.md
├── scripts/           # Optional - executable code
│   └── helper.py
└── assets/            # Optional - templates, images, data
    └── template.json

5. Write effective instructions

Keep SKILL.md under 500 lines
Move detailed reference material to references/
Include step-by-step instructions
Add examples of inputs and outputs
Cover common edge cases

Improving Existing Skills

Read the existing skill thoroughly
Test your changes locally
Keep changes focused and minimal
Update the version in metadata if making significant changes

Submitting Your Contribution

Fork the repository
Create a feature branch (git checkout -b feature/new-skill-name)
Make your changes
Test locally with an AI agent
Submit a pull request using the appropriate template:

Skill Quality Checklist

name matches directory name
description clearly explains when to use the skill
Instructions are clear and actionable
No sensitive data or credentials
Follows existing skill patterns in the repo

Questions?

Open an issue if you have questions or need help with your contribution.

2.5 KiB Raw Blame History