Update to Knotr

{
  "description": "Discover and run Knotr profile skills over MCP (list_skills, get_skill), and know when to write them back with create_or_update_skill. Use when the user wants profile skills, commands, or subagents without syncing a full IDE skill bundle. Prefer knotr-save-skill when the user explicitly wants to persist.",
  "included_files": [],
  "name": "use-knotr-skills",
  "skill_md_contents": "---\nname: use-knotr-skills\ndescription: >-\n  Discover and run Knotr profile skills over MCP (list_skills, get_skill), and\n  know when to write them back with create_or_update_skill. Use when the user\n  wants profile skills, commands, or subagents without syncing a full IDE skill\n  bundle. Prefer knotr-save-skill when the user explicitly wants to persist.\n---\n\n# Use Knotr skills (MCP)\n\nProfile skills live on knotr.ai. Discover and fetch them over the connected\nprofile MCP server—do **not** call `get_ide_plugin_install` for skill bodies.\n\n## Read path\n\n1. Call `list_skills` (optional `query`) or read `knotr-ai://manifests/skills`\n   (active only).\n2. Pick by name, description, and `intended_use` (`skill` | `command` |\n   `subagent`).\n3. Call `get_skill` with `skill_id`, or `resources/read` on `resource_uri`\n   (`knotr-ai://skills|commands|agents/<uuid>`).\n4. Follow the returned markdown. Use `referenced_documents` from `get_skill`\n   when present.\n5. Content is live—no `knotr-sync` / reload required to pick up remote edits.\n\n## Write path\n\nPrefer the **knotr-save-skill** command when the user should explicitly persist.\nOtherwise use `create_or_update_skill` (`mcp_write`) when:\n\n**Write when**\n\n- User asks to save, create, update, or publish a skill on Knotr.\n- A reusable workflow should travel across tools/machines with this profile.\n- Refining an existing Knotr skill (`skill_id` from list/get).\n- Persona/team procedures belong on the profile (not only in a repo’s\n  `.cursor/skills/`).\n\n**Do not write when**\n\n- One-off chat instructions.\n- Facts/docs → knowledgebase / `create_or_update_document`; finished shareable\n  outputs → Artifact.\n- Secrets, tokens, or machine-only absolute paths.\n- A matching skill already exists and the user only wanted to run it.\n- Soft-off (`inactive`) or overwrite of an active skill without confirmation.\n- Inventing skills nobody asked to persist.\n\n**Checklist**\n\n1. `list_skills` — avoid duplicates; prefer update with `skill_id`.\n2. Confirm with the user if create vs update is unclear.\n3. Set `intended_use`; prefer `status: draft` on create unless they want\n   `active`.\n4. Store clean markdown; attach `reference_document_ids` only for owned docs.\n5. Report UUID—live on MCP immediately (no full skill sync).\n\n## Repo-local vs Knotr\n\n- Project `.cursor/skills/` — git, this codebase only.\n- Knotr profile skill — durable across MCP clients. Default for “save as a\n  skill” in a connected session: Knotr via `create_or_update_skill`.\n"
}