[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698SAD8QTD8SB6Q74YRGENQ":3,"skill-same:01M698SAD8QTD8SB6Q74YRGENQ":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":38,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M698SAD8QTD8SB6Q74YRGENQ","security-triage",null,"Triage OpenClaw security advisories, drafts, and GHSA reports with shipped-tag and trust-model proof.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394352,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-triage\u002FSKILL.md",[],[18,19,20,9,21,22,23,24,25,26,27],"security triage","security","triage","model","openclaw security","reports","trust","proof","with","drafts","2026-11-10 10:12:30",false,"---\nname: security-triage\ndescription: \"Triage OpenClaw security advisories, drafts, and GHSA reports with shipped-tag and trust-model proof.\"\n---\n\n# Security Triage\n\nUse when reviewing OpenClaw security advisories, drafts, or GHSA reports.\n\nGoal: high-confidence maintainers' triage without over-closing real issues or shipping unnecessary regressions.\n\n## Close Bar\n\nClose only if one of these is true:\n\n- duplicate of an existing advisory or fixed issue\n- invalid against shipped behavior\n- out of scope under `SECURITY.md`\n- fixed before any affected release\u002Ftag\n\nDo not close only because `main` is fixed. If latest shipped tag or npm release is affected, keep it open until released or published with the right status.\n\n## Required Reads\n\nBefore answering:\n\n1. Read `SECURITY.md`.\n2. Read the GHSA body with `gh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories\u002F\u003CGHSA>`.\n3. Inspect the exact implicated code paths.\n4. Verify shipped state:\n   - `git tag --sort=-creatordate | head`\n   - `npm view openclaw version --userconfig \"$(mktemp)\"`\n   - `git tag --contains \u003Cfix-commit>`\n   - if needed: `git show \u003Ctag>:path\u002Fto\u002Ffile`\n5. Search for canonical overlap:\n   - existing published GHSAs\n   - older fixed bugs\n   - same trust-model class already covered in `SECURITY.md`\n\n## Review Method\n\nFor each advisory, decide:\n\n- `close`\n- `keep open`\n- `keep open but narrow`\n\nDefault to one advisory at a time when comments\u002Fclosures are involved:\n\n1. Review exactly one GHSA.\n2. Print the GHSA URL first.\n3. Summarize the decision and evidence for discussion.\n4. Draft one maintainer-ready comment.\n5. Copy only that one comment to the clipboard.\n6. Stop and wait for Peter to post\u002Fdiscuss before moving to the next GHSA.\n\nDo not batch multiple close comments unless Peter explicitly asks for a batch.\n\nCheck in this order:\n\n1. Trust model\n   - Is the prerequisite already inside trusted host\u002Flocal\u002Fplugin\u002Foperator state?\n   - Does `SECURITY.md` explicitly call this class out as out of scope or hardening-only?\n2. Shipped behavior\n   - Is the bug present in the latest shipped tag or npm release?\n   - Was it fixed before release?\n3. Exploit path\n   - Does the report show a real boundary bypass, not just prompt injection, local same-user control, or helper-level semantics?\n   - If data only moves between trusted workspace-memory files called out in `SECURITY.md`, do not treat \"injection markers\" alone as a security bug.\n   - In that case, frame sanitization as optional hardening only if it preserves expected memory workflows.\n4. Functional tradeoff\n   - If a hardening change would reduce intended user functionality, call that out before proposing it.\n   - Prefer fixes that preserve user workflows over deny-by-default regressions unless the boundary demands it.\n5. Hardening follow-up\n   - Even when the GHSA should close, ask whether a narrow hardening change would reduce footguns without changing the documented trust boundary.\n   - Separate hardening from vulnerability status. Phrase it as \"not required for GHSA closure, but worth considering\".\n   - Bring up hardening only if it is concrete, low-risk, and preserves intended maintainer\u002Foperator workflows.\n   - If hardening would require a product\u002Fsecurity model change, say that explicitly and do not imply it is a required fix for closure.\n\n## Response Format\n\nWhen preparing a maintainer-ready close reply:\n\n1. Print the GHSA URL first.\n2. Then draft a detailed response the maintainer can post.\n3. Include:\n   - exact reason for close\n   - exact code refs\n   - exact shipped tag \u002F release facts\n   - fix provenance or canonical duplicate GHSA when applicable\n   - optional hardening note only if worthwhile and functionality-preserving\n\nKeep tone firm, specific, non-defensive.\n\n## Public Wording Hygiene\n\n- Keep raw commit hashes, PR titles\u002Fnumbers, and fix-mechanism summaries out of public advisory text. Use the patched release\u002Fversion field only.\n- Keep exact commit SHAs, PRs, and implementation notes in internal notes and verification files.\n- For hardening\u002Fno-publish outcomes, do not add exploit-heavy details, \"Fixed by\" text, or a \"Fix Commit(s)\" section. Thank reporters, preserve credit, state the `SECURITY.md` boundary, and say clearly that the GHSA will close without publication.\n- For published CVE\u002FGHSA text, prefer `### Patched Versions` with the fixed release. Do not explain how the patch works unless Peter explicitly asks for that public detail.\n- Keep GHSA ids out of changelog and release-note wording unless Peter explicitly asks.\n\n## Discussion Mode\n\nWhen Peter is manually posting GHSA comments, use this flow:\n\n1. Show the URL.\n2. Give a terse verdict (`close`, `keep open`, or `keep open but narrow`).\n3. List the strongest evidence bullets.\n4. State any optional hardening follow-up separately from the close reason.\n5. Copy the proposed comment body with `pbcopy`.\n6. End the reply after the one advisory. Do not continue to the next advisory until Peter says to continue.\n\nIf the GitHub API cannot post comments for private advisories, say so once and keep using clipboard\u002FUI paste.\n\n## Clipboard Step\n\nAfter drafting the final post body for the current advisory, copy it:\n\n```bash\npbcopy \u003C\u003C'EOF'\n\u003Cfinal response>\nEOF\n```\n\nTell the user that the clipboard now contains the proposed response for that advisory.\n\n## Useful Commands\n\n```bash\ngh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories\u002F\u003CGHSA>\ngh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories --paginate\ngit tag --sort=-creatordate | head -n 20\nnpm view openclaw version --userconfig \"$(mktemp)\"\ngit tag --contains \u003Ccommit>\ngit show \u003Ctag>:\u003Cpath>\ngh search issues --repo openclaw\u002Fopenclaw --match title,body,comments -- \"\u003Cterms>\"\ngh search prs --repo openclaw\u002Fopenclaw --match title,body,comments -- \"\u003Cterms>\"\n```\n\n## Cyber Classifier Interruptions\n\nFor permitted defensive work interrupted by a cyber classifier, use an approved,\navailable Daybreak Blue route only for that bounded task, then restore the\nprevious model. Preserve the approved identity, scope, permissions, sandbox, and\nreview gates. Never switch models to bypass access denials, disallowed requests,\nor refused tool actions; if that route also refuses, stop and report. Follow\n[OpenAI's guidance](https:\u002F\u002Flearn.chatgpt.com\u002Fdocs\u002Fcyber-safety) for approved\nmodel access.\n\n## Decision Notes\n\n- “fixed on main, unreleased” is usually not a close.\n- “needs attacker-controlled trusted local state first” is usually out of scope.\n- “same-host same-user process can already read\u002Fwrite local state” is usually out of scope.\n- “trusted workspace memory promotes\u002Freindexes trusted workspace memory” is usually out of scope unless it crosses a documented boundary.\n- “helper function behaves differently than documented config semantics” is usually invalid.\n- If only the severity is wrong but the bug is real, keep it open and narrow the impact in the reply.\n","# Security Triage\n\nUse when reviewing OpenClaw security advisories, drafts, or GHSA reports.\n\nGoal: high-confidence maintainers' triage without over-closing real issues or shipping unnecessary regressions.\n\n## Close Bar\n\nClose only if one of these is true:\n\n- duplicate of an existing advisory or fixed issue\n- invalid against shipped behavior\n- out of scope under `SECURITY.md`\n- fixed before any affected release\u002Ftag\n\nDo not close only because `main` is fixed. If latest shipped tag or npm release is affected, keep it open until released or published with the right status.\n\n## Required Reads\n\nBefore answering:\n\n1. Read `SECURITY.md`.\n2. Read the GHSA body with `gh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories\u002F\u003CGHSA>`.\n3. Inspect the exact implicated code paths.\n4. Verify shipped state:\n   - `git tag --sort=-creatordate | head`\n   - `npm view openclaw version --userconfig \"$(mktemp)\"`\n   - `git tag --contains \u003Cfix-commit>`\n   - if needed: `git show \u003Ctag>:path\u002Fto\u002Ffile`\n5. Search for canonical overlap:\n   - existing published GHSAs\n   - older fixed bugs\n   - same trust-model class already covered in `SECURITY.md`\n\n## Review Method\n\nFor each advisory, decide:\n\n- `close`\n- `keep open`\n- `keep open but narrow`\n\nDefault to one advisory at a time when comments\u002Fclosures are involved:\n\n1. Review exactly one GHSA.\n2. Print the GHSA URL first.\n3. Summarize the decision and evidence for discussion.\n4. Draft one maintainer-ready comment.\n5. Copy only that one comment to the clipboard.\n6. Stop and wait for Peter to post\u002Fdiscuss before moving to the next GHSA.\n\nDo not batch multiple close comments unless Peter explicitly asks for a batch.\n\nCheck in this order:\n\n1. Trust model\n   - Is the prerequisite already inside trusted host\u002Flocal\u002Fplugin\u002Foperator state?\n   - Does `SECURITY.md` explicitly call this class out as out of scope or hardening-only?\n2. Shipped behavior\n   - Is the bug present in the latest shipped tag or npm release?\n   - Was it fixed before release?\n3. Exploit path\n   - Does the report show a real boundary bypass, not just prompt injection, local same-user control, or helper-level semantics?\n   - If data only moves between trusted workspace-memory files called out in `SECURITY.md`, do not treat \"injection markers\" alone as a security bug.\n   - In that case, frame sanitization as optional hardening only if it preserves expected memory workflows.\n4. Functional tradeoff\n   - If a hardening change would reduce intended user functionality, call that out before proposing it.\n   - Prefer fixes that preserve user workflows over deny-by-default regressions unless the boundary demands it.\n5. Hardening follow-up\n   - Even when the GHSA should close, ask whether a narrow hardening change would reduce footguns without changing the documented trust boundary.\n   - Separate hardening from vulnerability status. Phrase it as \"not required for GHSA closure, but worth considering\".\n   - Bring up hardening only if it is concrete, low-risk, and preserves intended maintainer\u002Foperator workflows.\n   - If hardening would require a product\u002Fsecurity model change, say that explicitly and do not imply it is a required fix for closure.\n\n## Response Format\n\nWhen preparing a maintainer-ready close reply:\n\n1. Print the GHSA URL first.\n2. Then draft a detailed response the maintainer can post.\n3. Include:\n   - exact reason for close\n   - exact code refs\n   - exact shipped tag \u002F release facts\n   - fix provenance or canonical duplicate GHSA when applicable\n   - optional hardening note only if worthwhile and functionality-preserving\n\nKeep tone firm, specific, non-defensive.\n\n## Public Wording Hygiene\n\n- Keep raw commit hashes, PR titles\u002Fnumbers, and fix-mechanism summaries out of public advisory text. Use the patched release\u002Fversion field only.\n- Keep exact commit SHAs, PRs, and implementation notes in internal notes and verification files.\n- For hardening\u002Fno-publish outcomes, do not add exploit-heavy details, \"Fixed by\" text, or a \"Fix Commit(s)\" section. Thank reporters, preserve credit, state the `SECURITY.md` boundary, and say clearly that the GHSA will close without publication.\n- For published CVE\u002FGHSA text, prefer `### Patched Versions` with the fixed release. Do not explain how the patch works unless Peter explicitly asks for that public detail.\n- Keep GHSA ids out of changelog and release-note wording unless Peter explicitly asks.\n\n## Discussion Mode\n\nWhen Peter is manually posting GHSA comments, use this flow:\n\n1. Show the URL.\n2. Give a terse verdict (`close`, `keep open`, or `keep open but narrow`).\n3. List the strongest evidence bullets.\n4. State any optional hardening follow-up separately from the close reason.\n5. Copy the proposed comment body with `pbcopy`.\n6. End the reply after the one advisory. Do not continue to the next advisory until Peter says to continue.\n\nIf the GitHub API cannot post comments for private advisories, say so once and keep using clipboard\u002FUI paste.\n\n## Clipboard Step\n\nAfter drafting the final post body for the current advisory, copy it:\n\n```bash\npbcopy \u003C\u003C'EOF'\n\u003Cfinal response>\nEOF\n```\n\nTell the user that the clipboard now contains the proposed response for that advisory.\n\n## Useful Commands\n\n```bash\ngh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories\u002F\u003CGHSA>\ngh api \u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Fsecurity-advisories --paginate\ngit tag --sort=-creatordate | head -n 20\nnpm view openclaw version --userconfig \"$(mktemp)\"\ngit tag --contains \u003Ccommit>\ngit show \u003Ctag>:\u003Cpath>\ngh search issues --repo openclaw\u002Fopenclaw --match title,body,comments -- \"\u003Cterms>\"\ngh search prs --repo openclaw\u002Fopenclaw --match title,body,comments -- \"\u003Cterms>\"\n```\n\n## Cyber Classifier Interruptions\n\nFor permitted defensive work interrupted by a cyber classifier, use an approved,\navailable Daybreak Blue route only for that bounded task, then restore the\nprevious model. Preserve the approved identity, scope, permissions, sandbox, and\nreview gates. Never switch models to bypass access denials, disallowed requests,\nor refused tool actions; if that route also refuses, stop and report. Follow\n[OpenAI's guidance](https:\u002F\u002Flearn.chatgpt.com\u002Fdocs\u002Fcyber-safety) for approved\nmodel access.\n\n## Decision Notes\n\n- “fixed on main, unreleased” is usually not a close.\n- “needs attacker-controlled trusted local state first” is usually out of scope.\n- “same-host same-user process can already read\u002Fwrite local state” is usually out of scope.\n- “trusted workspace memory promotes\u002Freindexes trusted workspace memory” is usually out of scope unless it crosses a documented boundary.\n- “helper function behaves differently than documented config semantics” is usually invalid.\n- If only the severity is wrong but the bug is real, keep it open and narrow the impact in the reply.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7",".agents\u002Fskills\u002Fsecurity-triage",82861,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-12 03:01:25",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add openclaw\u002Fopenclaw --skill security-triage",{"tool":48,"command":49},"bunx","bunx skills add openclaw\u002Fopenclaw --skill security-triage",{"tool":51,"command":52},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill security-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-triage\u002FSKILL.md",true,[],[57,63,86,103,125,149],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":28},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[59],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":28},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[65,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85],"for","api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":28},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[88,93,94,77,95,78,96,97,98,99,100,101,70,102,26],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":28},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[105,115,116,117,118,70,26,119,120,121,122,123,9,124],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":139,"publishedAt":28},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[131,136],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":137,"categoryName":138,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师",[127,97,140,141,142,143,144,145,77,78,146,96,71,147,148],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":28},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[151,77,156,157,70,158,159,160,161,162,163,164,78,165,166,167,168,169,170],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]