Run any Skill in Manus with one click

run-campaign

Stars1

Forks1

UpdatedJuly 17, 2026 at 20:28

Runs an end-to-end marketing campaign — sales analysis, content brief, Canva assets, HubSpot send. Accepts optional lookback and channel arguments.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Jylhis

Jylhis/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	run-campaign
description	Runs an end-to-end marketing campaign — sales analysis, content brief, Canva assets, HubSpot send. Accepts optional lookback and channel arguments.
metadata	{"upstream-id":"anthropics-knowledge-work","upstream-rev":"55447a28e6c785444197cecde5a401b44f830161","upstream-path":"small-business/skills/run-campaign","upstream-imported":"2026-06-20T00:00:00.000Z"}

Run the full campaign pipeline by chaining three skills in order. The owner approves at each handoff — never roll past a gate without explicit confirmation.

Parse arguments:

--lookback (default 90d) — how far back to look for the revenue dip
--channel (default both) — email, social, or both

Step 1 — Sales analysis + content brief

Run the sales analysis and content brief:

Pull sales data from QuickBooks and PayPal for the lookback window.
Identify the revenue dip — which product/service, which time period, magnitude.
Produce a 30-day prioritized content brief: what to push, what offer to run, what to hold.
Present the brief to the owner. Wait for explicit "approved, build the assets" before continuing.

If the owner edits the brief, incorporate edits and re-present.

Step 2 — Asset generation + send staging

After Step 1 approval, generate the campaign assets:

Take the approved brief from Step 1 as input.
Build the posting calendar matched to the brief's priorities.
Generate on-brand Canva assets for each post (apply each on screen for owner approval before moving on).
Draft caption copy for each post.
Stage the scheduled send in HubSpot (do NOT send — staging only).
Present the staged campaign to the owner. Wait for explicit "approved, send to segment X" before Step 3.

Step 3 — Audience segmentation (lead-triage)

After Step 2 approval, trigger the lead-triage skill workflow:

Pull HubSpot contacts that match the campaign's target segment (from the approved brief).
Score by engagement, company fit, urgency markers.
Produce two deliverables:
- Bulk send list — the segment receiving the staged campaign from Step 2
- High-priority call list — top 5 leads the owner should call personally with talking points
Block calendar time for the call list.
Present both lists. Wait for explicit "send" before pushing the HubSpot campaign live.

Approval gates (must hold)

Never auto-progress between steps. Each handoff requires explicit owner approval.
Never send the HubSpot campaign without the owner's "send" command in Step 3.
If any connector is unreachable (QuickBooks, PayPal, Canva, HubSpot), stop, report which connector failed, and ask whether to retry or abort.

Output

End the run with a one-paragraph recap: revenue dip identified, posts generated, segment size, calls booked. Link to the HubSpot campaign URL once sent.

More from this repository

same repository

upstream-tracker

Jylhis/skills

Track external upstream skill repositories: import a skill from upstream into this catalogue, modify it locally without losing the baseline, monitor the upstream for new commits since the last review, and review each upstream commit one-by-one to accept, skip, defer, or cherry-pick it into the local copy. Use when the user says "import skill from <repo>", "vendor <repo>", "monitor upstream for new commits", "what's changed upstream", "check upstream for updates", "review upstream commit", "backport <sha>", or "follow <repo> for new skills". Operates on `upstream/sources.yaml` (manifest), `upstream/decisions/<id>.log` (per-source review cursor), and `.cache/upstream/<id>.git` (local bare partial clone). Helper scripts under this skill's `scripts/` do the deterministic git work; the agent following this SKILL.md drives the decisions.

2026-07-171

business-pulse

Jylhis/skills

Produces a one-page cross-functional business snapshot for SMB owners — cash position (QuickBooks), sales trend (PayPal/Square), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail/Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a weekly summary, a Monday brief, or says anything like "what am I missing" or "catch me up on the business."

2026-07-171

cash-flow-snapshot

Jylhis/skills

Reads AR/AP, historical cash timing, and known fixed costs from QuickBooks, PayPal, Stripe, or Square — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.

2026-07-171

crm-cleanup

Jylhis/skills

Scans HubSpot for stale deals, duplicate contacts, and missing fields, then fixes what the owner approves. Accepts optional scope argument for deals, contacts, or all.

2026-07-171

crm-maintenance

Jylhis/skills

Keeps HubSpot current without the owner opening it: creates and updates contacts and deals from email and calendar context, logs notes and calls, and flags stale records. The 'stop doing data entry' skill. Use when the user asks to update the CRM, log a call, clean up HubSpot, or add context to a deal.

2026-07-171

customer-pulse

Jylhis/skills

Aggregates PayPal disputes, HubSpot feedback and tickets, and email sentiment (plus pasted or exported Google/Yelp reviews) into a themes report with verbatim evidence and a "do these three things this week" list. Use when the user asks how customers are feeling, for review analysis, what people are saying, or about disputes.

2026-07-171

name	run-campaign
description	Runs an end-to-end marketing campaign — sales analysis, content brief, Canva assets, HubSpot send. Accepts optional lookback and channel arguments.
metadata	{"upstream-id":"anthropics-knowledge-work","upstream-rev":"55447a28e6c785444197cecde5a401b44f830161","upstream-path":"small-business/skills/run-campaign","upstream-imported":"2026-06-20T00:00:00.000Z"}

Run the full campaign pipeline by chaining three skills in order. The owner approves at each handoff — never roll past a gate without explicit confirmation.

Parse arguments:

--lookback (default 90d) — how far back to look for the revenue dip
--channel (default both) — email, social, or both

Step 1 — Sales analysis + content brief

Run the sales analysis and content brief:

Pull sales data from QuickBooks and PayPal for the lookback window.
Identify the revenue dip — which product/service, which time period, magnitude.
Produce a 30-day prioritized content brief: what to push, what offer to run, what to hold.
Present the brief to the owner. Wait for explicit "approved, build the assets" before continuing.

If the owner edits the brief, incorporate edits and re-present.

Step 2 — Asset generation + send staging

After Step 1 approval, generate the campaign assets:

Take the approved brief from Step 1 as input.
Build the posting calendar matched to the brief's priorities.
Generate on-brand Canva assets for each post (apply each on screen for owner approval before moving on).
Draft caption copy for each post.
Stage the scheduled send in HubSpot (do NOT send — staging only).
Present the staged campaign to the owner. Wait for explicit "approved, send to segment X" before Step 3.

Step 3 — Audience segmentation (lead-triage)

After Step 2 approval, trigger the lead-triage skill workflow:

Pull HubSpot contacts that match the campaign's target segment (from the approved brief).
Score by engagement, company fit, urgency markers.
Produce two deliverables:
- Bulk send list — the segment receiving the staged campaign from Step 2
- High-priority call list — top 5 leads the owner should call personally with talking points
Block calendar time for the call list.
Present both lists. Wait for explicit "send" before pushing the HubSpot campaign live.

Approval gates (must hold)

Never auto-progress between steps. Each handoff requires explicit owner approval.
Never send the HubSpot campaign without the owner's "send" command in Step 3.
If any connector is unreachable (QuickBooks, PayPal, Canva, HubSpot), stop, report which connector failed, and ask whether to retry or abort.

Output

End the run with a one-paragraph recap: revenue dip identified, posts generated, segment size, calls booked. Link to the HubSpot campaign URL once sent.