marketing-skill-pack

Why use it

Key features

Bundles four marketing skills + 26 VS Code extensions in one install
Update-aware: re-runs pull against each pack rather than fresh cloning
Cross-platform installers (bash + PowerShell)
Tolerates per-step failures — completes partial installs without aborting

Live Demo

What it looks like in practice

marketing-skill-pack-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use marketing-skill-pack

Bootstrap a full marketing Claude environment on a new machine

👤 Solo marketers or agency teams standing up Claude Code ⏱ ~15 min beginner

When to use: Fresh laptop, want to skip the 30-minute manual clone-and-wire routine.

Prerequisites

git + Claude Code installed — brew install git && follow Claude Code install guide

Flow

Run the installer

bash <(curl -fsSL https://raw.githubusercontent.com/AgriciDaniel/marketing-skill-pack/main/install.sh)✓ Copied

→ Four packs clone into ~/.claude/packs/, VS Code extensions install
Verify in Claude Code

Which marketing-pack skills are available right now?✓ Copied

→ Claude lists Claude SEO, Claude Blog, Skill Forge, WP MCP Ultimate
Pin the WordPress MCP

Configure WP MCP Ultimate to point at https://mysite.com — give me the env var block.✓ Copied

→ Step-by-step auth setup

Outcome: A working Claude marketing environment in 10 minutes.

Pitfalls

Installer continues past a failure you actually needed — Re-run and watch each line — tolerance for failure doesn't mean 'ignore errors forever'

Combine with: claude-code-marketing-skill

Update every skill in the pack with one command

👤 Existing pack users ⏱ ~5 min beginner

When to use: It's been a month and you want the latest prompts without manually git-pulling four repos.

Flow

Re-run the installer in update mode

Re-run the marketing-skill-pack installer — it should do git pull on each sub-pack.✓ Copied

→ Pulls report up-to-date or new commits per pack

Outcome: All four skills updated, VS Code extensions re-checked.

Pitfalls

Local edits to a pack get overwritten — Fork the pack you edit rather than modifying ~/.claude/packs/ in-place

Combinations

Pair with other MCPs for X10 leverage

marketing-skill-pack-skill + claude-code-marketing-skill

Overlap with Cogny's pack — pick the one that matches your workflow, don't run both blindly

Compare marketing-skill-pack's Claude SEO against claude-code-marketing-skills /seo-audit — which covers my stack?✓ Copied

marketing-skill-pack-skill + github

Fork each pack so your team's customizations survive updates

Fork Claude SEO into our org, redirect ~/.claude/packs/claude-seo to the fork.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
install_all	none (detects OS)	First-time setup on a machine
update_all	none	Monthly refresh
install_single	pack name	You only want one of the four

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Varies per sub-skill
Monetary: Free — skills are local files; WP MCP Ultimate is the author's own plugin and may have its own licensing
Tip: Install only the packs you'll actually use — each adds context overhead when Claude auto-loads them.

Security

Permissions, secrets, blast radius

Credential storage: No credentials — pure prompts. WP MCP Ultimate needs WordPress creds if used.

Data egress: None from the installer. Sub-packs may call external services (WordPress, SEO APIs).

The installer runs a remote bash script — read it before piping to bash if you care about supply chain.

Troubleshooting

Common errors and fixes

SKILL.md frontmatter wrong in a sub-pack

Go into the specific pack's folder and inspect.

Verify: head ~/.claude/packs/claude-seo/SKILL.md

Wrong trigger keywords — installer ran but nothing triggers

Each sub-pack has its own trigger; reference by name ('use claude-seo to audit...').

Alternatives