Request access

Skills runtime

Your team’s skills, served as tools from your own git repo.

Repo in, tools out. Clapcake indexes the skills you keep in git and serves them to your team in Slack, Claude, a dashboard or MCP, and to your customers through a widget on your site.

Request access See how it works

Built by Lead.com. In a pilot with Aftermarket.com.

Repo in, tools out Your git repo holds your skills as folders. Clapcake indexes them with search, versions, grades and receipts. Then it serves them as tools: Slack, Claude, a dashboard, MCP and a site widget today, and next, customers' own Claude, ChatGPT or Grok. REPO IN Your git repo Skills as files you own main skills/refund-policy/ skills/order-lookup/ skills/new-hire-setup/ CLAPCAKE INDEX Clapcake Indexes every skill in the repo Search Versions Grades Receipts TOOLS OUT Served as tools For your team and your customers Slack Claude Dashboard MCP Site widget Next: their Claude, ChatGPT, Grok
Your skills stay in git. Clapcake indexes them and serves them as tools.

How it works

Ask, capture, ship

A question your skills can’t answer yet is a skill worth having. Clapcake turns those misses into tools, and your team approves each one.

  1. Ask

    Someone asks in chat. If no skill covers it, the miss becomes a tool request.

  2. Capture

    A draft skill is written from the request, ready for your team to review.

  3. Ship

    Your team approves the draft, and the tool goes live.

From a missed question to a live tool

Ask, capture, ship Step 1, Ask: a question in chat, "Can I move my delivery date?", has no skill yet, so it becomes a tool request. Step 2, Capture: a draft skill is written from the request. Step 3, Ship: a teammate reviews it, and the tool goes from In review to Live. 1 Ask A question in chat has no skill yet “Can I move my delivery date?” Tool request 2 Capture A draft skill is written from the request skills/delivery-date-change/ Draft 3 Ship Your team approves it, and the tool goes live D Dana Support lead In review Live
Nothing goes live until someone on your team approves it.

Who it’s for

Same skills, two kinds of tools

Clapcake keeps one index of your skills. Your team and your customers each get tools from it, in the places they already use.

  • Your team: skills as tools in Slack, Claude, the dashboard and over MCP.
  • Your customers: a widget on your site today. Next, their own Claude, ChatGPT or Grok, over MCP. Coming next
  • One index behind both, so your team and your customers draw on the same skills.

One index, team tools and customer tools

Same skills, two kinds of tools One skills index feeds two sets of tools. Your team gets Slack, Claude, the dashboard and MCP. Your customers get a site widget now, and next, their own Claude, ChatGPT or Grok over MCP. SAME SKILLS One skills index Search, versions, grades and receipts refund-policy order-lookup new-hire-setup TEAM TOOLS Your team Where they already work Slack Claude Dashboard MCP CUSTOMER TOOLS Your customers Site now, MCP next Site widget Now Their Claude Next Their ChatGPT Next Their Grok Next
Tools marked Next are coming, not live yet.

Site widget

What your customers see

The widget sits on your site and serves your skills as tools, right next to the page they’re about. This preview was designed for the Aftermarket pilot, on their Markets page.

  • Ask about the page. Answers use the page and the customer’s signed-in account.
  • Type / for tools. Every tool comes from a skill in your repo.
  • No tool yet? The question goes to your team as a request. Once they approve the new tool, it shows up in the widget.
  • Light or dark, it follows your site’s theme.

Try it

A working preview with example data. Run a tool, or type / to see them all.

Why not just ChatGPT, Glean or a support bot?

Your skills stay yours

They live in your git repo, not in a vendor’s workspace. Leave Clapcake and you keep every skill.

One set of skills, inside and out

Your team and your customers use the same skills, so answers in Slack and on your site come from one place.

Misses become tools

When chat can’t answer, the question becomes a tool request. Your team approves the draft, and it goes live.

Trust

Your git repo stays the source of truth

Clapcake serves what is in your repo, checks it before it goes live, and shows where each answer came from.

Git is the record

Every skill is a file in your own repo, with its history in git. Clapcake indexes it; your repo keeps it.

Scanned before live

Skills are scanned before they go live to your team or your customers.

Citations and versions

Answers cite the skill and version they came from. Each skill keeps its versions, grades and receipts in the index.

Pilot Aftermarket.com is piloting Clapcake. Early days, so no numbers here yet.

Put your team’s skills to work.

Request access to try Clapcake with your own skills repo.

Request access