# Starter: a play to share with the team

## What you build

You build rung 5. You take a play that works for you, and you package it as a skill or a routine. A peer can then use the same play on a different export, with no help from you.

A skill is a short file of instructions that Claude follows each time you ask for the play. A routine is a skill that runs on a schedule.

## What you need

- A view, an alert or an action that works in this conversation. Rung 3 is the minimum.
- The `H2-Command-Center` folder.
- A connection to the session site. See [Connect your Claude to the session site](/kit/03-connect-your-claude).

## Pick a play

Pick one play that you do again each week or each quarter. These four plays are good examples.

- **Deal-review questions.** The questions that you ask about each key deal, and the data that Claude reads first.
- **Call prep.** A brief of one page for one account before a customer call.
- **Forecast-call narrative.** The story of the number for the week: closed, commit, best case, gap and changes.
- **QBR outline.** The outline of a quarterly business review (QBR) for one account or one team.

You can also package the alert and the action that you built in the session.

## 1. Write the skill

Send this prompt in the conversation where you did the work. Put the name of your play in the first line.

```
Turn the work in this conversation into a skill for this play: <name of the play>.
Write a short markdown file with these five parts: name, when to use it, inputs, steps, output format.
Name: one short name in lower case with hyphens.
When to use it: one or two sentences that tell a peer when to ask for this play.
Inputs: each file and each column that the play needs. Use the column names from the Salesforce export.
Steps: numbered steps with one instruction in each step. Give each threshold as a number that a peer can change.
Output format: the file name, the sections and the columns of the result.
Add these two rules to the steps: state the export date at the top of each output, and never send a message, only draft.
Do not put an account name, a deal name, an amount or a person's name in the file.
Keep the file to one page. Save it in the H2-Command-Center folder as <name>-skill.md. Show me the file.
```

Read the file. If a step is not how you do the play, tell Claude and let Claude correct it.

## 2. Test the skill

A skill is ready when it works without the conversation that made it. Open a new conversation with access to the same folder, and send this prompt.

```
Read <name>-skill.md in the H2-Command-Center folder. Follow the steps on the newest export in the folder.
Do not ask me a question unless a step is not clear. Tell me each step that was not clear.
State the export date at the top of the output. Do not send a message. Only draft.
```

If Claude asks a question, the answer belongs in the file. Go back to the first conversation and add the answer to the steps.

## 3. Save it as a skill

Ask Claude to save the file as a skill, so that you can call the play by its name.

```
Save <name>-skill.md as a skill that I can use in a new conversation. Tell me how to call it and where you saved it.
```

If you want a routine, follow the steps in [Schedule it](/kit/04-schedule-it). Tell Claude to run the skill on a schedule.

## 4. Post it

```
Post <name>-skill.md to my page as a result of kind "skill", rung 5. Use the name of the play as the title.
Put the full text of the file in the body, so that a peer can copy it.
Add one line at the top: who can use it and which export it needs.
Mark the step "share" as done.
```

## 5. Give it to a peer

1. Ask one peer to copy the skill text from your page.
2. The peer saves the text as a file in the peer's `H2-Command-Center` folder.
3. The peer asks Claude to save the file as a skill.
4. The peer runs the play on the peer's own export.
5. Ask the peer which step was not clear. Correct that step and post the skill again.

## What good looks like

- A peer runs the play on a different export and gets a correct result at the first attempt.
- The file is one page, and each threshold is a number that a peer can change.
- The file holds no customer data, so that you can post it and share it.