doctor
Per-action readiness diagnostic. Shows which campaign-audit and launch-campaign actions are live (manifest-ready) vs blocked (stub-unconfigured) in the current environment, with one-step setup hints for the blocked ones. Now includes model-registry freshness + Cowork+Drive routing status.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/indranilbanerjee/digital-marketing-pro/HEAD/commands/doctor.md -o ~/.claude/commands/doctor.mddoctor.md
# /digital-marketing-pro:doctor — Per-Action Readiness Check Resolves every action in the campaign-audit and launch-campaign skill surfaces against the currently configured connectors and reports which mode each one is in: | Mode | What it means | |------|---------------| | `real` | Action runs end-to-end with no external API. Always available. | | `manifest_ready` | A matching connector is configured; the action returns the exact HTTP request manifest for the orchestrator (Claude via MCP) to execute. | | `stub_unconfigured` | No matching connector is configured; the action returns a structured stub plus a copy-paste setup hint. | ## Quick examples ``` /digital-marketing-pro:doctor # full readiness map for default brand /digital-marketing-pro:doctor --brand acme # for a named brand /digital-marketing-pro:doctor --action inventory --channel google_ads /digital-marketing-pro:doctor --summary # one-line counts /digital-marketing-pro:doctor --json # machine-readable ``` ## What it does NOT do - It does not execute write/launch actions. For that, run the action through the orchestrator (`/digital-marketing-pro:launch-campaign`) which respects approval gates. - It does not make any network call. It probes `.mcp.json` membership and env-var presence only — credentials are never read or echoed. ## Output sections 1. **Summary line** — count of actions in each of the three modes 2. **Per-action table** — action name, mode, operation type, configured connector or list of candidate connectors 3. **Unlock guide** — for any stub-unconfigured action, the exact next step 4. **Environment block** — detected surface (`claude-code-windows` / `claude-code-mac` / `claude-code-linux` / `cowork-sandbox`) 5. **Model curator block** — registry age + severity (`ok` <60d, `warn` 60-119d, `urgent` >=120d), with the exact `refresh_models.py` command when stale 6. **Cowork+Drive routing block** — only meaningful in Cowork. Shows whether `/digital-marketing-pro:cowork-setup` has been run; flags `urgent` when Cowork is detected but routing is missing (brand state would vanish at session end) ## See also - [scripts/action-doctor.py](../scripts/action-doctor.py) — the underlying script - [scripts/connector_resolver.py](../scripts/connector_resolver.py) — the resolver and ACTION_SPECS table - [scripts/connector-status.py](../scripts/connector-status.py) — the broader connector dashboard (categories, setup guides) - [/digital-marketing-pro:check](check.md) — pre-publish quality gate - [/digital-marketing-pro:status](status.md) — brand snapshot ## Run ```bash python scripts/action-doctor.py "$@" ```
Invoke when the user needs to manage multiple client brands, view portfolio-level dashboards, generate client reports, manage SOPs, switch credential profiles, assign team tasks, configure regions, or generate executive summaries. Triggers on requests involving multi-client management, agency workflows, client onboarding, or portfolio oversight.
Invoke when the user needs help with marketing measurement, KPI definition, dashboard design, attribution modeling, performance analysis, anomaly detection, competitive benchmarking, or translating data into marketing decisions. Triggers on requests involving metrics, reporting, analytics setup, or data interpretation.
Invoke when marketing content needs quality control review — brand voice consistency checks, regulatory compliance verification (GDPR, CAN-SPAM, CCPA, HIPAA, FTC, industry-specific), accessibility auditing (WCAG 2.1), inclusive language review, or brand safety assessment. Automatically invoked as a final review step before any content is published or delivered.
Invoke when the user needs competitor analysis — content strategy teardowns, SEO gap analysis, paid ad analysis from ad libraries, social media benchmarking, AI visibility comparisons, pricing and positioning research, or market landscape mapping. Triggers on requests mentioning competitors, competitive gaps, market analysis, or benchmarking.
Use when the task requires ongoing competitive monitoring, competitor change detection, share of voice tracking, competitive alerts, ad monitoring, price monitoring, win/loss analysis, or competitive narrative mapping.
Invoke when the user needs any form of marketing content created or refined — blog posts, ad copy, email campaigns, social media posts, landing page copy, press releases, video scripts, product descriptions, or newsletter content. Triggers on requests to write, draft, rewrite, or improve marketing copy.
Invoke when the user needs to manage CRM operations — creating contacts, importing leads, updating deals, syncing campaign data, segmenting audiences, managing pipelines, or connecting marketing data to Salesforce, HubSpot, Zoho, or Pipedrive. Triggers on requests involving CRM data, lead management, pipeline updates, or sales-marketing alignment.
Invoke when the user needs help with conversion rate optimization — landing page audits, A/B test design, form optimization, pricing page strategy, checkout flow improvement, personalization, statistical significance calculations, page speed impact analysis, or mobile conversion optimization. Triggers on requests involving conversions, landing pages, A/B testing, or optimization experiments.