agentleFS
mysticaltechmysticaltech/marketingskills/AGENTS.md

marketingskills

AGENTS.md352 starsChanged 10 months agoMITView on GitHub

Guidelines for AI agents working in this repository. 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. Not applicable - This is a content-only repository with no executable code. 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 Skills follow the Agent Skills spec. Valid:…

The file

We split this AGENTS.md into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Very specific:

    No consecutive hyphens (--)

    line 64
  2. Distinctive:

    Must match parent directory name exactly

    line 65
  3. Very specific:

    Keep SKILL.md under 500 lines (move details to references/)

    line 84
  4. Very specific:

    Use H2 (##) for main sections, H3 (###) for subsections

    line 85
  5. Distinctive:

    Use bullet points and numbered lists liberally

    line 86
  6. Distinctive:

    When to use it (trigger phrases)

    line 113
  7. Distinctive:

    Follow the Conventional Commits specification:

    line 141
  8. Very specific:

    Tool discovery: Read tools/REGISTRY.md to see available tools and their capabilities

    line 159
  9. Distinctive:

    When using any skill from this repository:

    line 185
  10. Very specific:

    Run git pull in the marketingskills directory

    line 203

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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.

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
  • name field matches directory name exactly
  • name is 1-64 chars, lowercase alphanumeric and hyphens only
  • description is 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

FieldRequiredConstraints
nameYes1-64 chars, lowercase a-z, numbers, hyphens. Must match dir.
descriptionYes1-1024 chars. Describe what it does and when to use it.
licenseNoLicense name (default: MIT)
metadataNoKey-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.md under 500 lines (move details to references/)
  • 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:

  1. What the skill does
  2. When to use it (trigger phrases)
  3. 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: feature/skill-name
  • Improvements: fix/skill-name-description
  • Documentation: docs/description

Commit Messages

Follow the Conventional Commits specification:

  • feat: add skill-name skill
  • fix: improve clarity in page-cro
  • docs: update README

Pull Request Checklist

  • name matches directory name exactly
  • name follows naming rules (lowercase, hyphens, no --)
  • description is 1-1024 chars with trigger phrases
  • SKILL.md is 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.md to see available tools and their capabilities
  • Integration details: See tools/integrations/{tool}.md for API endpoints, auth, and common operations
  • MCP-enabled tools: ga4, stripe, mailchimp, google-ads, resend, zapier

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:

  • referral-program skill → rewardful, tolt, dub-co, mention-me guides
  • analytics-tracking skill → ga4, mixpanel, segment guides
  • email-sequence skill → customer-io, mailchimp, resend guides
  • paid-ads skill → google-ads, meta-ads, linkedin-ads guides

Checking for Updates

When using any skill from this repository:

  1. Once per session, on first skill use, check for updates:
  2. 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)
  3. 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.
  4. If user says "update skills":
    • Run git pull in the marketingskills directory
    • Confirm what was updated

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.