HomlaSkills

One playbook for the team. Not twelve different ones.

Save how your best person does a job, right from Claude or Codex. Everyone's AI can use it. It always gets the latest version.

NorthwindSkills
Folder access
Refund reply

How we answer a refund request, with the right tone and the policy.

Supportv3 · Sam
Weekly client report

Pull the week's numbers and write the Monday update.

Client playbooksv7 · Nora
Month-end close

Match PennyLane invoices with Shopify payouts.

Financev4 · Nora
Order lookup

Find an order from a name, an email or an order number.

Supportv2 · Sam
Save this as a skill: Refund replyv3 saved
The problem

Everyone built their own. Now nothing matches.

Each person keeps their prompts in their own account. Everyone else writes a slightly different version. When someone leaves, their way of doing it leaves too.

Same rule, eight copies

The refund rule lives in eight prompts. Someone fixes one. The other seven are now wrong.

Nobody knows what exists

Someone builds a playbook the team already has. Nobody could find the first one.

Too technical for most people

If sharing means code or a terminal, most of the team never touches it.

How skills work

One library of playbooks. The right ones for each role.

Saved from the chat

Say “save this as a skill” in Claude or Codex. It goes into the team library, with folders and search.

  • One command adds the team's skills to Claude Code
  • Agents can use the same skills

Every version kept

See who changed what. Bring back an older version any time. Nothing is deleted.

Folders by role

Finance playbooks stay with finance. Client playbooks stay with the client team.

  • Everyone, or only the roles you pick
  • No role picked: only those who run the account see it
  • A locked folder inside another needs access to both
FAQ

Questions

The ones owners ask about skills.

Start free
Do my people need to learn anything new?

No. They say “save this as a skill” in Claude or Codex. To use one, they ask for it by name.

What happens to a skill when its author leaves?

It stays. Skills belong to the business, not to one person's account. The team keeps using and improving it.

Can some playbooks stay with one team?

Yes. Lock a folder to chosen roles. Everyone else won't see it at all.

What if someone breaks a skill?

Every version is kept. Bring back the old one. The fix reaches everyone at once.

Save your best person's way of doing it.

Start free. Save one playbook. See it show up in everyone's AI.

  • Playbooks the whole team can use
  • One memory every AI reads
  • Each person gets only their access
  • Works in Claude, ChatGPT and Cursor