bencium/bencium-marketplace8 files

Insurgent Campaign

>

Specification
Skill ID
bencium/bencium-marketplace/insurgent-campaign
Publisher
bencium
Repository
bencium-marketplace
Installs
0
Files
8
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

bencium/bencium-marketplace/insurgent-campaignInstalls these files
  • SKILL.md
  • references/asymmetry-audit-table.md
  • references/authenticity-playbook.md
  • references/campaign-archetypes.md
  • references/channel-tier-stack.md
  • references/hungarian-case-study.md
  • references/lift-test-templates.md
  • references/sector-riders.md

What this skill tells the agent

Insurgent Campaign

A campaign-design skill for organizations and people who cannot win by outspending. It ideates campaign concepts across every major archetype, audits the user's spend asymmetry against their competition, assembles an insurgent channel stack, sets strict boost gates on any paid spend, and produces a lift-test plan so the user measures incremental impact rather than vanity metrics.

Core Premise

Paid media scales attention. Organic narrative and grassroots networks scale trust. When trust is the bottleneck — and in 2025–2026, for most underdogs, it is — additional ad spend hits diminishing and then negative returns. Saturation, inauthenticity, and narrative incoherence produce reactance, not persuasion. The leverage point is not reach; it is credibility and message-market fit.

Empirical spine:

  • Academic field experiments show digital ad ROI confidence intervals are so wide that most campaigns cannot be statistically distinguished from zero lift (Lewis & Rao, "The Unfavorable Economics of Measuring the Returns to Advertising," Quarterly Journal of Economics 2015). Meta and Google both ship Conversion Lift / Brand Lift tools precisely because they distinguish attributed conversions from incremental conversions — the platforms' own tooling is the tacit admission that dashboard ROAS is not causal.
  • Across 18,000+ brands, CPA rose in 13/14 industries in 2025; ROAS fell in 13/14; conversion rates fell in 13/14. More money is buying fewer results.
  • Facebook organic engagement sits near 0.15%, Instagram ~0.50%, X ~0.15%, TikTok ~2.50% — still the best organic window but compressing fast.
  • Meta and Google both ended political/issue ads in the EU in October 2025, removing paid channels entirely for large categories and forcing organic to carry the campaign.
  • Under the most extreme spending asymmetry imaginable (a grassroots party vs. a €4B state-backed communications apparatus with foreign support), the side with near-zero paid media won a parliamentary supermajority in Hungary in April 2026 — see references/hungarian-case-study.md.

The same curve bends commercial advertising. The skill treats paid as an amplifier of proven organic winners, never as a standalone channel.

When to Apply This Skill

Apply when the user:

  • Asks to plan any campaign (marketing, launch, fundraising, mobilization, awareness, turnout).
  • Describes being outspent by a competitor, incumbent, or adversary.
  • Is considering ad spend, boosts, influencer deals, or scaling a paid channel.
  • Is watching their organic reach collapse and wondering what to do.
  • Is preparing for a launch, election, fundraise, product push, or cause-led moment.
  • Is deciding between paid and organic allocation, or between channels.

Also apply when no explicit "campaign" is named but the user is debating where to invest time and money for distribution.

Workflow

The skill runs in seven stages (1, 2, 3, 3a, 4, 5, 5b). Do not skip stages; later stages depend on the user's answers and selections from earlier ones. Stage 3a (MMF Gate) can refuse the full campaign plan and route the user to validation work instead. Stage 5 ends with a shape selection — Stage 5b only begins once the user has picked one of the three shapes.

This skill is designed to be portable across agent environments. Where the workflow says "ask the user," use whatever structured-question facility your environment provides (in Claude Code that is the AskUserQuestion tool, batching up to 4 questions per call); if no structured tool exists, ask in plain text and wait for the user to reply before continuing. Either way, never invent answers.

Resume Protocol (idempotency). Before producing any output, scan the conversation for prior skill output. If a section's heading (## N. <name>) is already present in the conversation, do not regenerate it. Pick up at the first stage whose Contract preconditions are satisfied AND whose output section(s) are not yet in the conversation. If the user explicitly asks to restart, restart from Stage 1; otherwise resume rather than rerun. This makes the skill safely re-invokable: a second call in the same conversation produces only the next incremental section, never duplicates or regressions to earlier stages. Scope: idempotency holds within a single conversation; if prior output exists only in an external file or a previous session, paste it into the conversation first or restart from Stage 1.

Stage Contracts. Each stage below opens with a Contract block declaring inputs, outputs, preconditions, postconditions, and failure modes. The contract is the structural boundary — it is what makes the stage retry-safe, error- explicit, and self-describing. Treat the contract as binding: if the preconditions are not met, do not enter the stage; if a failure-mode trigger fires, take the declared action rather than improvising.

Stage 1 — Interview / Brief Capture

Contract

  • Inputs: user's initial brief (free text, any length).
  • Outputs: Section 0 (Assumptions table) under Mode C; mode-tag (A/B/C) and the 8 fields captured in working memory for downstream stages.
  • Preconditions: none (entry stage).
  • Postconditions: all 8 fields have a value (captured, defaulted, or flagged as [ask] for a still-pending question); mode is determined.
  • Failure modes:
  • any always-capture field missing under Mode C → add it to the question batch; do not default silently.
  • a missing field would change Stage 3 asymmetry classification OR Stage 4 function choice → escalate it into the batch even if it would normally default.
  • user gives contradictory values for the same field → ask one clarifying question; do not pick one silently.

The skill has three intake modes. Pick the mode that matches the user's brief before asking any questions.

Mode A — Full-brief mode. The user has volunteered all 8 fields below up front (in a pasted brief, a prior plan, a detailed message). Skip the interview entirely, confirm understanding in one sentence, and proceed to Stage 2.

Mode B — Interview mode. The user explicitly asks to be scoped ("help me figure out what this campaign should be," "walk me through it," "interview me"). Ask the 8 questions below in batches of ≤4 per turn, using the environment's structured question facility if one exists (see the structured-tool note in the Workflow section above). Do not invent answers. Do not merge questions.

Mode C — Default mode (for terse briefs). The user gave a short brief (≤2 sentences) without asking for an interview. This is the common case. Do NOT run the full 8-question interview — it turns a 12-word prompt into an interrogation. Instead:

  1. Always-capture fields (ask once, batched). Four fields are too material to default silently; getting them wrong produces a generic plan. Ask the user in one batch of up to 4 questions covering:
  • Outcome — what specific action is the campaign driving (signups, ticket sales, votes, donations, attendance, pre-orders, qualified demos)?
  • Audience — who is the target? Who experiences the problem? Geography, seniority, community membership. "Everyone interested in AI" is not an audience; "London-based senior AI/ML engineers at Series A–C startups" is.
  • Sector — pick from the 6 riders in references/sector-riders.md (cohort-education, b2b-saas, ngo, consumer-brand, political-civic, personal-brand), or other with a one-sentence description. The sector rider materially changes Stage 4 channel weighting and Stage 5 archetype defaults.
  • Budget — what can you actually spend per month (€0 / <€1k / €1k–10k / €10k+) and what is the competitor's rough spend (unknown / similar / 5× ours / 50×+ ours)? Budget materially changes Stage 3 asymmetry classification and Stage 4 paid-channel availability. Never default this silently.

Use this skill in a project

Open any RiverX project, search the Skills panel for bencium/bencium-marketplace/insurgent-campaign, and install it in one click.

Use this skill