A recipe your team and your agents can share
A Skill packages a prompt, the tools it uses, and the policies it inherits, into a named unit. Humans invoke it the same way agents do.
Anatomy of a Skill
Read a contract, flag clauses against the house playbook, return a review memo.
Read a contract, flag clauses against the house playbook, return a review memo.
- filecontract PDF or DOCX
- collectionplaybook House playbook
- No external retrieval
- EU data residency
- Redact PII in outputs
{ memo, clauses[], risks[] }Humans and agents run the same recipe
A Skill is defined once. A person invokes it by name in the chat. An agent calls it when the loop needs it. The Space, the tools, and the guardrails are identical either way.
- Owners can version a Skill without breaking the callers.
- Every invocation lands in the same audit trail.
- Guardrails apply whether the caller is human or agent.
Why a Skill beats a prompt you paste around
Hardcoded prompts and custom GPTs are a start. A Skill packages the tools and the policies with them, so it actually works in a regulated setting.
Skills people already run
Small, named, reusable. Each one a building block for the loop.
Flag clauses against your playbook. Return a review memo.
Score an incoming deal against your investment criteria. Return a memo and a score.
Read a ticket, classify it, draft a reply, attach the policy that applies.
Read a regulatory filing, flag new requirements, assign owners.
Read the invite, pull the relevant Collection, draft a briefing.
Write a close-out memo from the Space's history at the end of a project.
Define, package, share
Three steps. No special IDE needed.
Define the recipe
Write the prompt, pick the tools, inherit the Space's policies. Declare the inputs and the output shape.
Package as a Skill
Name it, describe it, version it. The manifest lives in the Space.
Share with the Space
Every member and every agent in the Space can invoke it by name. Every call is in the audit trail.
Early access for design partners
We work with partners on the first set of Skills, then open authoring more broadly. Want to help shape it?
Turn your best prompts into Skills.
Book a demo or tell us which workflow your team keeps repeating. We'll package the first Skill with you.