AI Connectors · Productivity

skilder

Versioned skills and MCP tools distributed from one governed hub

Listed in Claude · 8 published tools · Community-listed

Overview

What skilder does

Skilder treats agent capabilities as software to be released instead of files to be copied. The listing names the failures it targets: skill copies drifting across repositories, live edits changing behaviour mid-task, tool lists overflowing the context window, and no record of what an agent actually did.

The arrangement is a versioned library where skills are composed with the MCP tools they need, published deliberately, and distributed to every connected agent from one endpoint. Skills load on demand, so instructions, files and tools arrive together only when a task needs them, which is what keeps the tool list short. Community tier.

Who it is for

Teams distributing agent capabilities without copies drifting across repositories.

Tool surface

The endpoint requires credentials, so eight is the listing's own count. On-demand skill loading, partitioned tool execution and governed distribution are the described operations.

Availability

Where skilder is listed

skilder is listed in the Claude connectors directory only. skilder.ai has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.

The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.

Claude listing

In the Claude connectors directory

skilder publishes 8 tools to Claude. That is a mid-sized surface: 37.7% of the 1,253 Claude-listed connectors expose fewer.

The median Claude-listed connector filed under Productivity publishes 12, so this one sits 4 tools below its bucket's median, 278th of 462.

It falls in the 7-10 tools band, which holds 14.6% of the Claude directory.

skilder publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.

Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.

Publisher
skilder.ai
Verification
Community-listed (61.5% of the Claude directory)
Filed under
Productivity
Endpoint
https://app.skilder.ai/mcp
Published tools
8 · 7-10 tools band
Depth rank in Productivity
278 of 462
Snapshot
August 2026

skilder is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality.

In the publisher's words

How skilder.ai describes it

Skilder is a versioned, governed library for your team's agent capabilities: skills composed with the MCP tools they need, published deliberately, distributed to every connected agent from one endpoint. It picks up where prototypes end: skill copies drifting across repos, live edits changing agent behavior mid-task, tool lists overflowing the context window, no answer to "what did the agent actually do?" With this connector, Claude can: • Learn skills on demand: instructions, files, and tools unlock together, exactly when a task needs them • Execute each skill's tools through server-partitioned read and write channels, under each user's own identity • Run skill scripts (Python, TypeScript, shell) sandboxed on your runtimes • Report friction on skills as it works, so you catch decay before users do • Build new capabilities in conversation (workspace admins): discover available tools, then create, compose, and update skills and roles Lifecycle is engineered in: drafts, publishing, version history, rollback. Agents only see the published state, so you can iterate on a skill while it runs in production. Usage is measured per skill: what runs, what fails, what sits unused. Admins curate which tools are exposed, and every session leaves an auditable timeline. Skills use the open Agent Skills format: import existing folders as-is from GitHub or ZIP. Everything stays portable. Setup takes five minutes: connect, sign in or sign up in the consent flow, and a demo workspace is provisioned. Then bring your own skills.

Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.

Nearby

Other Productivity connectors

Coconut Context

A versioned markdown context layer shared by people and agents

Claude

Lace Labs

Team knowledge captured during work and handed to agents

Claude

Nifty

Project creation, search, and status reporting from chat

ChatGPT

Productive

Query projects, time, and finances in Productive

ChatGPT

Stem

Cross-AI memory: store, recall and link decisions and context

Claude

This is an independent catalogue entry compiled by Node8 from skilder's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with skilder.ai, and inclusion here is not an endorsement.

Want your company reachable inside ChatGPT and Claude?

Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.

See how it works