mcpField
C
campaign-doctor

campaign-doctor

github.com/fortuneflickMarketing & growth044 installsUpdated 3d ago
Repository

About campaign-doctor

campaign-doctor is a skill that diagnoses campaign activity using WarmySender MCP tools, for investigating quiet email or LinkedIn campaigns. It distinguishes normal pacing from actual blockers using tool responses, then reports evidence and a limited set of next actions.

Key features

  1. 01Inspect campaign status and counters
  2. 02Review skipped actions and reasons
  3. 03Check mailbox sending and reading health
  4. 04Check LinkedIn account safety status
  5. 05Inspect LinkedIn campaign throttling

Use cases

  1. 01Determine whether a campaign is waiting normally
  2. 02Investigate email sending or reading issues
  3. 03Identify a LinkedIn safety pause
  4. 04Review LinkedIn limits and refresh timing

MCP support

It uses WarmySender MCP tools to retrieve campaign, skipped-action, mailbox-health, and LinkedIn status information. Findings must be based on tool responses.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fortuneflick/warmysender-claude-plugin --skill campaign-doctor

After installing, type/campaign-doctorin Claude Code to confirm it loaded.

Details

From the project README

Campaign Doctor

Diagnose a quiet campaign with WarmySender's MCP tools. Never guess — every conclusion must come from a tool response.

Workflow

  1. list_campaigns — find the campaign (or use the one the user named). Note its status and counters.
  2. list_skipped_actions with the campaign id (omit it for a workspace-wide view). This returns the actual skip reasons with plain-English explanations.
    • Reasons flagged is_normal_wait: true mean the system is pacing correctly — reassure, don't alarm. Report resumes_at when present.
    • Other reasons are genuine blockers — surface them verbatim.
  3. For email campaigns: get_mailbox_health on the sending mailboxes. Check BOTH channels: health_status (can we send) AND read_channel_state (can we read what arrives). not_tested is NOT a pass.
  4. For LinkedIn: get_linkedin_account_health — if sending_paused_for_safety is true, report safety_pause_explanation verbatim and stop; a safety rest cannot and must not be shortened.
  5. For LinkedIn campaigns: get_linkedin_campaign_throttle to see which allowance binds and when it refreshes.

Report format

Give a short verdict first (working-as-designed vs genuinely blocked), then the evidence, then at most three next actions the user can take in the WarmySender app. Never suggest raising limits — pacing protects their accounts.

Comments

Markdown supported