Live in the first week.

Day 1: the walkthrough

Thirty minutes. You bring one team and one task they keep redoing: renewal briefs, account research, escalation answers, the weekly report. We show you the exact path from that repeated work to an approved skill, on your use case, not a canned demo.

Week 1: your first approved skills

We work hands-on with the person who already does the task best. They describe the method in plain English, knacks drafts the skill with examples and tests, and the team lead reviews and approves the exact version. Only then does it ship to the team's Claude. You end the week with two or three skills your company actually stands behind, not a strategy deck.

After that: the loop runs from Claude

People publish what works, team leads approve what ships, and every skill keeps a named owner, a version history, and a changelog. When the owner improves a skill, the whole team is on the latest version. Nobody adopts a new app at any point: employees, reviewers, and teams stay in Claude.

What you need

• A Claude Team or Enterprise plan for the people who will run the skills.
• A private GitHub repository your company owns, where approved skills live as plain files. We connect through a scoped app; employees never need GitHub accounts.
• Thirty minutes from the team lead who will approve the first skills.

What we never need

Access to anyone's chats or screens, usage tracking of any kind, or a seat in your daily tools. Publishing is a deliberate act, and nothing enters knacks unless someone chooses to send it.