# Use the Catalog

> Find the ways your firm uses AI and start one in your own Claude or ChatGPT. Admins add use cases from Claude, and the review shows every prompt before it goes live.

The Catalog is your firm's own list of the ways your team uses AI. Each card is one use case: what it does, how the team uses it, and up to three starter prompts that work as they are. Open **Cookbook** in the sidebar, and the Catalog is the first tab.

The second tab, **Corridor Cookbook**, holds 13 ready-made skills for Claude that we write, the same for every firm. The Catalog is the one your admins fill in.

## For everyone

### Find a use case

<div class="page-clip"><video src="/docs/videos/catalog/find.mp4" poster="/docs/images/catalog/find-poster.jpg" autoplay muted loop playsinline aria-label="On the Catalog tab of the Cookbook page, pointing at a card marked Trending, then picking the Operations group from the chips above the cards, then back to All." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

Open **Cookbook** in the sidebar, then the **Catalog** tab. The cards your team uses most in the last 30 days come first.

- **Groups:** once the Catalog has enough cards, chips above them filter by group, such as Finance or Operations. A group gets a chip once it has three use cases. The rest sit under **Other**.
- **Trending:** up to three cards your team started or copied most in the last 30 days are marked **Trending**.

If your firm hasn't added any use cases yet, the Catalog says so, and **Open the Corridor Cookbook** takes you to the 13 skills instead.

### Start a use case in your AI

<div class="page-clip"><video src="/docs/videos/catalog/start.mp4" poster="/docs/images/catalog/start-poster.jpg" autoplay muted loop playsinline aria-label="Opening a card in the Catalog and pressing Try in Claude under the first starter prompt, then closing the card." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

1. Click a card to open it. You see what it does, **How the team uses it**, and its starter prompts.
2. Under the prompt you want, press **Try in Claude** or **Try in ChatGPT**.

**Try in Claude** opens a new chat with the prompt filled in, so you can read it and press send. **Try in ChatGPT** opens a new chat and sends it right away. It runs in your own AI, with your own connectors, so read the prompt first.

### Copy a prompt

<div class="page-clip"><video src="/docs/videos/catalog/copy.mp4" poster="/docs/images/catalog/copy-poster.jpg" autoplay muted loop playsinline aria-label="On an open card, pressing Copy under a starter prompt. The button changes to Copied." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

To use a prompt somewhere else, like a chat you already have open, press **Copy** under it. The button says **Copied**, and the prompt is ready to paste.

### Suggest a use case

