by Cesarjoquin
AI agent Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, ai agent, and growth engineering, ai agent
# Add to your Claude Code skills
git clone https://github.com/Cesarjoquin/Marketing-SkillsGuides for using ai agents skills like Marketing-Skills.
Marketing-Skills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Cesarjoquin. AI agent Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, ai agent, and growth engineering, ai agent. It has 51 GitHub stars.
Marketing-Skills's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Cesarjoquin/Marketing-Skills" and add it to your Claude Code skills directory (see the Installation section above).
Marketing-Skills is primarily written in TypeScript. It is open-source under Cesarjoquin on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Marketing-Skills against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
A production-ready toolkit for AI agents working on marketing tasks. Ships 51+ Agent Skills (markdown workflows) and a TypeScript CLI platform with optional Redis-backed response caching.
Built for engineers and technical marketers who want reproducible, testable tooling around conversion optimization, copywriting, SEO, analytics, and growth workflows.
| Capability | Description |
|---|---|
| Agent Skills | Spec-compliant SKILL.md files for Claude Code, Cursor, Codex, and other Agent Skills hosts |
| Unified CLI | Single marketing-skills entry point for 64 marketing tool integrations |
| Redis cache | Optional persistence layer for CLI responses with graceful shutdown |
| Strict TypeScript | Typed core libraries, ESLint, Vitest, and CI validation |
| Cross-platform validation | Node-based skill validator (replaces bash-only audit) |
| Plugin marketplace | Claude Code plugin manifest in .claude-plugin/ |
flowchart TB
subgraph Content["Content Layer"]
SK[skills/*/SKILL.md]
INT[tools/integrations/*.md]
end
subgraph Runtime["TypeScript Runtime"]
CLI[marketing-skills CLI]
SYNC[ms-sync]
VAL[ms-validate]
REG[CLI Registry]
end
subgraph Core["Core Libraries"]
CFG[config]
LOG[logger]
HTTP[http-client]
ARGS[parse-args]
end
subgraph Persistence["Persistence"]
REDIS[(Redis)]
CACHE[cache layer]
end
SK --> VAL
SK --> SYNC
CLI --> REG
REG --> Core
CLI --> CACHE
CACHE --> REDIS
SYNC --> SK
flowchart LR
PM[product-marketing] --> SEO[SEO & Content]
PM --> CRO[CRO]
PM --> COPY[Copy]
PM --> PAID[Paid & Analytics]
PM --> GROWTH[Growth & Retention]
PM --> GTM[Sales & GTM]
PM --> STRAT[Strategy]
Every skill reads product-marketing context first for positioning, audience, and messaging consistency.
marketingskills/
├── src/ # TypeScript application code
│ ├── cli.ts # Unified CLI entry
│ ├── config/ # Environment configuration (Zod)
│ ├── lib/
│ │ ├── cli/ # Argument parsing, HTTP helpers
│ │ ├── logger/ # Structured logging
│ │ └── redis/ # Connection manager + cache
│ ├── skills/ # Sync + validate modules
│ └── clis/ # Per-tool CLI handlers (64 tools)
├── skills/ # Agent Skills content (unchanged spec)
├── tools/
│ ├── clis/ # CLI documentation
│ └── integrations/ # API integration guides
├── tests/ # Vitest unit tests
├── docs/ # Engineering documentation
├── dist/ # Build output (gitignored)
└── .claude-plugin/ # Claude Code marketplace manifest
Design decisions
src/.run(args) handler; shared logic lives in src/lib/.REDIS_ENABLED=false for local development without infrastructure.git clone https://github.com/coreyhaines31/marketingskills.git
cd marketingskills
npm install
cp .env.example .env
npm run build
npx skills add coreyhaines31/marketingskills
Or install individual skills from the skills/ directory into .agents/skills/.
Copy .env.example to .env and adjust:
| Variable | Default | Description |
|---|---|---|
LOG_LEVEL |
info |
Logging verbosity |
REDIS_ENABLED |
true |
Set false to disable Redis |
REDIS_URL |
redis://127.0.0.1:6379 |
Redis connection URL |
REDIS_KEY_PREFIX |
ms: |
Key namespace prefix |
REDIS_CACHE_TTL_SECONDS |
300 |
CLI response cache TTL |
SKILLS_DIR |
skills |
Skills directory path |
Tool-specific API keys (e.g. GA4_ACCESS_TOKEN, APOLLO_API_KEY) are read at runtime by each CLI module.
# Watch mode
npm run dev
# Type check
npm run typecheck
# Lint
npm run lint
# Test
npm run test
# Full pipeline
npm run validate
npx marketing-skills list
npx marketing-skills ga4 reports run --property 123456789 --dry-run
npx marketing-skills apollo people search --titles "CEO,CTO"
npm run sync-skills # Update README table + marketplace.json
npm run validate-skills # Audit all SKILL.md files
npm test # Run all unit tests
npm run test:watch # Watch mode
Tests cover argument parsing, configuration loading, skill discovery/validation, Redis connection management, and cache key generation.
sequenceDiagram
participant Dev as Developer
participant CLI as marketing-skills
participant Cache as Redis Cache
participant API as External API
Dev->>CLI: marketing-skills ga4 reports run
CLI->>Cache: getCached(key)
alt cache hit
Cache-->>CLI: cached JSON
CLI-->>Dev: response (_cached: true)
else cache miss
CLI->>API: HTTP request
API-->>CLI: JSON response
CLI->>Cache: setCached(key, ttl)
CLI-->>Dev: response
end
Redis connection failedredis-cli pingREDIS_ENABLED=false for local dev without RedisREDIS_URL formatUnknown tool: xyzRun npx marketing-skills list for available tools. Tool names match the legacy tools/clis/ filenames (e.g. ga4, apollo).
GA4_ACCESS_TOKEN environment variable requiredEach tool requires its own API credentials. See tools/integrations/ for setup guides.
Run npm run validate-skills for detailed per-skill errors. Common issues:
name must match directory name (lowercase, hyphens only)description must include trigger phrasesSKILL.md should stay under 500 linesrm -rf dist node_modules
npm install
npm run build
npm run validate before committingSee CONTRIBUTING.md for skill authoring guidelines.
Is this a fork of the original Marketing Skills repo?
Yes — this version adds a TypeScript runtime, Redis caching, tests, and CI while preserving the original skill content and workflows.
Do I need Redis?
No. Set REDIS_ENABLED=false and the CLI works without caching.
Can I still use individual tool scripts?
Use npx marketing-skills <tool> instead of standalone node tools/clis/*.js scripts.
Are skills still markdown-only?
Yes. Skills under skills/ remain content files with no build step.
How do skills relate to CLIs?
Skills provide agent workflows; CLIs provide JSON API access to external marketing tools referenced in those workflows.
| Skill | Description |
|---|---|
| ab-testing | When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.... |
| ad-creative | When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad... |
| ads | When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X,... |
| ai-seo | When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.... |
| analytics | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
| aso | When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO... |
| churn-prevention | When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or... |
| co-marketing | When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use... |
| cold-email | Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails,... |
| community-marketing | Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a... |
| competitor-profiling | When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions... |
| competitors | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
| content-strategy | When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also... |
| copy-editing | When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the... |
| copywriting | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages,... |
| cro | When the user wants to optimize, improve, or increase conversions on any marketing page or form — including h |