[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CASHBA8G69F4RKZVNKC1GF":3,"skill-same:01M6CASHBA8G69F4RKZVNKC1GF":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6CASHBA8G69F4RKZVNKC1GF","agent-memory-skill-hygiene",null,"Audit Hermes memory and skills after corrections, workflow discoveries, or periodic maintenance. Use session recall plus live verification to keep durable memory compact and skills accurate.","adnichols\u002Fai-configs","adnichols","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F493746?v=4","01M6C33VRY9WF6XWYPT1AFA7JJ","Aaron Nichols","01M6C33VWTNKGRM92E9G643V4W",5,"MIT","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fautonomous-ai-agents\u002Fagent-memory-skill-hygiene\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"memory","agent memory","skill hygiene","agent memory skill hygiene","workflow","verification","audit","recall","hermes","hermes agent","session","use","periodic","maintenance","2026-11-10 10:12:30",false,"---\nname: agent-memory-skill-hygiene\ndescription: Audit Hermes memory and skills after corrections, workflow discoveries, or periodic maintenance. Use session recall plus live verification to keep durable memory compact and skills accurate.\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [memory, skills, maintenance, hermes, hygiene]\n---\n\n# Agent memory + skill hygiene\n\nUse this when:\n- the user asks to review\u002Frefine memory\n- several sessions contained corrections or workflow discoveries\n- a skill may now be stale relative to live CLI behavior or current docs\n- memory is nearing capacity and needs compression\n\n## Goals\n1. Keep durable memory compact, high-value, and current.\n2. Patch or create skills when a reusable workflow or command quirk is confirmed.\n3. Treat most substantive sessions as likely to produce at least one skill-library improvement; a no-op pass requires an explicit reason that no correction, workflow discovery, tool quirk, or stale skill surfaced.\n4. Avoid saving temporary task state, noisy session summaries, or facts easy to rediscover.\n\n## Audit flow\n\n### 1. Recall recent corrections first\n- Use `session_search` with broad OR queries such as:\n  - `correction OR outdated OR wrong command OR failed`\n  - `remember this OR skill update OR overreach`\n- Look for:\n  - user corrections that should become durable preferences\n  - repeated command\u002FAPI quirks worth skill updates\n  - places where an existing skill caused drift or overreach\n\n### 2. Inspect relevant skills before editing\n- Load any potentially relevant skills with `skill_view`.\n- Prefer patching an existing skill over creating a near-duplicate.\n- If a skill is broad and security-scanned as dangerous, expect patch attempts to require confirmation; in that case, patch a narrower related skill or summarize the blocked change clearly.\n- If the best-matching skill is pinned and `skill_manage` refuses writes, do **not** create a duplicate narrow skill just to bypass pinning. Try the next-best existing umbrella only if it genuinely covers the lesson; otherwise report the blocked update and tell the user the exact `hermes curator unpin \u003Cskill>` command needed.\n\n### 3. Verify live behavior\nNever trust stale recollection for command syntax or current behavior.\n- Use `terminal` for CLI help\u002Fversion checks.\n- Use `web_search` \u002F `web_extract` for current docs when the behavior depends on upstream releases.\n- Only write skill guidance that was either:\n  - confirmed live, or\n  - clearly labeled as doc-derived.\n\n### 4. Decide what belongs in memory\nGood memory candidates:\n- durable user preferences\n- stable environment quirks\n- recurring naming\u002Fidentity conventions\n- persistent workflow interpretations that prevent future correction\n\nDo not save:\n- completed work logs\n- one-off task outcomes\n- bulky session recaps\n- facts that belong better in a skill than memory\n\n### 5. Compress before adding\nWhen memory is tight:\n- replace verbose entries with shorter versions rather than adding duplicates\n- merge closely related rules into one concise line\n- remove obsolete facts after confirming they are no longer needed\n\n### 6. Patch\u002Fcreate skills when reuse is likely\nUpdate a skill when:\n- a command changed\n- fallback behavior was learned from failure\n- a workflow needs a new guardrail\n\nCreate a skill when:\n- the procedure is reusable\n- it took multiple steps or multiple tools to validate\n- future sessions would benefit from a named playbook\n\n## Output checklist\nBefore finishing, report:\n- what memory was added\u002Freplaced\u002Fremoved\n- which skills were patched\u002Fcreated\n- anything you attempted but could not update (for example confirmation-gated or pinned skill edits)\n- any recommended next cleanup items\n\nReference: `references\u002Fpinned-skill-blocked-updates-2026-05.md` records a concrete session where the correct target skills were pinned; use it as a pattern for reporting blocked updates without creating duplicate narrow skills.\n\n## Heuristics\n- Prefer one strong concise memory entry over several overlapping ones.\n- Prefer targeted skill patches over broad rewrites.\n- If a discovered lesson only matters in one channel\u002Fcontext, say so explicitly in memory\u002Fskill text.\n- If a correction changes product framing or authority boundaries, store it promptly.\n","# Agent memory + skill hygiene\n\nUse this when:\n- the user asks to review\u002Frefine memory\n- several sessions contained corrections or workflow discoveries\n- a skill may now be stale relative to live CLI behavior or current docs\n- memory is nearing capacity and needs compression\n\n## Goals\n1. Keep durable memory compact, high-value, and current.\n2. Patch or create skills when a reusable workflow or command quirk is confirmed.\n3. Treat most substantive sessions as likely to produce at least one skill-library improvement; a no-op pass requires an explicit reason that no correction, workflow discovery, tool quirk, or stale skill surfaced.\n4. Avoid saving temporary task state, noisy session summaries, or facts easy to rediscover.\n\n## Audit flow\n\n### 1. Recall recent corrections first\n- Use `session_search` with broad OR queries such as:\n  - `correction OR outdated OR wrong command OR failed`\n  - `remember this OR skill update OR overreach`\n- Look for:\n  - user corrections that should become durable preferences\n  - repeated command\u002FAPI quirks worth skill updates\n  - places where an existing skill caused drift or overreach\n\n### 2. Inspect relevant skills before editing\n- Load any potentially relevant skills with `skill_view`.\n- Prefer patching an existing skill over creating a near-duplicate.\n- If a skill is broad and security-scanned as dangerous, expect patch attempts to require confirmation; in that case, patch a narrower related skill or summarize the blocked change clearly.\n- If the best-matching skill is pinned and `skill_manage` refuses writes, do **not** create a duplicate narrow skill just to bypass pinning. Try the next-best existing umbrella only if it genuinely covers the lesson; otherwise report the blocked update and tell the user the exact `hermes curator unpin \u003Cskill>` command needed.\n\n### 3. Verify live behavior\nNever trust stale recollection for command syntax or current behavior.\n- Use `terminal` for CLI help\u002Fversion checks.\n- Use `web_search` \u002F `web_extract` for current docs when the behavior depends on upstream releases.\n- Only write skill guidance that was either:\n  - confirmed live, or\n  - clearly labeled as doc-derived.\n\n### 4. Decide what belongs in memory\nGood memory candidates:\n- durable user preferences\n- stable environment quirks\n- recurring naming\u002Fidentity conventions\n- persistent workflow interpretations that prevent future correction\n\nDo not save:\n- completed work logs\n- one-off task outcomes\n- bulky session recaps\n- facts that belong better in a skill than memory\n\n### 5. Compress before adding\nWhen memory is tight:\n- replace verbose entries with shorter versions rather than adding duplicates\n- merge closely related rules into one concise line\n- remove obsolete facts after confirming they are no longer needed\n\n### 6. Patch\u002Fcreate skills when reuse is likely\nUpdate a skill when:\n- a command changed\n- fallback behavior was learned from failure\n- a workflow needs a new guardrail\n\nCreate a skill when:\n- the procedure is reusable\n- it took multiple steps or multiple tools to validate\n- future sessions would benefit from a named playbook\n\n## Output checklist\nBefore finishing, report:\n- what memory was added\u002Freplaced\u002Fremoved\n- which skills were patched\u002Fcreated\n- anything you attempted but could not update (for example confirmation-gated or pinned skill edits)\n- any recommended next cleanup items\n\nReference: `references\u002Fpinned-skill-blocked-updates-2026-05.md` records a concrete session where the correct target skills were pinned; use it as a pattern for reporting blocked updates without creating duplicate narrow skills.\n\n## Heuristics\n- Prefer one strong concise memory entry over several overlapping ones.\n- Prefer targeted skill patches over broad rewrites.\n- If a discovered lesson only matters in one channel\u002Fcontext, say so explicitly in memory\u002Fskill text.\n- If a correction changes product framing or authority boundaries, store it promptly.\n",{"name":5,"author":43,"license":15,"version":44,"metadata":45,"description":7},"Hermes Agent","1.0.0",{"hermes":46},{"tags":47},[24,48,37,32,49],"skills","hygiene","main","64e2fc9afa7bb3da1138eb73399144d0e7e73e9d","_hermes\u002Fdefault\u002Fskills\u002Fautonomous-ai-agents\u002Fagent-memory-skill-hygiene",4,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs","https:\u002F\u002Fgithub.com\u002Fadnichols","2026-11-06 00:28:38",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add adnichols\u002Fai-configs --skill agent-memory-skill-hygiene",{"tool":63,"command":64},"bunx","bunx skills add adnichols\u002Fai-configs --skill agent-memory-skill-hygiene",{"tool":66,"command":67},"pnpm","pnpm dlx skills add adnichols\u002Fai-configs --skill agent-memory-skill-hygiene","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fautonomous-ai-agents\u002Fagent-memory-skill-hygiene\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fopenai.yaml","REFERENCE","参考文档",273,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fcontent-creation\u002Fshared\u002Fskills\u002Farticle-writing\u002Fagents\u002Fopenai.yaml",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fpinned-skill-blocked-updates-2026-05.md",2142,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fautonomous-ai-agents\u002Fagent-memory-skill-hygiene\u002Freferences\u002Fpinned-skill-blocked-updates-2026-05.md",[82,101,130,155,166,182],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":38},"01M6CB7RN791P5RRRCJWWC7DAR","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[89,90,91,92,93,35,94,33,32,95,96,97,98,99,100],"recovery","page","blocked page recovery","bot","fallback","fetch","Citations","waf","windows","research","linux","macos",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":116,"publishedAt":38},"01M6CB7NQY2VVYCQJ1QBXACQF4","writing-plans","Use when creating or updating executable software plans. Keep plans as local files unless the user explicitly asks to register them in Doct.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[107,110,111],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[117,118,119,120,28,121,122,123,124,125,126,127,35,128,33,32,129],"writing","writing plans","documentation","test","design","user","development","planning","files","implementation","html","ops","plan",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":145,"publishedAt":38},"01M6CB7JME246KZQHP73Z2STDF","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[136,139,142],{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":143,"categoryName":144,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000037","律师与法务",[120,123,146,147,148,33,32,149,129,150,151,152,100,153,99,154,97],"test driven development","red-green-refactor","superpowers","quality","refactor","code","debugging","tdd","testing",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":38},"01M6CB7FQ407KQTD4Z9VAWKY54","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[161],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},[152,163,123,148,33,32,164,129,165,97,120,99,100],"systematic debugging","troubleshooting","investigation",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":38},"01M6CB7D57MK88HE5YPZHKH68Q","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[168,97,176,177,98,178,99,100,179,180,181,33,32,129,124],"validate","experiments","prototype","feasibility","sketch","experiment",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":38},"01M6CB7APAQ37YE5YE1MAAFT42","simplify-code","Parallel 3-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[188,189],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":190,"categoryName":191,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000030","开发工程师",[193,194,151,195,33,32,196,129,150,197,198,199,123,97,120,99,200,100],"simplify code","simplify","subagent","parallel","code-review","delegation","cleanup","review"]