Corey Haines
30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
90 lines
2.5 KiB
Markdown
90 lines
2.5 KiB
Markdown
# 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](https://github.com/coreyhaines31/marketingskills/issues/new?template=skill-request.yml).
|
|
|
|
## Adding a New Skill
|
|
|
|
### 1. Create the skill directory
|
|
|
|
```bash
|
|
mkdir -p skills/your-skill-name
|
|
```
|
|
|
|
### 2. Create the SKILL.md file
|
|
|
|
Every skill needs a `SKILL.md` file with YAML frontmatter:
|
|
|
|
```yaml
|
|
---
|
|
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., `emails`)
|
|
- **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
|
|
|
|
1. Read the existing skill thoroughly
|
|
2. Test your changes locally
|
|
3. Keep changes focused and minimal
|
|
4. Update the version in metadata if making significant changes
|
|
|
|
## Submitting Your Contribution
|
|
|
|
1. Fork the repository
|
|
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:
|
|
- [New Skill](?template=new-skill.md)
|
|
- [Skill Update](?template=skill-update.md)
|
|
- [Documentation](?template=documentation.md)
|
|
|
|
## 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.
|