- Add MIT LICENSE file - Add CONTRIBUTING.md with skill creation guide - Add AGENTS.md and CLAUDE.md for AI agent guidelines - Add issue template for skill requests - Add PR templates for new skills, updates, and docs - Update README with links to contributing guide and license
4.8 KiB
AGENTS.md
Guidelines for AI agents working in this repository.
Repository Overview
This repository contains Agent Skills for AI agents following the Agent Skills specification. It also serves as a Claude Code plugin marketplace via .claude-plugin/marketplace.json.
- Name: Marketing Skills
- GitHub: coreyhaines31/marketingskills
- Creator: Corey Haines
- License: MIT
Repository Structure
marketingskills/
├── .claude-plugin/
│ └── marketplace.json # Claude Code plugin marketplace manifest
├── skills/ # Agent Skills
│ └── skill-name/
│ └── SKILL.md # Required skill file
├── CONTRIBUTING.md
├── LICENSE
└── README.md
Build / Lint / Test Commands
Not applicable - This is a content-only repository with no executable code.
Verify manually:
- YAML frontmatter is valid
namefield matches directory name exactlynameis 1-64 chars, lowercase alphanumeric and hyphens onlydescriptionis 1-1024 characters
Agent Skills Specification
Skills follow the Agent Skills spec.
Required Frontmatter
---
name: skill-name
description: What this skill does and when to use it. Include trigger phrases.
---
Frontmatter Field Constraints
| Field | Required | Constraints |
|---|---|---|
name |
Yes | 1-64 chars, lowercase a-z, numbers, hyphens. Must match dir. |
description |
Yes | 1-1024 chars. Describe what it does and when to use it. |
license |
No | License name (default: MIT) |
metadata |
No | Key-value pairs (author, version, etc.) |
Name Field Rules
- Lowercase letters, numbers, and hyphens only
- Cannot start or end with hyphen
- No consecutive hyphens (
--) - Must match parent directory name exactly
Valid: page-cro, email-sequence, ab-test-setup
Invalid: Page-CRO, -page, page--cro
Optional Skill Directories
skills/skill-name/
├── SKILL.md # Required - main instructions (<500 lines)
├── references/ # Optional - detailed docs loaded on demand
├── scripts/ # Optional - executable code
└── assets/ # Optional - templates, data files
Writing Style Guidelines
Structure
- Keep
SKILL.mdunder 500 lines (move details toreferences/) - Use H2 (
##) for main sections, H3 (###) for subsections - Use bullet points and numbered lists liberally
- Short paragraphs (2-4 sentences max)
Tone
- Direct and instructional
- Second person ("You are a conversion rate optimization expert")
- Professional but approachable
Formatting
- Bold (
**text**) for key terms - Code blocks for examples and templates
- Tables for reference data
- No excessive emojis
Clarity Principles
- Clarity over cleverness
- Specific over vague
- Active voice over passive
- One idea per section
Description Field Best Practices
The description is critical for skill discovery. Include:
- What the skill does
- When to use it (trigger phrases)
- Related skills for scope boundaries
description: When the user wants to optimize conversions on any marketing page. Use when the user says "CRO," "conversion rate optimization," "this page isn't converting." For signup flows, see signup-flow-cro.
Claude Code Plugin
This repo also serves as a plugin marketplace. The manifest at .claude-plugin/marketplace.json lists all skills for installation via:
/plugin marketplace add coreyhaines31/marketingskills
/plugin install marketing-skills
See Claude Code plugins documentation for details.
Git Workflow
Branch Naming
- New skills:
feat/skill-name - Improvements:
fix/skill-name-description - Documentation:
docs/description
Commit Messages
Follow the Conventional Commits specification:
feat: add skill-name skillfix: improve clarity in page-crodocs: update README
Pull Request Checklist
namematches directory name exactlynamefollows naming rules (lowercase, hyphens, no--)descriptionis 1-1024 chars with trigger phrasesSKILL.mdis under 500 lines- No sensitive data or credentials
Skill Categories
See README.md for the current list of skills organized by category. When adding new skills, follow the naming patterns of existing skills in that category.