Not an admin? Copy [the prompt](#the-prompt-in-full) from this page, run it in Claude, and send the block Claude gives you to your admin. They review it and publish it.

## For admins

Only admins can add, edit, hide or remove use cases. Anyone can run [the prompt](#the-prompt-in-full), and someone who isn't an admin can send you the block Claude gives them.

### Add use cases from Claude

<div class="page-clip"><video src="/docs/videos/catalog/add.mp4" poster="/docs/images/catalog/add-poster.jpg" autoplay muted loop playsinline aria-label="Pressing Add use cases on the Catalog tab. Pasting the block from Claude under Paste what Claude gave you and pressing Continue. Check what Claude found opens." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

1. On the Catalog tab, press **Add use cases**.
2. Under **Run this in your Claude**, press **Open in Claude**. It opens a new chat with the prompt filled in. Press send. You can also press **Copy** and paste the prompt into a chat yourself.
3. Claude asks which skills you want to share. A skill is a folder of instructions, and sometimes scripts and files, that Claude loads when a task needs it, so it does the job your firm's way. Type the names of the skills you use, then pick how you use each one.
4. Claude replies with one line and one block. Copy all of it.
5. Back in the Catalog, paste it under **Paste what Claude gave you** and press **Continue**.

One paste can hold up to 100 use cases. To add one by hand instead, press **Type one in**, fill in the form and press **Done**. It joins the review below.

### Review every prompt, then publish

<div class="page-clip"><video src="/docs/videos/catalog/review.mp4" poster="/docs/images/catalog/review-poster.jpg" autoplay muted loop playsinline aria-label="On Check what Claude found, one use case is flagged and starts unticked. Reading it, ticking it, and pressing Publish 3 use cases. The new cards show in the Catalog." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

After you press **Continue**, you see **Check what Claude found**, with each use case and its prompts in full. Corridor Context can't judge whether a prompt is safe, and your team runs it with their own connectors, so read every prompt before you publish.

- Each use case is marked **New**, **Changed**, **No change** or **Needs details**. **Needs details** can't be ticked until you add what's missing with **Edit**. **No change** has nothing to publish.
- A use case starts unticked if it names a person, says I, you or we, contains a link, uses a group that isn't on your list, or changes a prompt that's already live. Read it, fix it with **Edit** if you need to, then tick it.
- Only ticked use cases are published. The button counts them, such as **Publish 3 use cases**. Press it, and your team sees the new cards right away.

Use cases match by skill name, so running the prompt again next week updates the same cards instead of adding new ones.

A starter prompt that names a skill only works for teammates whose Claude has that skill. Before you publish, share the skill with your team in Claude. On Claude Team and Enterprise plans, an organization owner can provision a skill for everyone from organization settings, or let members share skills with each other.

### Edit, hide, remove and restore

<div class="page-clip"><video src="/docs/videos/catalog/manage.mp4" poster="/docs/images/catalog/manage-poster.jpg" autoplay muted loop playsinline aria-label="On an open card, pressing Hide from team. The card moves under Hidden from the team. Then pressing Remove and confirming. Under the cards, the Removed list shows it, and pressing Restore brings it back under Hidden from the team." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

Open a card. As an admin, you see who added it and when, and three buttons:

- **Edit:** change the title, what it does, how the team uses it, the starter prompts (up to three), the group and the picture. Press **Save**.
- **Hide from team:** nobody else sees it, but you still do, under **Hidden from the team**. **Show to team** puts it back.
- **Remove:** takes it away for everyone, once you confirm. To bring it back, open **Removed** under the cards and press **Restore**. It comes back as it was: a card that was hidden when you removed it stays hidden until you press **Show to team**, and a card whose group no longer exists comes back under **Other**.

### Organize groups and pictures

<div class="page-clip"><video src="/docs/videos/catalog/groups.mp4" poster="/docs/images/catalog/groups-poster.jpg" autoplay muted loop playsinline aria-label="Opening the ... menu and Edit groups, adding a group called People, then Save. Then editing a card, pressing Change icon, searching for lease and picking a picture." width="1536" height="1080"></video><div class="page-clip-bar" aria-hidden="true"><span></span></div></div>

Open the **...** menu beside **Add use cases** and choose **Edit groups**. Your firm can have up to five groups, plus **Other**, which is always there. Claude picks from this list when it writes your use cases.

- Rename a group by typing over its name, and its cards move with it.
- **Remove** a group, and its cards move to Other.
- **Add a group**, then press **Save**.

Every card gets a picture from our library. Claude suggests one when it writes the use case. To change it, press **Edit** on the card, then **Change icon**, and search by job or word, such as rent, invoice or hire.

## The prompt, in full

This is the prompt the **Copy** button gives you. Your copy lists your firm's own groups in place of the five shown here. If a block names a group your firm doesn't have, the review flags it and you pick one of yours.

```text wrap
I want to share an AI skill I use with my team, on our Corridor page. Help me in three short steps.

Before you start: load my Corridor Context if it is connected. That tool is allowed.

One thing is not allowed: do not call any tool that looks up or lists skills, and do not show a skills card. You already know which skills are turned on in this chat. Use only that.

Step 1. Ask me one short question in the chat: "Which skill do you want to share? Type its name. You can name more than one." Do not list my skills. Wait for my answer. If a name I type matches no skill you know, tell me and ask again. If I say I do not remember the name, show me at most eight skills that I used in recent chats, as a short numbered list.

Step 2, right after I name the skills: use your tool that asks the user a question with choices to click (the "ask user question" tool). Do not ask in chat when that tool can do it. For each skill, ask: "How do you use <skill name>, day to day?" Offer three short, likely answers that you take from what that skill does. I can pick one or write my own.

Step 3. Write one entry for each skill. A teammate who has never used it reads it. Write every field like a label on a tool: no "I", "you" or "we". Start each line with a verb or a noun. Turn my answers into that form, for example "I use it on Mondays when a new partner signs up" becomes "Used on Mondays when a new partner signs up." The starter prompts are the one exception: a person sends them to Claude as their own words, so keep "me" in them. Each starter prompt must work when someone sends it as it is.

Write for any teammate, not for me. Never use my name or any person's name, even if the skill's own description has one. Where the skill says a name, write "the writer" or "the user" in the fields, and "my" in the starter prompts. For example, a skill described as "Rewrites prose in Dana's voice" becomes "Rewrites a draft in the writer's own voice", and its starter prompt says "Rewrite this in my voice." Use plain words that a new employee would understand. Do not invent anything. If you do not know a detail, leave it empty.

Your last reply has two parts, in this order, and nothing else.
First, one line in plain words, before anything else: "Done. Copy the block below and paste it into your Corridor page, under Add use cases. Not an admin? Send the block to your Corridor admin."
Second, one code block in exactly this JSON shape:

{
  "corridor_use_cases": 1,
  "made_on": "YYYY-MM-DD",
  "use_cases": [
    {
      "name": "the exact skill name",
      "kind": "skill",
      "title": "Draft a weekly report",
      "line": "Turns call notes into a one-page brief.",
      "how_we_use_it": "Used on Mondays when a new partner signs up.",
      "prompts": [
        { "title": "A short label", "prompt": "Use the <name> skill. Then the request in plain words. End with one sentence that asks me for the details you need, for example: Ask me for the partner's name before you start." }
      ],
      "group": "One of: Client service, Finance, Operations, Sales, People, Other.",
      "icon_words": ["chart", "envelope", "calendar"]
    }
  ]
}

Rules:
- "title": five words or fewer, starts with a verb.
- "line": says what it does, in 14 words or fewer.
- "how_we_use_it": one or two short sentences, from my answer.
- "prompts": two or three for each entry. No square brackets and no blanks. End each one with a sentence that asks for the details you need.
- Do not write "I", "you" or "we" in any field except "prompts".
- No person's name in any field or prompt.
- "kind": skill, project or connector.
- "group": pick one from the list in the shape. Do not make a new one.
- "icon_words": three plain nouns that could be a small picture for this entry.
```

---
Source: https://www.corridorcontext.com/docs/catalog/
