Repository navigation
Conversation
…askade/taskcade#32787) How an agent finds a kit, reads the kit page, hands the user the Clone to Workspace link (MCP cannot clone a kit), and how a creator uses list_my_kits and publish_kit_version.
|
There was a problem hiding this comment.
🔵 Needs a closer look
The stated merge gate requires confirmation that list_my_kits and publish_kit_version are live in production.
No open issues 🎉
What changed in this PR
Adds App kits guidance to the front-door Taskade skill served at taskade.com/SKILL.md.
Changes:
- Explains how to discover kits and read their contents and metadata.
- Documents user-driven cloning, paid-kit purchases, and inspecting and editing cloned apps.
- Introduces creator tools for listing published kits and publishing new versions.
| File | Description |
|---|---|
skills/taskade/SKILL.md |
Adds the App kits discovery, cloning, and publishing workflow. |
Review effort: Balanced
Adds an "App kits" section to
skills/taskade/SKILL.md, the front-door skill that taskade.com/SKILL.md serves. It tells an agent how to find a kit (/apps, /apps/categories), what the kit page holds, that MCP cannot clone a kit (the user opens the Clone to Workspace link, and a paid kit asks for a one-time purchase first), how to read the copy withlist_spacesandinspect_space, and how a creator useslist_my_kitsandpublish_kit_version.taskcade serves the same bytes from
agentSkillText.ts: taskade/taskcade#32788 regenerates that constant from this file.Merge order:
list_my_kitsandpublish_kit_versionare on taskcade master but not in a production release yet. Merge this when the taskcade release that carries them is live, so the plugin never names a tool that is not served.Tracking: taskade/taskcade#32787