Help

/digital-marketing-pro:help

Show the Digital Marketing Pro user guide with live plugin state (version, agent/skill/command/script counts, connector counts, runtime environment) pulled from disk — not hardcoded — plus getting-started steps, usage examples, and troubleshooting.

CRITICAL: never hardcode version, counts, or connector numbers

Versions and counts in this plugin used to be baked into this skill body as literal version and count strings — a hardcoded version number, a fixed slash-command count, a fixed integrations count. Those drifted out of sync with the actual install every release and misreported the plugin to users.

Always read live values from scripts/plugin-metadata.py. Never quote a version number, skill count, agent count, command count, or connector count from memory or from this skill body.

Behavior

Step 1 — Fetch live plugin metadata

Run first, every time this skill is invoked (any argument or none):

python "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-metadata.py" --section all-with-environment

This returns JSON with:

• version — { version, name, required_min_version, ... }
• assets — { agents, skills_total, commands, scripts, reference_docs }
• connectors — { available_http, available_npx, available_total, active_count, active_names, cowork_compatible_count }
• skills — array of { skill_dir, slash_command, description }
• commands — array of { command_file, slash_command, description }
• environment — runtime detection (local Claude Code vs Cowork sandbox, with a warning if filesystem writes won't reach the user's host)

Substitute the values from this JSON into every place the help output references a count, a version, or a slash-command list. Do not invent or quote numbers from elsewhere.

Step 2 — Default rendering (no args)

Render a clean orientation using the live data. Suggested format (fill every <...> from the JSON):

=== DIGITAL MARKETING PRO ===
Version: <version.version>
Agents: <assets.agents> | Skills: <assets.skills_total> | Commands: <assets.commands> | Scripts: <assets.scripts>
Connectors: <connectors.available_http> HTTP + <connectors.available_npx> npx available
  (<connectors.active_count> currently active in your .mcp.json)
  Cowork-compatible: <connectors.cowork_compatible_count> (HTTP only — npx connectors don't run in Cowork)
Environment: <environment.environment>
<if environment.cowork_warning is non-null, show it as a WARNING block>

Getting Started:
  1. /digital-marketing-pro:brand-setup       — Create your brand profile (start here)
  2. /digital-marketing-pro:import-guidelines  — Import voice guides, restrictions, templates
  3. /digital-marketing-pro:integrations       — See which connectors are active
  4. /digital-marketing-pro:connect <name>     — Set up a new connector
  5. Just ask!                                 — Describe what you need in natural language

Step 3 — Cowork warning (when applicable)

If environment.cowork_warning is non-null, surface it prominently after the orientation block, explaining that brand-state writes to ~/.claude-marketing/ land inside the sandbox and won't persist to the user's host; recommend /digital-marketing-pro:cowork-setup to route state through a Drive MCP.

Step 4 — Argument routing

When rendering the skills/commands list, iterate over the JSON arrays — do not paste a hand-maintained list, and do not state a total count from memory. Each row shows the slash_command field as the user-facing label and the description field as the explanation.

Step 5 — Example prompts (--examples)

Show real-world example prompts across marketing tasks:

Getting Started:
  /digital-marketing-pro:brand-setup
  → Create your brand profile interactively (5 quick questions or 17 detailed)

Strategy:
  "Plan a product launch for our new cold brew line"
  → Activates the campaign orchestrator with your brand context

Content:
  "Write a 3-email welcome sequence for new subscribers"
  → Creates emails in your brand voice with compliance rules applied

SEO:
  /digital-marketing-pro:seo-audit https://example.com
  → Full technical + content + E-E-A-T audit with action items

Competitive:
  /digital-marketing-pro:competitor-analysis "Blue Bottle, Counter Culture, Stumptown"
  → Multi-dimensional analysis: content, SEO, ads, social, positioning

Analytics:
  /digital-marketing-pro:performance-report
  → KPI tracking, trend analysis, anomaly detection, recommendations

AI Visibility:
  /digital-marketing-pro:aeo-audit
  → Check how your brand appears in ChatGPT, Perplexity, Google AI Overviews

Full engagement:
  /digital-marketing-pro:engagement start acme-corp 2026-q2
  → Run the full 12-Part strategy methodology end to end

Step 6 — Troubleshooting (--troubleshoot)

Step 7 — Documentation references

Output formatting rules

• Render in clean, scannable tables and code blocks. Keep it concise — this is a quick reference, not a tutorial.
• Always quote version and counts from the JSON, never from this file body.
• Iterate the JSON skills / commands arrays for those lists — never a hand-maintained list.
• If scripts/plugin-metadata.py fails to run (e.g. Python not available), fall back to: "Live metadata script could not run. Plugin version is in .claude-plugin/plugin.json; the skill list is in skills/; the command list is in commands/." Do not invent numbers in the fallback either.

What this skill explicitly avoids

• Quoting version numbers from this file body
• Quoting any count string (agent count, skill count, command count, integrations count) from this file body
• Listing slash commands manually — always derived from the JSON
• Stale references to renamed skills (always use the names from the JSON)