import-skills-to-skilder
Move the user's existing local Agent Skills into their Skilder workspace. Skills use the open Agent Skills format on both sides, so content imports as-is: frontmatter and body stay what they are.
What this import is
| Applies when | The Skilder tools are listed and the user is a workspace admin (the manage tool is in the tool list). |
| What flows out | The SKILL.md files and companion files the user approves, verbatim, to the chosen Skilder workspace, where they become draft skills. |
| What flows in | The workspace's existing skill names, to detect duplicates. |
| What stays local | The original files, untouched. Files that look like secrets are skipped and never sent. |
| Review | Imported skills land as drafts in the workspace library. Publishing them is a human step in Skilder. |
Step 1: be connected
The Skilder MCP server has to be listed with its tools. If it is not, the connect-to-skilder skill covers that step (one endpoint, browser sign-in, no keys).
Then call init_skilder with a one-sentence summary such as "import this machine's local agent skills into the workspace", and keep the session id it returns: every other Skilder call takes it as sessionId.
Importing uses the manage tool, which Skilder lists to workspace admins. The first user of a workspace is its admin, so a user on their own workspace qualifies. If manage is not in the tool list, say that the import needs a workspace admin and stop.