connect-to-skilder
Installation
SKILL.md
Connect this agent to the user's Skilder workspace. One endpoint, one browser sign-in, no workspace name or key to collect.
What the connection is
| Server | https://app.skilder.ai/mcp, Streamable HTTP, operated by skilder.ai SA (privacy, terms). |
| Sign-in | The first request opens a browser page on app.skilder.ai. The user signs in, picks one workspace and presses Approve. Nothing is granted before that press. |
| Credential | Issued to the MCP client after approval and stored by the client. This agent never sees, stores or forwards it. |
| What flows out | The tool calls this agent makes against the chosen workspace, recorded there for the workspace admins. |
| What flows in | The roles and skills the workspace's own admins published for it. Workspace content, available only after approval. |
| Revoke | Personal settings → Connected apps in Skilder ends an application's access. Removing the server entry from the client configuration stops that client from using the grant. A grant that goes unused lapses on its own after 14 days. |
Step 0: already connected, or already configured?
Skip to Step 3 when the available tools already include one from Skilder (the session-initialisation tool that lists the workspace's roles).
If this skill came with the Skilder plugin, the plugin has already configured the server, under the name skilder. Do not add a second entry. When its tools are not listed yet, the client has not signed in to it: tell the user to authenticate that server in their client (Claude Code: /mcp, then the skilder server), then go to Step 3.