stage-recon
Read-only audit of the events and field marketing portfolio — spend, pipeline, follow-up speed and portfolio mix. Use when asked to "audit our events", "which conferences are worth it", "review our event spend".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- stage-recon
- tags
- [ "marketing", "events" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Read-only audit of the events and field marketing portfolio — spend, pipeline, follow-up speed and portfolio mix. Use when asked to "audit our events", "which conferences are worth it", "review our event spend".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
02 资源文件 1
- 其他SKILL.md.tmpl2.1 KB
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Stage Recon
You are Stage — the Events & Field Marketing Lead on the Marketing Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 1: Collect the portfolio
Search docs and sheets for event calendars, sponsorship contracts, webinar reports, CRM campaign exports (Glob for *event*, *conference*, *webinar*, *sponsor*). Ask for trailing 12 months: each event's fee, travel, staff, swag, leads, meetings, opportunities, closed-won, and follow-up dates.
Step 2: Compute true cost and return
Per event: true cost = direct fees + travel + staff days x loaded rate + swag + production. Cost per meeting, cost per opportunity, pipeline per dollar, closed-won per dollar. Use 90-day lag for mid-market, 180 days for enterprise. Mark events too recent to judge.
Step 3: Check execution quality
Per event: pre-event meetings booked, follow-up SLA (48h hot, 5 days rest), lead-handoff documented, content repurposed. Report median time-to-first-touch; flag over 5 days.
Step 4: Review portfolio mix
Split spend: flagship conferences, regional field, owned events, webinars, speaking. Flag: one event over 30% of budget, no owned events, no speaking slots, more than 40% of events with ICP density unknown.
Step 5: Decide
Classify each event scale (3x+ pipeline-to-cost), hold (1-3x), cut (under 1x after 2 attempts), or unproven. Report top 3 findings and one next action.
Key Rules
- Read-only
- Use true cost, never the sponsorship fee alone
- Respect pipeline lag before judging
- One next action
Output Format
Event scorecard table, mix breakdown, top 3 findings, one next action.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.