Everyone has their own prompts
Know-how lives in people’s heads and chat histories. When someone leaves, it leaves too.
From individual habits to a shared AI workforce: skilder turns the way your teams already use AI into clear roles built on your processes, working alongside your people, monitored and governed.
Pick an AI interface to start.
Hi, I’m skilder. I run your company’s roles inside ChatGPT. Which role should we build first?
Hi, I’m skilder. I run your company’s roles inside Claude. Which role should we build first?
Hi, I’m skilder. I run your company’s roles inside Microsoft Copilot. Which role should we build first?
Hi, I’m skilder. I run your company’s roles inside Gemini. Which role should we build first?
Here’s the Sales role I’d start with:
Skills
Connectors
Here’s the Legal role I’d start with:
Skills
Connectors
Here’s the Support role I’d start with:
Skills
Connectors
Here’s the Ops role I’d start with:
Skills
Connectors
Here’s the Marketing role I’d start with:
Skills
Connectors
Here’s the HR role I’d start with:
Skills
Connectors
Here’s the Finance role I’d start with:
Skills
Connectors
Here’s the IT role I’d start with:
Skills
Connectors
Here’s the Procurement role I’d start with:
Skills
Connectors
Here’s the Product role I’d start with:
Skills
Connectors
The problem
Know-how lives in people’s heads and chat histories. When someone leaves, it leaves too.
You can’t tell who uses what, for which task, or what it actually brings in.
Personal accounts, internal documents pasted into chats: your data moves outside any framework.
AI roles
A role is one of your company’s jobs translated for AI: its procedures, document templates and tools. Build it once, the whole team uses it.
Example roles
Insights
Every use of a role is tracked. You finally know where AI saves time, and what that time is worth.
Illustrative data
| Role | Uses | Time saved | Value |
|---|---|---|---|
| Sales assistant | 412 | 96 h | EUR 8,600 |
| Legal counsel | 287 | 74 h | EUR 6,700 |
| Human resources | 184 | 41 h | EUR 3,400 |
| Marketing assistant | 98 | 19 h | EUR 1,500 |
| User | Roles used | Time saved | Value |
|---|---|---|---|
| Marie Dupont Sales | 4 roles | 28 h | EUR 2,400 |
| Thomas Lambert Legal | 3 roles | 21 h | EUR 1,900 |
| Sophie Berger HR | 2 roles | 12 h | EUR 980 |
| Aline Rochat Back office | 1 role | 7 h | EUR 560 |
| Team | Users | Time saved | Value |
|---|---|---|---|
| Sales | 18 | 142 h | EUR 12,400 |
| Legal | 6 | 74 h | EUR 6,700 |
| Human resources | 5 | 41 h | EUR 3,400 |
| Back office | 3 | 19 h | EUR 1,500 |
Governance
Going from a few users to the whole company takes a framework. skilder builds it in from day one.
Everyone reaches the roles and tools they need. Nothing more.
Every skill has a history. You know what changed, and you can roll back.
Every use is traced, from request to tool call. Ready for your audits.
Hosted in Switzerland by Infomaniak, or installed on-premise in your own environment.
Get started
skilder is agnostic. Your teams keep the AI assistant they know, and skilder connects to it through MCP, the open standard.
Pick your company’s AI assistant, or a model hosted in Switzerland.
We start from two or three priority processes, with your teams.
Roles go live, usage comes back, ROI becomes visible.
Works with your AI stack
And with your ecosystem
Customers
Expert session
30 minutes with an expert, free, no strings attached.
Tell us what you needYou leave with
FAQ
Another question? Ask it on the call, a founder will answer.
Most organisations have bought Claude, ChatGPT or Copilot licences and watched adoption stall, because every employee has to re-explain their job to the AI each time. skilder fixes that. It is a registry and control plane that turns your know-how into governed roles, one per seat on the org chart, assembled from Agent Skills and scoped MCP tools. Employees keep the AI client they already have; the role arrives inside it. skilder adds no new tool to open.
A Claude Skill is a single SKILL.md file: instructions, optional scripts, reference content. It describes one capability and is portable across any agent that reads the standard. A role is the work one seat actually does: it bundles several skills with the MCP tools that seat may reach, its context and its permissions, and serves them on demand to any MCP-compatible agent. The skill is the capability; the role is how that capability runs in your company, versioned, access-controlled and traced.
No, and that is by design. skilder ships blueprints for 60+ functions, from finance to legal to support, and each one is configured to your playbooks, systems and vocabulary before it goes live. Configuring a role from a blueprint takes a few clicks in a visual interface, not code. Engineers are only needed when you want to expose a custom internal system as an MCP server.
A role is the permission boundary: it reaches only the connectors granted to it centrally, those grants are revocable, and they never widen at runtime. Access is governed by SSO and role-based access control, with tenant isolation between workspaces. Every task is logged and attributed to the person who sent it; skilder keeps that execution trace, and you can export or delete it. Hosting is sovereign in Switzerland or the EU, with on-premise available, and LLM providers run under zero-data-retention terms, so your data never trains a public model.
There is a free plan with usage included, so a builder can configure and run a first role before talking to anyone. Paid plans scale with usage, meaning executions, connected tools and governed users, and add enterprise SSO, advanced audit and dedicated support. skilder does not charge per seat, and authoring roles is always free: you pay for what your organisation actually runs.
skilder Factory is the fast lane. The skilder team works beside yours for two weeks: your first roles configured, SSO and permissions set, everything tested on real work, then the keys handed over. Two ways to work together: delegate the build, or have your own champions backed while they ship. The self-serve path stays free and is enough to configure a first role. Durations, scope and prices are on the Factory page.
The blog
Field notes on Agent Skills, MCP and governed AI: what holds up in real deployments, and what quietly breaks.
Agent plugins bundle skills, MCP servers and hooks into one install for one client. A skilder role serves skills and scoped tools to any MCP agent from a governed workspace. How they differ, and when to use which.
Read article →A 30-page white paper tests whether serving skills through one MCP server can enforce what an agent may do. 13 scenarios, six models, three tool interfaces, and the limits the authors report.
Read article →LiteLLM fronts the models, agentgateway fronts the tools and agents, skilder defines the roles an agent performs. What each one governs, where it sits in the request path, and which one to deploy first.
Read article →