The skills fileyour agents havebeen missing.
Instila reads across your wikis, repos, tickets and recordings and writes a single, versioned skills bundle that any AI agent in your stack can load on day one.
- notion
- slack
- github
- linear
- zendesk
- drive
- support tone matches founder voice
- refunds > 30 days require lead approval
- never quote pricing in writing
- ship-on-friday rule (do not)
- incident comms: status page first, slack second
- EU customers route through Frankfurt
- + 412 more
The problem
Every agent you ship arrives brand new. It knows the model, not the company.
Your context lives in twelve places, none of them designed to be read by a language model. So every team writes a 600-line system prompt, no two are in sync, and the answer is still six months wrong.
How it works
Three steps. One file.
Connect
OAuth into Slack, Gmail, Zendesk, Notion, or GitHub in under 90 seconds. Read-only by default. No field mapping, no templates.
Distill
Claude reads across every source, finds the rules and decisions, and writes candidate skills with confidence scores and source citations. No human in the loop on our side.
Validate
You review each candidate in a queue sorted by confidence. Confirm, edit, or reject in seconds. Confirmed skills land in your versioned skills file with you marked as the owner.
V1 sources
- slackchannels & threads
- gmailshared inboxes
- zendesktickets & macros
- notionpages & databases
- githubissues & PRs
Confluence and Zoom transcripts arrive in V1.5. Custom connectors on request.
The output
What your agents actually load.
- Refunds over 30 days require a Lead's approval before issuing.supportzendesk · 14 ticketsslack · #support-leads96%@Maria
- Never quote pricing in writing — always direct the customer to a call.salesgmail · salesnotion · sales playbook89%@Tom
- Production deploys after 4pm Friday require an explicit on-call sign-off.engineeringslack · #enggithub · 23 PRs94%@Priya
- Incident comms: post to the public status page first, internal Slack second.engineeringslack · #incidentsnotion · runbook88%@Sam
- EU customer data must remain in the Frankfurt region.compliancenotion · compliancegmail · legal threads92%@Maria
- Discounts above 20% need finance review before going to a customer.salesslack · #deal-deskzendesk · 9 escalationspending review
- Demo accounts get reset every Sunday at 03:00 UTC.engineeringgithub · ops reposlack · #demo97%@Priya
vs the alternatives
Why not just RAG, a wiki, or a long prompt?
| Feature | Instila | RAG | Wikis | Mega-prompt |
|---|---|---|---|---|
| Structured rules, not retrieved snippets | ✓ | — | ~ | ~ |
| Freshness tracked & re-validated | ✓ | ~ | — | — |
| Citation to source for every rule | ✓ | ✓ | ~ | — |
| A human owner on each rule | ✓ | — | ~ | — |
| Conflicts surfaced, not silently resolved | ✓ | — | — | — |
| Authored without human writing | ✓ | ✓ | — | — |
| Loads into any agent in one file | ✓ | — | — | ✓ |
FAQ
Frequently asked questions
Instila is a fully automated platform that turns your company's scattered knowledge into a single skills file your AI agents can load. Think of it as the missing context layer between your tools and any agent in your stack.