claude-agent-skills-hub / marketingskills
AGENTS.md0 starsChanged 56 days agoMITView on GitHub
Guidelines for AI agents working in this repository. This repository contains Agent Skills for AI agents following the Agent Skills specification. Skills install to .agents/skills/ (the cross-agent standard). This repo also serves as a Claude Code plugin marketplace via .claude-plugin/marketplace.json. Skills are content-only (no build step). Verify manually: - YAML frontmatter is valid - name field matches directory name exactly - name is 1-64 chars, lowercase alphanumeric and hyphens only - description is 1-1024 characters CLI tools (tools/clis/*.js) are zero-dependency…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository55 other files it gives its agents.
- agent-browser/AGENTS.mdAGENTS.md
- caveman/AGENTS.mdAGENTS.md
- find-skills/AGENTS.mdAGENTS.md
- graphify/AGENTS.mdAGENTS.md
- gsap/AGENTS.mdAGENTS.md
- gstack/AGENTS.mdAGENTS.md
- humanizer/AGENTS.mdAGENTS.md
- hyperframes/AGENTS.mdAGENTS.md
- hyperiux-components/AGENTS.mdAGENTS.md
- i-have-adhd/AGENTS.mdAGENTS.md
- impeccable/AGENTS.mdAGENTS.md
- last30days-skill/AGENTS.mdAGENTS.md
- notebooklm-py/AGENTS.mdAGENTS.md
- ponytail/AGENTS.mdAGENTS.md
- superdesign-skill/AGENTS.mdAGENTS.md
- superpowers/AGENTS.mdAGENTS.md
- caveman/CLAUDE.mdCLAUDE.md
- claude-hud/CLAUDE.mdCLAUDE.md
- gsap/CLAUDE.mdCLAUDE.md
- gstack/CLAUDE.mdCLAUDE.md
- hyperframes/CLAUDE.mdCLAUDE.md
- hyperiux-components/CLAUDE.mdCLAUDE.md
- impeccable/CLAUDE.mdCLAUDE.md
- last30days-skill/CLAUDE.mdCLAUDE.md
- marketingskills/CLAUDE.mdCLAUDE.md
- notebooklm-py/CLAUDE.mdCLAUDE.md
- superdesign-skill/CLAUDE.mdCLAUDE.md
- ui-ux-pro-max/CLAUDE.mdCLAUDE.md
- ui-ux-pro-max-skill/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- brandkitSkill
- industrial-brutalist-uiSkill
- defuddleSkill
- gpt-tasteSkill
- gstackSkill
- humanizerSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- json-canvasSkill
- last30daysSkill
- llm-councilSkill
- minimalist-uiSkill
- notebooklmSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- full-output-enforcementSkill
- redesign-existing-projectsSkill
- high-end-visual-designSkill
- stitch-design-tasteSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- ui-ux-design-patternsSkill
- webgpu-threejs-tslSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Do not bump y for content added to an existing skill, no matter how substantial — that's a z release (e.g.
- Very specific: line 99
No consecutive hyphens (--)
- Distinctive: line 100
Must match parent directory name exactly
- Very specific: line 119
Keep SKILL.md under 500 lines (move details to references/)
- Very specific: line 120
Use H2 (##) for main sections, H3 (###) for subsections
- Distinctive: line 121
Use bullet points and numbered lists liberally
- Distinctive: line 148
When to use it (trigger phrases)
- Distinctive: line 176
Follow the Conventional Commits specification:
- Very specific: line 194
Tool discovery: Read tools/REGISTRY.md to see available tools and their capabilities
- Distinctive: line 224
When using any skill from this repository:
- Distinctive: line 242
Run git pull in the marketingskills directory
- Very specific: line 259
Instead of every skill telling the agent "go check if .agents/product-marketing.md exists and read it," you can inject it automatically:
- Distinctive: line 265
Place this at the top of a skill's body (after frontmatter) to make context available immediately without any file-reading step.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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. Skills install to .agents/skills/ (the cross-agent standard). This repo 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
├── tools/
│ ├── clis/ # Zero-dependency Node.js CLI tools (66 tools)
│ ├── composio/ # Composio integration layer (quick start + toolkit mapping)
│ ├── integrations/ # API integration guides per tool
│ └── REGISTRY.md # Tool index with capabilities
├── CONTRIBUTING.md
├── LICENSE
└── README.mdBuild / Lint / Test Commands
Skills are content-only (no build step). Verify manually:
- YAML frontmatter is valid
namefield matches directory name exactlynameis 1-64 chars, lowercase alphanumeric and hyphens onlydescriptionis 1-1024 characters
CLI tools (tools/clis/*.js) are zero-dependency Node.js scripts (Node 18+). Verify with:
node --check tools/clis/<name>.js # Syntax check
node tools/clis/<name>.js # Show usage (no args = help)
node tools/clis/<name>.js <cmd> --dry-run # Preview request without sending
node --test tests/clis/*.test.cjs # Contract tests (mocked fetch, no live calls)Versioning
Two version layers, with different rules:
Repo release version — .claude-plugin/plugin.json version, .claude-plugin/marketplace.json metadata.version, and the VERSIONS.md changelog headings all share one x.y.z number:
- x — repo-wide changes (restructures, spec changes, breaking changes)
- y — new skill(s) added
- z — updates to existing skills
Do not bump y for content added to an existing skill, no matter how substantial — that's a z release (e.g. a new reference file in ad-creative is 2.8.0 → 2.8.1, not 2.9.0).
Per-skill version — metadata.version in each SKILL.md, mirrored in the VERSIONS.md table. Bump on ANY shipped change to that skill: the update check compares VERSIONS.md against users' local skill metadata, so an unbumped change is invisible to installed users. Minor for new capability or description triggers, patch for fixes and clarifications.
Bump the repo release version in the same PR that ships the change (2.7.0 and 2.8.0 shipped without touching plugin.json/marketplace.json and needed a catch-up later).
CI enforces both layers on PRs. Fetch first so origin/main is current, then run it locally before pushing:
node scripts/check-versions.mjs --base origin/mainIt fails if a changed skill didn't bump metadata.version, if VERSIONS.md disagrees with any SKILL.md, if the repo version didn't bump (or has no ### x.y.z block), or if a file in references/ isn't linked from anywhere in its skill. Changes only under a skill's evals/ don't need a bump, since they don't change what installed users get.
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: cro, emails, ab-testing
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 filesWriting 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.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-skillsSee Claude Code plugins documentation for details.
Git Workflow
Branch Naming
- New skills:
feature/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 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
Tool Integrations
This repository includes a tools registry for agent-compatible marketing tools.
- Tool discovery: Read
tools/REGISTRY.mdto see available tools and their capabilities - Connecting accounts: For a new local setup, follow
tools/SETUP.md: check the environment, configure only chosen tools, keep secrets local, and verify a read before proposing broader work - Integration details: See
tools/integrations/{tool}.mdfor API endpoints, auth, and common operations - MCP-enabled tools (checked 2026-10-15; the registry is the source of truth): ga4, stripe, mailchimp, google-ads, meta-ads, resend, zapier, zoominfo, clay, supermetrics, coupler, outreach, crossbeam, introw, exa, apollo, hubspot, attio, close, instantly, lemlist, heyreach, hunter, truelist, fullenrich, leadmagic, rowbound, theirstack, apify, firecrawl, browserbase, calendly, composio
- Composio (integration layer): Adds MCP access to OAuth-heavy tools without native MCP servers (Salesforce, LinkedIn Ads, Google Sheets, Slack, etc.). See
tools/integrations/composio.md
Registry Structure
tools/
├── REGISTRY.md # Index of all tools with capabilities
└── integrations/ # Detailed integration guides
├── ga4.md
├── stripe.md
├── rewardful.md
└── ...When to Use Tools
Skills reference relevant tools for implementation. For example:
referralsskill → rewardful, tolt, dub-co, mention-me guidesanalyticsskill → ga4, mixpanel, segment guidesemailsskill → customer-io, mailchimp, resend guidesadsskill → google-ads, meta-ads, linkedin-ads guides
For tools without native MCP servers (Salesforce, LinkedIn Ads, Google Sheets, Slack, Notion), Composio provides MCP access via a single server. See tools/integrations/composio.md for setup and tools/composio/marketing-tools.md for the full toolkit mapping.
Checking for Updates
When using any skill from this repository:
- Once per session, on first skill use, check for updates:
- Fetch
VERSIONS.mdfrom GitHub: https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/VERSIONS.md - Compare versions against local skill files
- Fetch
- Only prompt if meaningful:
- 2 or more skills have updates, OR
- Any skill has a major version bump (e.g., 1.x to 2.x)
- Non-blocking notification at end of response:
--- Skills update available: X marketing skills have updates. Say "update skills" to update automatically, or run `git pull` in your marketingskills folder. - If user says "update skills":
- Run
git pullin the marketingskills directory - Confirm what was updated
- Run
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.
Claude Code-Specific Enhancements
These patterns are Claude Code only and must not be added to SKILL.md files directly, as skills are designed to be cross-agent compatible (Codex, Cursor, Windsurf, etc.). Apply them locally in your own project's .claude/skills/ overrides instead.
Dynamic content injection with !command``
Claude Code supports embedding shell commands in SKILL.md using !`command` syntax. When the skill is invoked, Claude Code runs the command and injects the output inline — the model sees the result, not the instruction.
Most useful application: auto-inject the product marketing context file
Instead of every skill telling the agent "go check if .agents/product-marketing.md exists and read it," you can inject it automatically:
Product context: !`cat .agents/product-marketing.md 2>/dev/null || echo "No product context file found — ask the user about their product before proceeding."`Place this at the top of a skill's body (after frontmatter) to make context available immediately without any file-reading step.
Other useful injections:
# Inject today's date for recency-sensitive skills
Today's date: !`date +%Y-%m-%d`
# Inject current git branch (useful for workflow skills)
Current branch: !`git branch --show-current 2>/dev/null`
# Inject recent commits for context
Recent commits: !`git log --oneline -5 2>/dev/null`Why this is Claude Code-only: Other agents that load skills will see the literal !`command` string rather than executing it, which would appear as garbled instructions. Keep cross-agent skill files free of this syntax.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

