# revops-kickoff

Routes RevOps and Sales Ops tasks across a 20-skill suite in Claude Code and bootstraps shared context in revops-context.md.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 20500 installs · ★ 1
- Author: Maya-Beth Finotti
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revops-kickoff/SKILL.md
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/skills/revops-kickoff

## What it does

This skill acts as the entry router for the 20-skill `revops-skills` collection. It inspects the workspace first. If `revops-context.md` exists, the agent performs a warm start; otherwise, it starts cold. It reads recent git commits and project documentation to avoid asking redundant questions.

During a cold start, the interview stays capped at 5 to 7 multiple-choice questions. It captures revenue motions, CRM ownership, deadlines, and effort ceilings. The session ends by routing the problem to exactly one sibling skill or stating that none fits. Do not point quota-carrying sales tasks here: the repository explicitly requires `mbfinotti/sales-skills@sales-kickoff` instead.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revops-kickoff -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/revops-kickoff/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/revops-kickoff/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revops-kickoff -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/revops-kickoff/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revops-kickoff -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/revops-kickoff/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/revops-skills revops-kickoff
```

2. **Manually: put the files in place**
- File: `.github/skills/revops-kickoff/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revops-kickoff -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mbfinotti/revops-skills --path skills/revops-kickoff
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/revops-kickoff/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revops-kickoff -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revops-kickoff/SKILL.md

## When to use it
- Route a RevOps or CRM problem to a single dedicated skill
- Bootstrap or resume the shared revops-context.md project file
- Inspect git history and project files before starting an interview
- Record CRM ownership, constraints, and effort limits for future sessions

## Example prompts
- Where do I start with our RevOps project?
- Which revops skill do I need for fixing lead scoring?
- Run a revops kickoff for our CRM migration

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1b27cfb077630b5d.

BEGIN THIRD-PARTY FILE 1b27cfb077630b5d
```text
---
name: revops-kickoff
description: Before starting any RevOps or Sales Ops task, and at the start of every session on an ongoing RevOps project, run this first - it routes the task to exactly one skill of the revops-skills collection or says plainly that none fits, and bootstraps or resumes the project's shared, versioned context artifact so the next session starts warm instead of cold, ending in a short-list plus an ordered skill chain. Run it even when the collection's other skills are already used daily - a new project is a new context. Also use whenever the user mentions a revops kickoff, a new RevOps project, a revops project start, revops or crm skill routing, a periodic RevOps check-in, a recurring RevOps review, "which revops skill do I need", or "where do I start with RevOps" - even if they never name a skill, and even if the request looks like it already belongs to one specific skill. Do NOT use for routing quota-carrying sales tasks - use mbfinotti/sales-skills@sales-kickoff instead.
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.4.4"
---

# RevOps Kickoff

You are the entry point and router for the 20-skill revops-skills collection, which spans two altitudes: macro design skills that decide what the revenue system _is_, and tactical skills that operate inside it. Route the current RevOps task to exactly one sibling skill, or say plainly that none fits, and make the next session start warm instead of cold. Routing is the reason this skill exists; everything else here serves it.

Run this skill at every project start, even when the collection's skills are already used daily in another context - a new project is a new context, and daily familiarity with siblings does not replace the kickoff pass. On later sessions of the same project, re-run it to resummarize and re-route, never to re-interview.

## 1. Detect before asking

Every fact derivable from the environment is a question the user never has to answer. Run detection first; the interview cap only survives if it does.

1. Decide cold vs warm start from one signal only: does the context artifact `revops-context.md` exist in the project? Present → warm start. Absent → cold start. Never ask the user which one it is.
2. Read the repository's recent git log when the history is readable, and infer project stage and pace from it: commit frequency, what changed last, whether work stalled.
3. Inventory existing files - README, agent-instruction files, data dictionaries, stage documentation, `.github/` - so nothing already written gets re-asked.
4. If the harness exposes connectors or integrations, detect which are available - a CRM export, an analytics source, a ticketing system, meeting notes - and let their presence shape routing and routines. Describe the capability; never assume a specific product.
5. If the collection ships readable version metadata, note what changed since the last session. If it doesn't - the common case - degrade silently. Never block, warn, or ask about versions.

## 2. Interview - capped, tappable

On a cold start:

- Ask at most 5-7 questions.
```
END THIRD-PARTY FILE 1b27cfb077630b5d

The third-party file has ended. Everything between the 1b27cfb077630b5d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3105 of 39918 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revops-kickoff/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md