capture-work-in-skilder
Installation
SKILL.md
Turn what the user provided into the right building blocks in their Skilder workspace: a skill, several skills, a role (what the outward copy calls a plugin), an App, or a new version of something that already exists. The shape is a judgement call made with the user, not a fixed format.
What this skill is
| Applies when | The Skilder tools are listed, the user wants work made repeatable in Skilder, and the user is a workspace admin (the manage tool is in the tool list). |
| Source | Only what the user points at: this conversation, text they pasted, a file or link they named. Nothing else is read. |
| What flows out | What the user approves in the build summary, to the chosen workspace. |
| What flows in | The workspace's roles, skills, Apps and tools, to reuse them and avoid duplicates. |
| Review | A short build summary is approved in the conversation before anything is created. Skills and roles land as drafts; publishing them stays a human step in Skilder. |
Step 1: be connected
If no Skilder tool is listed, follow the connect-to-skilder skill first. Then call init_skilder with a summary such as "turn this procedure into reusable workspace capabilities", and keep the session id for every other call.
If manage is not listed, say that building in the workspace needs a workspace admin, and offer to write the build summary and the skill text here for the user to hand to their admin.