run-campaign

run-campaign is a skill for Claude Code from alebgl77/claude-inc. It costs 0 tokens per session (1,230 once invoked), scanned A, original, MIT.

A seven-day sales campaign plan for a small business. It turns an offer and the business's existing channels, such as email, social media, a shop, or partners, into a short launch calendar.

In plain words
What is it for?
Launching a promotion, filling empty appointment slots, moving excess or expiring stock, or introducing a product to existing customers.
Why use it?
It gives an owner a concrete promotion to run when sales, bookings, or customer traffic are low. It avoids requiring an advertising account, agency, or long planning period.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-inc plugin — 50 skills, 3 commands, 8 agents shipped together

Good fit Launching a promotion, filling empty appointment slots, moving excess or expiring stock, or introducing a product to existing customers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alebgl77/claude-inc/run-campaign
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add alebgl77/claude-inc --skill run-campaign
Clone the repo
git clone --depth 1 https://github.com/alebgl77/claude-inc

Made for: Claude Code.

Or install claude-inc, the plugin that ships this one along with the rest of its 50 skills, 3 commands, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for run-campaign

README.md
[![agentmods](https://agentmods.dev/badge/skills/alebgl77/claude-inc/run-campaign.svg)](https://agentmods.dev/skills/alebgl77/claude-inc/run-campaign)
Your own site
<a href="https://agentmods.dev/skills/alebgl77/claude-inc/run-campaign"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/run-campaign.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01230
Opus 5 $0.00000 $0.00615
Sonnet 5 $0.00000 $0.00246
Haiku 4.5 $0.00000 $0.00123

Measured 8d ago against content hash a3d7cb2c9f19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

run-campaign scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/run-campaign/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Campaign — Campaign Runner

"Run a campaign."

Seven days, one offer, channels the owner already controls. No ad account required, no agency, no month of planning.

When to use

  • "We need sales this month" / "August is looking empty."
  • "Run a promo for the shop" — seasonal push, anniversary, slow-season filler.
  • "I have 900 emails and an Instagram — do something with them."
  • Launching a new product or service to the existing customer base.
  • Overstock, expiring inventory, or unbooked capacity that needs a deadline.

Workflow

  1. Nail the offer. One offer: the value (what they get and what it's worth), the deadline (day 7, a real date), and the reason-why (anniversary, season, slots to fill, overstock). No fake urgency — the owner must be able to say the reason with a straight face.
  2. Inventory owned channels. Email list size, each social account and its real reach, storefront traffic, partners who'd share. Pick 2–3 that can actually deliver; skip paid unless the user names a budget.
  3. Set the goal and do the math. One number (sales, bookings, covers). Back into required leads with a stated conversion assumption — compute it, write it down, judge day 8 against it.
  4. Build the day-by-day calendar. Tease → launch → proof → reminder → last call, mapped to real dates and the picked channels, respecting the list's tolerance (max three emails in seven days).
  5. Draft every asset. Three emails (launch, reminder, last call), three social posts (tease, proof, last call), flyer or counter-card copy. One voice, one offer, one CTA everywhere — same link, same code.
  6. Build the tracking sheet. Date, channel, spend, leads, sales, revenue, note. Two minutes a day to fill; it is the only reporting.
  7. Schedule the day-8 debrief. Goal vs actual, cost per sale, which channel pulled, keep / change / kill — and the date of the next campaign while the lessons are warm.

Output format

7-DAY CAMPAIGN KIT — <business> — starts <date>

OFFER
Value: <what they get and what it's worth>
Deadline: <day-7 date>
Reason-why: <the honest reason this deal exists>
Goal: <n> <sales/bookings> → needs ~<n> leads at <x>% assumed conversion

CHANNELS (owned)
1. <channel> — reach <n> — role: workhorse
2. <channel> — reach <n> — role: support

CALENDAR
D1 <date> | Tease post (<channel>) — hint, no link yet
D2 <date> | Launch email + post — full offer, one CTA
D3 <date> | Proof post — testimonial or photo, deadline restated
D4 <date> | Storefront/partner push — flyer up, partner shares
D5 <date> | Reminder email — handle the main objection, deadline visible
D6 <date> | Human-angle post — behind the scenes, soft CTA
D7 <date> | Last call — email at 9:00, post at 12:00 — hours left

ASSETS (full drafts follow)
Email 1 — Launch: <subject> + body
Email 2 — Reminder: <subject> + body
Email 3 — Last call: <subject> + body
Post 1 — Tease | Post 2 — Proof | Post 3 — Last call
Flyer: headline, three lines, CTA + <code/link>

TRACKING SHEET
Date | Channel | Spend | Leads | Sales | Revenue | Note

DAY-8 DEBRIEF (fill on <date>)
Goal vs actual | Cost per sale | Channel that pulled | Keep / Change / Kill | Next campaign date

Read the full file on GitHub · 82 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 82 lines · 0 tokens per session scan A a3d7cb2c9f19

Subscribe to this mod's changes

run-campaign is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,230 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

snack-batching

Weekly snack-request batching for {{officechannel}}. Collects Slack shortcut submissions since the last order, consolidates duplicates and standing staples, builds a cart against {{preferredvendor}} within {{weeklybudget}}, and posts it for the office manager to approve before anything is placed.

kortix-ai/suna · 59 tokens

parcel-tracking

Track parcels and check delivery status for Australian and international couriers. Searches Gmail for dispatch/shipping emails and provides tracking links for all major Australian couriers including AusPost, StarTrack, Aramex, CouriersPlease, Sendle, Toll, Team Global Express, DHL, FedEx, TNT, Hunter Express, Border…

jezweb/claude-skills · 112 tokens

mcp-lark

Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.

aahl/skills · 45 tokens

maishou

A price-comparison workflow for products sold through major Chinese online marketplaces. It searches listings and can retrieve product details, purchase links, and available coupons.

aahl/skills · 103 tokens

giasip-dispatch

A skill for sending a task to other AI models and collecting their results. It supports direct API calls, command-line tools and built-in internal agents, depending on the model.

GiaSip/giasip-skills · 162 tokens

checklist

Activate when: user says 'let's make sure we don't skip anything', 'we need a pre-flight', 'build me a checklist for X', 'we keep missing steps in our deployment / close / launch', 'Gawande / Pronovost / checklist manifesto'. Do NOT activate when: the task is simple and one-off with no recurrence; the user is asking…

deciqAI/knowledge-skills · 105 tokens