Systems Lab

Agent skill

event-to-pipeline

Turn a conference, meetup, or event you attend or host into booked calls.

activeSelf-containedInstructions only402 words

Filed under ABM and paid.

From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03

What it does when it runs

Turn a conference, meetup, or event you attend or host into booked calls. Trigger when the user is about to attend or host an event, asks how to "work the room", or names an upcoming conference/meetup.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about event-to-pipeline

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os
git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/event-to-pipeline"
mkdir -p ~/.claude/skills/event-to-pipeline
cp -R "/tmp/claude-code-growth-os/.claude/skills/event-to-pipeline/." ~/.claude/skills/event-to-pipeline/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/event-to-pipeline/SKILL.md, which is licensed MIT (repository). 402 words, 3 headings.

Event → Pipeline

An event is for booking calls, not holding them. In a room of 30–50 people you can't run real conversations on the floor — the win is a short, specific touch that ends in a call booked two or three days out.

  1. Lead with a call-earning offer, not a pitch. Offer one small, genuinely useful thing that makes a 15-minute call worth their time — an outline of where you'd start, a teardown of one thing, a second opinion. Frame it as your read, hedged ("where I'd start"), never their numbers. If you limit it, make the limit true — it costs real prep hours, so "I can only do a few of these properly" is honest; an invented "only 5 spots" is not.
  2. Book the next step on the spot. Keep a QR code to your booking link on your phone. "Worth 15 minutes Thursday?" + scan now beats "I'll follow up." Know your week well enough to offer two concrete slots.
  3. Discern fit fast. Sort each person as you go: a fit worth a call, a wrong-fit to be warm to and move on from, or someone whose need is a different offer than the one you lead with. Don't spend a room's worth of time on the biggest logo if they can't buy what you do.
  4. Don't over-send afterward. A document emailed before the call gives a busy person a reason to say no alone. Get them on the call first; material follows.
  5. Follow up within 48–72h, while they still remember meeting you. A warm, in-person lead outranks anything on your cold list — work these first.

When they hesitate (Chris Voss, Never Split the Difference)

"Let me think about it" → a calibrated question, then silence: "That's fair — what specifically would you want to think through?" Calibrated questions start with What or How, never "why". Don't let them set the agenda by deferring to email — name the next step and put it in the calendar.

Bring your own proof and your own voice; don't fabricate offers, names, or numbers.

Depth

  • quick: the call-earning offer + the one-line ask to book.
  • standard: the full play above, tuned to this event (who's likely there, the offer, two slots).
  • deep: + a per-segment sort (prioritise vs be-warm-and-move-on) and a 48–72h follow-up note ready to send.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what event-to-pipeline does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.