Update to Knotr

{
  "description": "Lint user-facing prose against the profile’s Knotr style guides via MCP check_style (Vale). Use before shipping copy, emails, docs, or marketing text so outputs match the user’s voice. Prefer knotr-check-style for an explicit lint pass.",
  "included_files": [],
  "name": "use-knotr-style",
  "skill_md_contents": "---\nname: use-knotr-style\ndescription: >-\n  Lint user-facing prose against the profile’s Knotr style guides via MCP\n  check_style (Vale). Use before shipping copy, emails, docs, or marketing text\n  so outputs match the user’s voice. Prefer knotr-check-style for an explicit\n  lint pass.\n---\n\n# Use Knotr style checking (MCP)\n\n`check_style` is only available when the profile has at least one **active**\nstyle guide. Prefer this path over guessing tone from memory.\n\n## Check loop\n\n1. `list_style_guides` — confirm an active guide exists (`status: active`).\n   If none, tell the user to activate or create a guide in knotr.ai (or use\n   `create_or_update_style_guide` with `mcp_write` if they ask).\n2. Optionally `get_style_guide` for editorial guidelines / source context.\n3. Call `check_style` with the draft `content` (optional `format`, default\n   `md`; optional `style_guide_id`).\n4. Fix reported issues (line, match, message, rule, suggested fix).\n5. Re-run `check_style` until clean or the user accepts remaining issues.\n\n## When to run\n\n- Before finalizing user-facing prose the profile should “sound like”\n- After substantial rewrites of emails, docs, landing copy, or skill text\n- When the user asks to match brand / style / voice\n\n## Authoring guides (light)\n\nCreating or regenerating Vale rules is secondary. Use\n`create_or_update_style_guide` when the user wants a new guide or to change\n`source_text` / regenerate. Deep Vale on-disk sync remains an optional profile\nIDE zip concern—not required for MCP `check_style`.\n"
}