Skip to main content
Live on DevHunt Vote for us →
skilder

The shared skills workspace for humans and agents.

Your teams’ agent skills are scattered across Notion pages, shared drives and GitHub repos. skilder operates them in one place, with clear owners, traced usage and instant updates to every agent.

This is a live demo: click around.

Sample data · Norvane Logistics is fictitious

Works with

  • Claude
  • ChatGPT
  • Copilot
  • Gemini
  • Cursor
  • Any MCP client

Today

Every agent has its own copy.

The same skills, connectors and apps, set up again for each agent. Each copy has its own versions, access rules, guardrails and activity.

With skilder

One layer between your agents and your systems.

The agent brings the model and the chat. Your systems hold the data. skilder sits in between, with the capabilities your agents call and the controls around them.

What skilder does

Orchestrate your AI capabilities. Keep them yours.

01 · Know what you have

Every capability your agents use, in one place.

These are your AI capabilities: what your company knows how to do. Teams bring in the skills and connectors they already have. From then on each one has an owner, a version and a list of who may use it.

02 · Keep it up to date

Change a capability without breaking what depends on it.

A capability nobody maintains goes wrong quietly. skilder shows what needs attention and what a change touches, and publishes the fix to every agent.

03 · Get it to every team

Connect an agent once. Every team gets its plugins.

Try a plugin, decide who gets it, then add skilder to an agent once. Each person gets the plugins they are allowed to use.

04 · Stay in control

Stop what your agents should not do. Know what they did.

Guardrails can block a tool call. Every call is recorded per user. You set the time one skill use saves, and skilder adds it up.

Security

Built to pass your security review.

01

How agents get in

Authentication

OAuth 2.1 with PKCE. Each token belongs to one person and one workspace, so there is no shared key.

Token lifetime

Access tokens last one hour. Refresh tokens rotate at every use, and a replayed one revokes the connection. Anyone can revoke their connected agents.

Single sign-on

People sign in through your identity provider, with OIDC or Microsoft Entra. On the Enterprise plan.

Key storage

API keys and tokens are stored as hashes only. A key is shown once, when it is created.

02

What they can reach

Credentials

The credentials of your systems are encrypted with AES-256-GCM. They never appear in a tool definition or a result, so the agent and its model never see them.

User permissions

Each person can connect their own account to a system. Calls then run with that person’s rights, not a shared service account.

Least privilege

A skill’s scripts can call only the tools attached to that skill.

Off switch

Turn off a connector, a tool, a skill or a plugin. It applies from the next call.

03

Where it runs

Workspace scope

Every request is tied to one workspace, and permissions are checked on each request.

Hosting

In Switzerland, at Infomaniak. On-premise on request.

Compliance

GDPR and Swiss FADP. A DPA is available and the subprocessor list is published.

Data deletion

Deleting a workspace purges all its data.

See the Trust page →

Customer cases

Connected once, used across the company.

  • Branch secretariat

    Services

    The problem

    The form data lived in scattered databases, and each branch had its own way of reconciling it.

    With skilder

    The databases are connected once, and one forms plugin serves the agent of every branch.

    300+ forms a month

  • On-site drilling crews

    Construction

    The problem

    Every crew kept its own copy of the drilling reference, and site reports had no common format.

    With skilder

    The drilling reference and the site-report format are two maintained skills. An update reaches every crew at its next use.

    50+ sites

  • Product team

    Fintech (SaaS)

    The problem

    Each new business-process check needed IT to build and run it.

    With skilder

    The systems are connected once. The product team builds and runs its validation pipeline itself.

    End to end business-process validation

Customers and partners

OrllatiIDRHEquallMemowaysFutura21ADOPT-AI

FAQ

Questions AI owners ask

Before they bring their capabilities in.

  • What is skilder?

    skilder is the workspace where a company maintains its AI capabilities (skills, tools and apps, bundled into plugins) and distributes them to the agents its teams already use. Each capability has an owner, versions, access rules and a record of every call.

  • What about the skills and connectors our teams already use on their own?

    skilder does not scan laptops or chat accounts. It records what is served through it. Teams bring in the skills and MCP servers they already have, in their standard formats, and from then on they are managed in the workspace like everything else.

  • Is skilder an AI assistant?

    No. Claude, ChatGPT, Copilot or another MCP client is the assistant. skilder supplies the capabilities it calls, and the controls around them.

  • Do we have to replace what we built, and are we locked in?

    No to both. skilder works with the open standards: skills in the Agent Skills format, tools as MCP servers, and MCP Apps. Bring what you have and keep the agents you use. Nothing is tied to a format of ours.

  • How is skilder different from a skills marketplace or a shared repo?

    A marketplace or a repo stores files, and each person installs a copy. skilder serves the published version live at each call, applies access rules and guardrails, and records what was called. When you fix a skill, there are no copies left to chase.

  • How do we know it is being used?

    Three places. Activity records every call, per user. Insights lists the skills nobody uses and the tools that fail. And if you set the minutes one use of a skill saves, skilder adds up the time given back.

  • What happens if we change AI assistant?

    Your capabilities live in skilder, not inside one assistant. Connect the new assistant and it loads the same plugins, under the same access rules and guardrails.

  • Who decides who can use what?

    You set, for each plugin, who can use it and who can edit it. Every call is recorded per user, and the audit log can be exported.

  • Where does skilder run?

    Hosted by skilder in Switzerland (Infomaniak) or the EU, as a dedicated instance in your private cloud, or in your data centre on request.

  • How do we start?

    Start free. An engineer brings one skill and one MCP server, bundles them into a plugin and connects the agent the team already uses. The docs walk through each step.

Bring one skill and one connector.
See every agent pick them up.

Start free with one team and one capability. The docs show you how, step by step.

Supported by