stage-pick
Evaluate and select conferences and sponsorships with ICP density, true cost, expected pipeline and a go/no-go call. Use when asked to "should we sponsor this conference", "pick which events to attend", "evaluate this sponsorship".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- stage-pick
- tags
- [ "marketing", "sponsorship" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Evaluate and select conferences and sponsorships with ICP density, true cost, expected pipeline and a go/no-go call. Use when asked to "should we sponsor this conference", "pick which events to attend", "evaluate this sponsorship".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
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 Pick
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: Qualify the audience
Request the organizer's attendee breakdown: titles, company size, industry, buyer vs. practitioner, repeat rate. Match against ICP and the target-account list. Compute ICP density and top-100 account overlap. Below 15% density or fewer than 15 target accounts: no-go unless an owned side event is possible.
Step 2: Price the real cost
Fee x 2.5-3 as a default, or itemize: fee, booth build, shipping, travel for N staff, staff days x loaded rate, swag, lead retrieval, follow-up programs. Ask the organizer what is negotiable: sponsor-only meeting lists, speaking slot, discounted second year.
Step 3: Estimate return
Expected meetings = target accounts present x expected meeting rate (25-40% with pre-outreach). Expected opportunities = meetings x 25-35% conversion. Pipeline = opportunities x average opportunity size. Compute pipeline-to-cost. Go if 3x+, conditional if 1.5-3x, no-go under 1.5x.
Step 4: Choose the format
Compare formats for the same money: booth, speaking slot, hosted dinner (15-25 people), after-party, private room. Default to hosted or speaking when the show is large and generalist.
Step 5: Commit with conditions
Go decisions need: owner, target list, 10+ pre-booked meetings by T-14 days, follow-up sequence drafted, handoff SLA agreed with Sales. Write the cancel criteria and the date.
Key Rules
- ICP density before size
- Price at 2.5-3x the fee
- Prefer speaking and hosted formats at generalist shows
- No go without an owner, a target list and a follow-up plan
Output Format
Go/no-go scorecard: density, true cost, expected pipeline, pipeline-to-cost, format, conditions.
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.