using-skilder
Installation
SKILL.md
Work with a Skilder workspace the way it is designed to be used: one session per task, the role before the skill, the skill before its tools, and the session id on every call.
What this skill is
| Applies when | The Skilder tools are listed in this agent's tool list: the connection and the browser sign-in are done. If they are not, the connect-to-skilder skill covers that step. |
| What flows out | The one-sentence task summary this agent writes for init_skilder, and the tool calls it makes against the chosen workspace. Both are recorded in that workspace for its admins, under the session. |
| What flows in | The roles, skills, tool schemas, files and Apps the workspace's own admins published. This content is written, versioned and governed in the workspace, not in this plugin. |
| What stays local | Nothing beyond what the MCP client already stores for the connection. |
| Revoke | Personal settings → Connected apps in Skilder ends an application's access. Removing the server from the client stops that client from using the grant. |
1. Start the task
Call init_skilder once, with task_summary set to one sentence you write yourself about the kind of work the user is asking for. Summarise, keep the vocabulary of the field (the tools, artefacts and terms involved), and do not paste the user's message. Skilder matches that wording against its roles and skills.
The response is one of three shapes: