[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSXATZKEFHCSTPS7SKNBHN":3,"skill-same:01M6DSXATZKEFHCSTPS7SKNBHN":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6DSXATZKEFHCSTPS7SKNBHN","mc-changelog-update",null,"Add a properly-formatted entry to a project's CHANGELOG.md following the project's existing conventions. TRIGGER when the user says \"update the changelog\", \"add to changelog\", \"log this change\", or as part of a document-and-commit flow when CHANGELOG.md is one of the artifacts that needs to change.","clayrune-io\u002Fclayrune","clayrune-io","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F324312123?v=4","01M6DSX1QQQMJ0FPCSHSX95Q9G","01M6DSX1ZXTZQSGRA5ZXH1ZZWM",17,"MIT","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fbuiltin\u002Fmc-changelog-update\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"update","changelog","changelog update","mc","mc changelog update","project","when","entry","Existing","add","trigger","as","change","conventions","document","log","user","flow","artifacts","commit","2026-11-10 10:12:30",false,"---\nname: mc-changelog-update\ndescription: Add a properly-formatted entry to a project's CHANGELOG.md following the project's existing conventions. TRIGGER when the user says \"update the changelog\", \"add to changelog\", \"log this change\", or as part of a document-and-commit flow when CHANGELOG.md is one of the artifacts that needs to change.\n---\n\n# CHANGELOG.md update — guided\n\nMost Clayrune-managed projects keep a CHANGELOG.md in the project root. This skill walks through adding an entry that matches the project's existing format.\n\n## Steps\n\n### 1. Read the current CHANGELOG.md\n\n```bash\nhead -120 CHANGELOG.md\n```\n\nPattern-match the existing style:\n\n- **Date stamp format** — `[2026-05-10]`, `## 2026-05-10`, `[v1.4.2 — 2026-05-10]`, etc.\n- **Section style** — flat bullets, or grouped under `### New`, `### Changed`, `### Fixed`?\n- **Voice** — past tense (\"Added X\") or imperative (\"Add X\")?\n- **Detail level** — one-line bullets, or paragraphs with Why\u002FRollback subsections?\n\n### 2. Compose the entry\n\nMatch the style exactly. Don't introduce a new format. Common structures:\n\n**Style A — flat bullets:**\n```markdown\n## [2026-05-10] — Short headline\n\n- Added foo\n- Fixed bar in baz\n- Removed deprecated quux\n```\n\n**Style B — grouped:**\n```markdown\n## [2026-05-10] — Short headline\n\n### Added\n- New foo widget for X\n\n### Fixed\n- bar no longer crashes when Y\n\n### Changed\n- baz default flipped to true\n```\n\n**Style C — narrative with Why\u002FRollback:**\n```markdown\n## [2026-05-10] — Short headline\n\n- **Change:** One-sentence description of what changed.\n- **Why:** The motivation — incident, requirement, user request.\n- **Rollback:** How to revert if needed.\n```\n\n### 3. Insert at the top (most projects) — or at the bottom (rarely)\n\nMost CHANGELOG.md files have newest entries at the top. Confirm by checking the existing first few entries: do dates descend or ascend?\n\nInsert above the most recent entry, NOT at the very top of the file (which usually has a header \u002F title \u002F \"Unreleased\" section).\n\n### 4. Show the diff before saving\n\nAfter editing, show the user the diff so they can sanity-check:\n\n```bash\ngit diff CHANGELOG.md\n```\n\n### 5. Companion gate — `docs\u002FUSER_GUIDE.md` (Clayrune only)\n\nIf the CHANGELOG entry describes a **user-facing feature** — a new UI\nelement, button, menu entry, sidebar item, settings toggle, keyboard\nshortcut, or any feature an end user can discover — then `USER_GUIDE.md`\nneeds a matching update **in the same change set**. That file is the\nsource of truth for the in-app \"Ask Claydo\" helper; if the feature isn't\nin it, Claydo can't tell users about it.\n\nAfter step 4, ask yourself: *\"Is the thing I just added to CHANGELOG.md\na user-facing feature?\"*\n\n- **Yes** → grep `docs\u002FUSER_GUIDE.md` for the feature name. If it's not\n  there (or only barely mentioned), draft the matching guide section\n  before this skill considers itself done. Surface the diff to the user\n  alongside the CHANGELOG diff.\n- **No** (refactor, internal-only change, bug fix with no UX delta) →\n  state explicitly: *\"USER_GUIDE.md doesn't need an update — this is\n  internal-only.\"*\n\nThis gate exists because Clayrune has historically shipped UI\nfeatures that Claydo wasn't taught about, leaving the in-app helper\nunable to answer \"how do I use X?\" questions.\n\n### 6. Do not commit yet\n\nThis skill only edits CHANGELOG.md (and, when warranted, `USER_GUIDE.md`).\nCommit happens separately — usually as part of the `document-commit-deploy`\nflow.\n\n## Important\n\n- Don't fabricate detail. If you're unsure why a change was made, ask the user — don't invent a justification.\n- Don't reformat existing entries. New entry only.\n- Preserve trailing newlines, separator lines, and any header comments at the top of the file.\n","# CHANGELOG.md update — guided\n\nMost Clayrune-managed projects keep a CHANGELOG.md in the project root. This skill walks through adding an entry that matches the project's existing format.\n\n## Steps\n\n### 1. Read the current CHANGELOG.md\n\n```bash\nhead -120 CHANGELOG.md\n```\n\nPattern-match the existing style:\n\n- **Date stamp format** — `[2026-05-10]`, `## 2026-05-10`, `[v1.4.2 — 2026-05-10]`, etc.\n- **Section style** — flat bullets, or grouped under `### New`, `### Changed`, `### Fixed`?\n- **Voice** — past tense (\"Added X\") or imperative (\"Add X\")?\n- **Detail level** — one-line bullets, or paragraphs with Why\u002FRollback subsections?\n\n### 2. Compose the entry\n\nMatch the style exactly. Don't introduce a new format. Common structures:\n\n**Style A — flat bullets:**\n```markdown\n## [2026-05-10] — Short headline\n\n- Added foo\n- Fixed bar in baz\n- Removed deprecated quux\n```\n\n**Style B — grouped:**\n```markdown\n## [2026-05-10] — Short headline\n\n### Added\n- New foo widget for X\n\n### Fixed\n- bar no longer crashes when Y\n\n### Changed\n- baz default flipped to true\n```\n\n**Style C — narrative with Why\u002FRollback:**\n```markdown\n## [2026-05-10] — Short headline\n\n- **Change:** One-sentence description of what changed.\n- **Why:** The motivation — incident, requirement, user request.\n- **Rollback:** How to revert if needed.\n```\n\n### 3. Insert at the top (most projects) — or at the bottom (rarely)\n\nMost CHANGELOG.md files have newest entries at the top. Confirm by checking the existing first few entries: do dates descend or ascend?\n\nInsert above the most recent entry, NOT at the very top of the file (which usually has a header \u002F title \u002F \"Unreleased\" section).\n\n### 4. Show the diff before saving\n\nAfter editing, show the user the diff so they can sanity-check:\n\n```bash\ngit diff CHANGELOG.md\n```\n\n### 5. Companion gate — `docs\u002FUSER_GUIDE.md` (Clayrune only)\n\nIf the CHANGELOG entry describes a **user-facing feature** — a new UI\nelement, button, menu entry, sidebar item, settings toggle, keyboard\nshortcut, or any feature an end user can discover — then `USER_GUIDE.md`\nneeds a matching update **in the same change set**. That file is the\nsource of truth for the in-app \"Ask Claydo\" helper; if the feature isn't\nin it, Claydo can't tell users about it.\n\nAfter step 4, ask yourself: *\"Is the thing I just added to CHANGELOG.md\na user-facing feature?\"*\n\n- **Yes** → grep `docs\u002FUSER_GUIDE.md` for the feature name. If it's not\n  there (or only barely mentioned), draft the matching guide section\n  before this skill considers itself done. Surface the diff to the user\n  alongside the CHANGELOG diff.\n- **No** (refactor, internal-only change, bug fix with no UX delta) →\n  state explicitly: *\"USER_GUIDE.md doesn't need an update — this is\n  internal-only.\"*\n\nThis gate exists because Clayrune has historically shipped UI\nfeatures that Claydo wasn't taught about, leaving the in-app helper\nunable to answer \"how do I use X?\" questions.\n\n### 6. Do not commit yet\n\nThis skill only edits CHANGELOG.md (and, when warranted, `USER_GUIDE.md`).\nCommit happens separately — usually as part of the `document-commit-deploy`\nflow.\n\n## Important\n\n- Don't fabricate detail. If you're unsure why a change was made, ask the user — don't invent a justification.\n- Don't reformat existing entries. New entry only.\n- Preserve trailing newlines, separator lines, and any header comments at the top of the file.\n",{"name":5,"description":7},"master","ef008ef5ed969452bf69f2e0baeb9c441f3ac83d","data\u002Fskills\u002Fbuiltin\u002Fmc-changelog-update",2,"https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune","https:\u002F\u002Fclayrune.io","https:\u002F\u002Fgithub.com\u002Fclayrune-io","2026-11-13 03:36:15",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add clayrune-io\u002Fclayrune --skill mc-changelog-update",{"tool":57,"command":58},"bunx","bunx skills add clayrune-io\u002Fclayrune --skill mc-changelog-update",{"tool":60,"command":61},"pnpm","pnpm dlx skills add clayrune-io\u002Fclayrune --skill mc-changelog-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fbuiltin\u002Fmc-changelog-update\u002FSKILL.md",true,[],[66,88,98,108,118,141],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":38},"01M6DSYZRPBR2KVMJ9F05W02WR","prompt-injection-skill","TEST FIXTURE (MC-912) — do not install. Exercises the prompt-injection detector.","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fprompt-injection-skill\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[78,79,80,81,82,21,83,84,85,86,87],"prompt injection","prompt","injection","prompt injection skill","detector","fixture","do","install","test","prompt-injection",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":38},"01M6DSYWKY8FQKJ2202HZTRZXN","persistence-skill","TEST FIXTURE (MC-912) — do not install. Exercises the persistence detector.","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fpersistence-skill\u002FSKILL.md",[94],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[96,97,86,85,84,83,21,82],"persistence","persistence skill",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":38},"01M6DSYSTMXZJXN4VH879PSH06","exfiltration-skill","TEST FIXTURE (MC-912) — do not install. Exercises the exfiltration detector.","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fexfiltration-skill\u002FSKILL.md",[104],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[106,107,86,85,84,83,21,82],"exfiltration","exfiltration skill",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":38},"01M6DSYP2HPFZS2D71SQTAK9WC","destructive-skill","TEST FIXTURE (MC-912) — do not install. Exercises the destructive-command detector.","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fdestructive-skill\u002FSKILL.md",[114],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[116,82,86,117,85,84,83,21],"destructive skill","command",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":130,"publishedAt":38},"01M6DSYK30Q44MPGK6QW8T6TSM","config-mod-skill","TEST FIXTURE (MC-912) — do not install. Exercises the agent-config-mod detector's write-API coverage (the gap Hermes's own scanner documents missing).","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fconfig-mod-skill\u002FSKILL.md",[124,125],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,85,86,133,134,135,136,137,138,84,83,139,140,21,82],"config mod skill","config","documents","api","hermes","write","coverage","scanner","gap","missing",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":38},"01M6DSYFMVW71SEMTN11XFQMAG","benign-skill","TEST FIXTURE (MC-912) — negative control. Should produce zero scanner findings.","https:\u002F\u002Fgithub.com\u002Fclayrune-io\u002Fclayrune\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fmalicious_skills\u002Fbenign-skill\u002FSKILL.md",[147],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[149,150,86,151,152,138,83,153,21],"benign","benign skill","produce","ZeRO","control"]