[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7S1SWV11N96X35BQNNW2D":3,"skill-same:01M7F7S1SWV11N96X35BQNNW2D":69},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7F7S1SWV11N96X35BQNNW2D","privacy-safe-observability",null,"Design, implement, and verify useful application diagnostics without leaking user content, identifiers, paths, secrets, or exception payloads. Use for debug logging, lifecycle instrumentation, background-worker visibility, and log-safety reviews.","chaorenex1\u002Fhermes-home-content","chaorenex1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23194925?v=4","01M7F5NA1D1D02R2MEMYQN2NZT","chan chan","01M7F5NA20KTHMTY2015CYM1TZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fprivacy-safe-observability\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\r\nname: privacy-safe-observability\r\ndescription: Design, implement, and verify useful application diagnostics without leaking user content, identifiers, paths, secrets, or exception payloads. Use for debug logging, lifecycle instrumentation, background-worker visibility, and log-safety reviews.\r\nversion: 1.0.0\r\nauthor: Masia\r\nlicense: MIT\r\nplatforms: [linux, macos, windows]\r\nmetadata:\r\n  hermes:\r\n    tags: [observability, logging, privacy, debugging, testing]\r\n    related_skills: [test-driven-development, systematic-debugging]\r\n---\r\n\r\n# Privacy-Safe Observability\r\n\r\nBuild logs that answer “what happened, where, and what state changed?” without copying the data being processed into the log stream.\r\n\r\n## When to Use\r\n\r\n- Adding DEBUG\u002FINFO\u002FWARNING events to a service, provider, plugin, scheduler, queue, or lifecycle hook\r\n- Diagnosing silent failures hidden by intentional exception handling\r\n- Instrumenting asynchronous workers, retries, timers, or stale-result fencing\r\n- Reviewing logs for private-content, secret, path, or identifier leakage\r\n- Adding tests for logging behavior\r\n\r\n## Core Contract\r\n\r\nEvery event should provide:\r\n\r\n1. A stable machine-searchable event name, such as `provider.prefetch_completed`\r\n2. Safe correlation, usually a deterministic short hash rather than a raw user\u002Fsession identifier\r\n3. Bounded structural metadata: counts, booleans, generation\u002Fattempt numbers, states, durations, and exception class names\r\n4. No raw payload, secret, user message, query, memory body, tool argument, host path, or exception message\r\n\r\nDEBUG is not a secrecy boundary. Anything unsafe at INFO is also unsafe at DEBUG.\r\n\r\n## Implementation Workflow\r\n\r\n### 1. Map the state transitions\r\n\r\nInstrument transitions rather than every line:\r\n\r\n- initialized \u002F shutdown\r\n- queued \u002F consumed \u002F completed\r\n- scheduled \u002F started \u002F completed\r\n- switched \u002F cancelled \u002F superseded\r\n- retrying \u002F exhausted \u002F failed\r\n- stale result discarded \u002F result applied\r\n\r\nFor background work, always cover both the success and caught-error path. An exception that is intentionally swallowed still needs a sanitized diagnostic event.\r\n\r\n### 2. Define a stable event vocabulary\r\n\r\nUse lowercase dotted names:\r\n\r\n```text\r\n\u003Ccomponent>.\u003Coperation>_\u003Ctransition>\r\nprovider.prefetch_queued\r\nprovider.prefetch_completed\r\nprovider.prefetch_failed\r\n```\r\n\r\nKeep field names stable. Prefer `error_type`, `result_count`, `message_count`, `generation`, `applied`, and `checkpoint_status` over free-form prose.\r\n\r\n### 3. Correlate without disclosure\r\n\r\nHash private identifiers before logging:\r\n\r\n```python\r\nsession_debug_id = hashlib.sha256(session_id.encode(\"utf-8\")).hexdigest()[:12]\r\n```\r\n\r\nA short hash is for correlation only, not authentication. Do not hash low-entropy secrets and assume they are safe; omit them entirely.\r\n\r\n### 4. Sanitize failures\r\n\r\nFor expected caught failures, log the class—not the message:\r\n\r\n```python\r\nexcept EXPECTED_ERRORS as exc:\r\n    logger.debug(\r\n        \"provider.operation_failed session=%s error_type=%s\",\r\n        session_debug_id,\r\n        type(exc).__name__,\r\n    )\r\n    return\r\n```\r\n\r\nUse `exc_info=True` only when the stack and exception text have been reviewed as safe for that deployment. Library\u002Fplugin code should generally avoid configuring root handlers or log levels; emit through a module logger and let the host decide visibility.\r\n\r\n### 5. Test first\r\n\r\nUse RED → GREEN for logging behavior:\r\n\r\n- Seed unmistakable private sentinel strings\r\n- Capture logs at the target logger and level\r\n- Assert stable event names and safe structural fields\r\n- Assert every sentinel is absent\r\n- Exercise both success and swallowed-error paths\r\n\r\nDo not assert the entire formatted line. Exact-line assertions are brittle and discourage useful safe fields.\r\n\r\n### 6. Handle asynchronous tests deterministically\r\n\r\nA worker can finish before the test reads its thread\u002Ftask handle. Capture the handle immediately when available and wait with a bound; if it is already gone, assert the observable event\u002Fstate instead of requiring the internal handle to exist. Never use an unbounded join or arbitrary sleep as the primary synchronization mechanism.\r\n\r\n### 7. Verify at increasing scope\r\n\r\n1. New focused observability tests\r\n2. Related lifecycle, scheduler, queue, and worker tests\r\n3. Full suite\r\n4. Syntax\u002Fdiff checks for the touched paths\r\n\r\nUse an interpreter-bound test command such as `python -m pytest` when a bare executable may resolve to a different Python environment than the source under test.\r\n\r\n## Event Design Guide\r\n\r\n| Situation | Useful safe fields | Avoid |\r\n|---|---|---|\r\n| Queue operation | generation, queue size, item count | payload, raw key |\r\n| Retrieval | mode, result count, cached chars, applied | query, document body |\r\n| Session lifecycle | short hash, turn, cancelled count | raw session ID, messages |\r\n| Background failure | operation, attempt, exception class | exception message, traceback by default |\r\n| Scheduler | checkpoint status, delay bucket, classifier configured | full timestamps tied to user data when unnecessary |\r\n| Memory processing | action enum, target enum, character count | memory content, tool arguments |\r\n\r\n## Pitfalls\r\n\r\n1. **Success-only instrumentation** — the system is still opaque when the worker fails.\r\n2. **Logging exception strings** — storage errors frequently contain absolute paths; validation errors may echo user input.\r\n3. **Raw correlation IDs** — session, chat, document, and candidate IDs can be private even without content.\r\n4. **Logging before validation** — malformed hostile input can reach logs unchanged.\r\n5. **Over-instrumenting hot loops** — prefer one transition event with counts to per-item logs.\r\n6. **Changing host logging configuration from a library** — emit records; do not seize global handlers or levels.\r\n7. **Racy tests** — do not assert that a fast worker handle must still exist after dispatch.\r\n8. **Using DEBUG as permission to leak** — log level controls volume, not data classification.\r\n\r\n## Reference Files\r\n\r\n- `references\u002Fmemory-provider-lifecycle-logging.md` — worked event taxonomy and regression-test pattern for a provider with queues, prefetch, session switching, timers, and idle workers.\r\n","# Privacy-Safe Observability\r\n\r\nBuild logs that answer “what happened, where, and what state changed?” without copying the data being processed into the log stream.\r\n\r\n## When to Use\r\n\r\n- Adding DEBUG\u002FINFO\u002FWARNING events to a service, provider, plugin, scheduler, queue, or lifecycle hook\r\n- Diagnosing silent failures hidden by intentional exception handling\r\n- Instrumenting asynchronous workers, retries, timers, or stale-result fencing\r\n- Reviewing logs for private-content, secret, path, or identifier leakage\r\n- Adding tests for logging behavior\r\n\r\n## Core Contract\r\n\r\nEvery event should provide:\r\n\r\n1. A stable machine-searchable event name, such as `provider.prefetch_completed`\r\n2. Safe correlation, usually a deterministic short hash rather than a raw user\u002Fsession identifier\r\n3. Bounded structural metadata: counts, booleans, generation\u002Fattempt numbers, states, durations, and exception class names\r\n4. No raw payload, secret, user message, query, memory body, tool argument, host path, or exception message\r\n\r\nDEBUG is not a secrecy boundary. Anything unsafe at INFO is also unsafe at DEBUG.\r\n\r\n## Implementation Workflow\r\n\r\n### 1. Map the state transitions\r\n\r\nInstrument transitions rather than every line:\r\n\r\n- initialized \u002F shutdown\r\n- queued \u002F consumed \u002F completed\r\n- scheduled \u002F started \u002F completed\r\n- switched \u002F cancelled \u002F superseded\r\n- retrying \u002F exhausted \u002F failed\r\n- stale result discarded \u002F result applied\r\n\r\nFor background work, always cover both the success and caught-error path. An exception that is intentionally swallowed still needs a sanitized diagnostic event.\r\n\r\n### 2. Define a stable event vocabulary\r\n\r\nUse lowercase dotted names:\r\n\r\n```text\r\n\u003Ccomponent>.\u003Coperation>_\u003Ctransition>\r\nprovider.prefetch_queued\r\nprovider.prefetch_completed\r\nprovider.prefetch_failed\r\n```\r\n\r\nKeep field names stable. Prefer `error_type`, `result_count`, `message_count`, `generation`, `applied`, and `checkpoint_status` over free-form prose.\r\n\r\n### 3. Correlate without disclosure\r\n\r\nHash private identifiers before logging:\r\n\r\n```python\r\nsession_debug_id = hashlib.sha256(session_id.encode(\"utf-8\")).hexdigest()[:12]\r\n```\r\n\r\nA short hash is for correlation only, not authentication. Do not hash low-entropy secrets and assume they are safe; omit them entirely.\r\n\r\n### 4. Sanitize failures\r\n\r\nFor expected caught failures, log the class—not the message:\r\n\r\n```python\r\nexcept EXPECTED_ERRORS as exc:\r\n    logger.debug(\r\n        \"provider.operation_failed session=%s error_type=%s\",\r\n        session_debug_id,\r\n        type(exc).__name__,\r\n    )\r\n    return\r\n```\r\n\r\nUse `exc_info=True` only when the stack and exception text have been reviewed as safe for that deployment. Library\u002Fplugin code should generally avoid configuring root handlers or log levels; emit through a module logger and let the host decide visibility.\r\n\r\n### 5. Test first\r\n\r\nUse RED → GREEN for logging behavior:\r\n\r\n- Seed unmistakable private sentinel strings\r\n- Capture logs at the target logger and level\r\n- Assert stable event names and safe structural fields\r\n- Assert every sentinel is absent\r\n- Exercise both success and swallowed-error paths\r\n\r\nDo not assert the entire formatted line. Exact-line assertions are brittle and discourage useful safe fields.\r\n\r\n### 6. Handle asynchronous tests deterministically\r\n\r\nA worker can finish before the test reads its thread\u002Ftask handle. Capture the handle immediately when available and wait with a bound; if it is already gone, assert the observable event\u002Fstate instead of requiring the internal handle to exist. Never use an unbounded join or arbitrary sleep as the primary synchronization mechanism.\r\n\r\n### 7. Verify at increasing scope\r\n\r\n1. New focused observability tests\r\n2. Related lifecycle, scheduler, queue, and worker tests\r\n3. Full suite\r\n4. Syntax\u002Fdiff checks for the touched paths\r\n\r\nUse an interpreter-bound test command such as `python -m pytest` when a bare executable may resolve to a different Python environment than the source under test.\r\n\r\n## Event Design Guide\r\n\r\n| Situation | Useful safe fields | Avoid |\r\n|---|---|---|\r\n| Queue operation | generation, queue size, item count | payload, raw key |\r\n| Retrieval | mode, result count, cached chars, applied | query, document body |\r\n| Session lifecycle | short hash, turn, cancelled count | raw session ID, messages |\r\n| Background failure | operation, attempt, exception class | exception message, traceback by default |\r\n| Scheduler | checkpoint status, delay bucket, classifier configured | full timestamps tied to user data when unnecessary |\r\n| Memory processing | action enum, target enum, character count | memory content, tool arguments |\r\n\r\n## Pitfalls\r\n\r\n1. **Success-only instrumentation** — the system is still opaque when the worker fails.\r\n2. **Logging exception strings** — storage errors frequently contain absolute paths; validation errors may echo user input.\r\n3. **Raw correlation IDs** — session, chat, document, and candidate IDs can be private even without content.\r\n4. **Logging before validation** — malformed hostile input can reach logs unchanged.\r\n5. **Over-instrumenting hot loops** — prefer one transition event with counts to per-item logs.\r\n6. **Changing host logging configuration from a library** — emit records; do not seize global handlers or levels.\r\n7. **Racy tests** — do not assert that a fast worker handle must still exist after dispatch.\r\n8. **Using DEBUG as permission to leak** — log level controls volume, not data classification.\r\n\r\n## Reference Files\r\n\r\n- `references\u002Fmemory-provider-lifecycle-logging.md` — worked event taxonomy and regression-test pattern for a provider with queues, prefetch, session switching, timers, and idle workers.\r\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":37,"description":7},"Masia","1.0.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"observability","logging","privacy","debugging","testing",[35,36],"test-driven-development","systematic-debugging",[38,39,40],"linux","macos","windows","main","a3f3199bb87ec3c91248f68a39d88527e1847ae9","skills\u002Fsoftware-development\u002Fprivacy-safe-observability","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content","https:\u002F\u002Fgithub.com\u002Fchaorenex1","https:\u002F\u002Fblog.aduib.com","A programmer whose only hobby in life is coding","2026-10-20 00:34:32",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add chaorenex1\u002Fhermes-home-content --skill privacy-safe-observability",{"tool":55,"command":56},"bunx","bunx skills add chaorenex1\u002Fhermes-home-content --skill privacy-safe-observability",{"tool":58,"command":59},"pnpm","pnpm dlx skills add chaorenex1\u002Fhermes-home-content --skill privacy-safe-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fprivacy-safe-observability\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmemory-provider-lifecycle-logging.md","REFERENCE","参考文档",3686,"https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fprivacy-safe-observability\u002Freferences\u002Fmemory-provider-lifecycle-logging.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F8GF32YD5MBQW2TGSRH1YP","web-retrieval-resilience","Web tools fail or search rules break: repair or fall back.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fweb-retrieval-resilience\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F8FP46QESQMCZ1KBT3TW3R","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F8ER6VXHBNVRQBZS7X08SE","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F8E4BQJ38KVQVM3MT20PYV","unreal-world-builder","开放世界与环境专家——精通 UE5 World Partition、Landscape、程序化植被、HLOD 和大规模关卡流式加载，打造无缝开放世界体验","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-world-builder\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F8D747SQW2FTP7GBSX38BR","unreal-technical-artist","Unreal Engine 视觉管线专家——精通材质编辑器、Niagara 特效、程序化内容生成和 UE5 项目的美术到引擎管线","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-technical-artist\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F8CKHYJVZVBTN0321J88T2","unreal-systems-engineer","性能与混合架构专家——精通 C++\u002FBlueprint 边界、Nanite 几何体、Lumen GI 和 Gameplay Ability System，面向 AAA 级 Unreal Engine 项目","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-systems-engineer\u002FSKILL.md",[],[]]