Export one skill as an Agent Skills zip package
Any workspace role may export; a key needs read:skills. Streams the skill’s published state as an Agent Skills package: <skill-name>/SKILL.md, every related resource at its folder path, declared empty folders, and — when present — the mcp.json (suggested servers) and SKILDER.json (resource descriptions, suggested tools, App names) sidecars. The skill’s Apps sit beside it under apps/<name>/ (app.html, SKILDER.json) when the key may read them (read:apps). Downloadable resources with no uploaded file yet are left out.
apiKeyAuthorizationBearer <token>Workspace API key (SKA_...).
skillId*stringSkill id
1 <= lengthThe skill package as a zip
response?fileapplication/zipbinarycurl -X GET 'https://app.skilder.ai/api/v1/skills/0x1a2b/export'"string"Export several skills as one zip bundle GET
Streams a zip holding one Agent Skills package folder per skill (published state only). Any workspace role may export; a key needs `read:skills`, and `read:roles` too when filtering by `roleId`. Filter with exactly one of `ids` (comma-separated, max 100) or `roleId` (every skill of that role). All-or-nothing: any id that does not resolve in the key’s workspace fails the whole request with 404. Folder-name collisions inside the bundle get numeric suffixes (`report`, `report-2`, …). A role with no skills yields an empty zip. Downloadable resources with no uploaded file yet are left out of their package. Every App the skills attach is written once under `apps/<name>/`, and no skill folder is named `apps` then; Apps travel only when the key may read them (`read:apps`).
Release notes
What changed in Skilder, newest first.

