[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EBTSVRG4FM36HPE3X42T57":3,"skill-same:01M7EBTSVRG4FM36HPE3X42T57":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7EBTSVRG4FM36HPE3X42T57","case-review",null,"Quality-gate review of a reverse-engineering or assessment case package: scope readiness, Evidence-to-Finding-to-Path traceability, work-item coverage, timeline consistency, and artifact hashes.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fcase-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: case-review\ndescription: \"Quality-gate review of a reverse-engineering or assessment case package: scope readiness, Evidence-to-Finding-to-Path traceability, work-item coverage, timeline consistency, and artifact hashes.\"\nrisk: safe\nsource: \"https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill\"\nsource_repo: \"zhaoxuya520\u002Freverse-skill\"\nsource_type: community\ndate_added: \"2026-08-25\"\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n# Evidence Graph Review\n## When to Use\n\n- Before delivering an analysis report, verify traceability and completeness.\n- Auditing whether conclusions are backed by recorded evidence.\n\n\nUse this skill when a reverse engineering, forensics, CTF, or authorized security case needs a defensible handoff. It audits the existing `work\u002F\u003Ccase>\u002F` package without changing the case or touching a target.\n\n## Scope\n\nThis skill covers:\n\n- Scope metadata and target-activity readiness\n- Evidence record structure and reproducibility fields\n- References from work items and timeline entries to Evidence\n- Structured Findings and Paths in report Markdown\n- Optional SHA-256 verification for case-local artifacts\n- A Markdown or JSON review result for a report handoff\n\nIt MUST NOT perform reconnaissance, exploitation, dynamic instrumentation, or target changes. Those actions belong to the routed analysis skill and require the case scope gate.\n\n## Tool dependencies\n\n| Tool | Required | Purpose | Auto-bootstrap |\n|------|----------|---------|---------------|\n| Python 3.9+ | Yes | Runs the read-only case review script | No, use the platform Python installation |\n\nNo network access or third-party package is required.\n\n## Workflow\n\n### Phase 1: Intake\n\nRun the review against the existing case directory:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --format markdown\n```\n\nConfirm that `scope.md`, `timeline.md`, `workitems.md`, and `evidence\u002F` are present. A non-strict review reports scope warnings while a strict review treats warnings as handoff blockers.\n\n## 建议下一步（选一个编号）\n\n1. 修复 scope.md 中的授权、范围或 network_profile 字段\n2. 继续检查 Evidence 记录的可复现命令和来源\n3. 导出当前 review 结果并附到阶段性报告\n4. 换 JSON 输出接入 CI 或其他审查工具\n5. 暂停，先确认审查范围\n\n### Phase 2: Traceability\n\nReview the checks for:\n\n- Evidence IDs that do not exist\n- Findings without `evidence_ids`\n- Paths without an allowed `path_type` or Evidence reference\n- Work items and timeline entries pointing to unknown Evidence\n- Unlinked Evidence records\n- Validated Findings with low confidence\n\nAn offline observation may use `repro_command: n\u002Fa` only when its `notes` field explicitly documents the offline limitation.\n\nUse JSON when another tool needs stable fields:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --format json\n```\n\n## 建议下一步（选一个编号）\n\n1. 补写缺失的 Evidence，并保留原始命令\n2. 将候选 Finding 绑定到 Evidence 后重新审查\n3. 为调用链或攻击链补充 P-id 和 Path 步骤\n4. 生成 Markdown handoff summary\n5. 换回 PRIMARY skill 继续分析\n\n### Phase 3: Fixity verification\n\nWhen an Evidence record contains both `content_hash` and `artifact_path`, verify the case-local artifact:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --verify-hashes --strict\n```\n\nThe script accepts `sha256:\u003C64 hex characters>` and checks that the artifact remains inside the case root. A hash mismatch is a hard failure.\n\nThe PowerShell Evidence helper can record a hash while appending a record:\n\n```powershell\npowershell -File skills\u002Fscripts\u002Fappend-evidence.ps1 -CaseRoot work\\\u003Ccase> -Id E-001 -Title \"Sample hash\" -ReproCommand \"sha256sum evidence\u002Fsample.bin\" -ArtifactPath \"evidence\\sample.bin\"\n```\n\n## 建议下一步（选一个编号）\n\n1. 修复 hash mismatch 或替换已污染的工作副本\n2. 为未固定的原始文件补充 SHA-256 和 artifact_path\n3. 继续进入报告生成阶段\n4. 导出 JSON 结果供 CI 保存\n5. 暂停并请求人工复核\n\n### Phase 4: Handoff\n\nUse strict mode before a final report or specialist handoff:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --strict --format markdown > work\u002F\u003Ccase>\u002Freport\u002Fcase-review.md\n```\n\nThe command is read-only with respect to the case unless shell redirection is explicitly used to save its output. The review is not legal advice and does not replace organizational evidence handling procedures.\n\n## 建议下一步（选一个编号）\n\n1. 将通过的 review 结果交给 `docs-generator\u002F` 生成正式报告\n2. 回到 PRIMARY skill 补齐新的分析证据\n3. 归档 Markdown 和 JSON review 结果\n4. 暂停并请求人工复核\n\n## Language behavior contract\n\n- Internal reasoning, tool selection, and phase control: English.\n- User-visible messages, section labels, reports, and next-step menus: Chinese unless the user requests another language.\n- Default bilingual labels place Chinese first and English second, separated by `\u002F`.\n\n## Bootstrap boundary\n\nThis skill has no third-party dependency. If Python 3 is unavailable, the only allowed recovery action is the repository bootstrap path when a Python capability is registered for the current platform. If no such capability is registered, stop and report the missing runtime. Do not guess executable paths, download packages, or perform a manual install from inside this skill.\n\n## Routing context\n\n**Upstream entry**: any reverse, forensics, CTF, or authorized security skill that has produced a case package.\n\n**Downstream exit**: `docs-generator\u002F` for a formal report, or the original PRIMARY skill when the graph is incomplete.\n\n**Related modules**: `ops\u002Fevidence-finding-path.md`, `ops\u002Ftimeline-workitem.md`, `digital-forensics\u002F`, `reverse-engineering\u002F`, and `docs-generator\u002F`.\n\n## References\n\n- [NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response](https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F86\u002Ffinal)\n- [SWGDE Best Practices for Computer Forensic Acquisitions](https:\u002F\u002Fwww.swgde.org\u002Fdocuments\u002Fpublished-complete-listing\u002F17-f-002-2-1\u002F)\n- [SWGDE Best Practices for Archiving Digital and Multimedia Evidence](https:\u002F\u002Fwww.swgde.org\u002Fdocuments\u002Fpublished-complete-listing\u002F19-f-003-best-practices-for-archiving-digital-and-multimedia-evidence\u002F)\n\n## 任务完成自检\n\n- [ ] 我是否审查了 scope.md、timeline.md、workitems.md 和 evidence\u002F？\n- [ ] 所有 Finding 是否引用了现存 Evidence？\n- [ ] 所有 Path 是否包含合法 path_type 和 Evidence 引用？\n- [ ] 是否执行了 hash verification，或记录了未执行原因？\n- [ ] 是否以 strict 模式重新运行并保存了 review 结果？\n\n## Limitations\n\n- Expects a structured case layout (scope, evidence, findings); ad-hoc notes need pre-organization.\n- Reviews documentation quality, not the technical correctness of findings.\n\n> Adapted from [zhaoxuya520\u002Freverse-skill](https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill) (MIT).\n","# Evidence Graph Review\n## When to Use\n\n- Before delivering an analysis report, verify traceability and completeness.\n- Auditing whether conclusions are backed by recorded evidence.\n\n\nUse this skill when a reverse engineering, forensics, CTF, or authorized security case needs a defensible handoff. It audits the existing `work\u002F\u003Ccase>\u002F` package without changing the case or touching a target.\n\n## Scope\n\nThis skill covers:\n\n- Scope metadata and target-activity readiness\n- Evidence record structure and reproducibility fields\n- References from work items and timeline entries to Evidence\n- Structured Findings and Paths in report Markdown\n- Optional SHA-256 verification for case-local artifacts\n- A Markdown or JSON review result for a report handoff\n\nIt MUST NOT perform reconnaissance, exploitation, dynamic instrumentation, or target changes. Those actions belong to the routed analysis skill and require the case scope gate.\n\n## Tool dependencies\n\n| Tool | Required | Purpose | Auto-bootstrap |\n|------|----------|---------|---------------|\n| Python 3.9+ | Yes | Runs the read-only case review script | No, use the platform Python installation |\n\nNo network access or third-party package is required.\n\n## Workflow\n\n### Phase 1: Intake\n\nRun the review against the existing case directory:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --format markdown\n```\n\nConfirm that `scope.md`, `timeline.md`, `workitems.md`, and `evidence\u002F` are present. A non-strict review reports scope warnings while a strict review treats warnings as handoff blockers.\n\n## 建议下一步（选一个编号）\n\n1. 修复 scope.md 中的授权、范围或 network_profile 字段\n2. 继续检查 Evidence 记录的可复现命令和来源\n3. 导出当前 review 结果并附到阶段性报告\n4. 换 JSON 输出接入 CI 或其他审查工具\n5. 暂停，先确认审查范围\n\n### Phase 2: Traceability\n\nReview the checks for:\n\n- Evidence IDs that do not exist\n- Findings without `evidence_ids`\n- Paths without an allowed `path_type` or Evidence reference\n- Work items and timeline entries pointing to unknown Evidence\n- Unlinked Evidence records\n- Validated Findings with low confidence\n\nAn offline observation may use `repro_command: n\u002Fa` only when its `notes` field explicitly documents the offline limitation.\n\nUse JSON when another tool needs stable fields:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --format json\n```\n\n## 建议下一步（选一个编号）\n\n1. 补写缺失的 Evidence，并保留原始命令\n2. 将候选 Finding 绑定到 Evidence 后重新审查\n3. 为调用链或攻击链补充 P-id 和 Path 步骤\n4. 生成 Markdown handoff summary\n5. 换回 PRIMARY skill 继续分析\n\n### Phase 3: Fixity verification\n\nWhen an Evidence record contains both `content_hash` and `artifact_path`, verify the case-local artifact:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --verify-hashes --strict\n```\n\nThe script accepts `sha256:\u003C64 hex characters>` and checks that the artifact remains inside the case root. A hash mismatch is a hard failure.\n\nThe PowerShell Evidence helper can record a hash while appending a record:\n\n```powershell\npowershell -File skills\u002Fscripts\u002Fappend-evidence.ps1 -CaseRoot work\\\u003Ccase> -Id E-001 -Title \"Sample hash\" -ReproCommand \"sha256sum evidence\u002Fsample.bin\" -ArtifactPath \"evidence\\sample.bin\"\n```\n\n## 建议下一步（选一个编号）\n\n1. 修复 hash mismatch 或替换已污染的工作副本\n2. 为未固定的原始文件补充 SHA-256 和 artifact_path\n3. 继续进入报告生成阶段\n4. 导出 JSON 结果供 CI 保存\n5. 暂停并请求人工复核\n\n### Phase 4: Handoff\n\nUse strict mode before a final report or specialist handoff:\n\n```bash\npython3 skills\u002Fcase-review\u002Fscripts\u002Freview_case.py work\u002F\u003Ccase> --strict --format markdown > work\u002F\u003Ccase>\u002Freport\u002Fcase-review.md\n```\n\nThe command is read-only with respect to the case unless shell redirection is explicitly used to save its output. The review is not legal advice and does not replace organizational evidence handling procedures.\n\n## 建议下一步（选一个编号）\n\n1. 将通过的 review 结果交给 `docs-generator\u002F` 生成正式报告\n2. 回到 PRIMARY skill 补齐新的分析证据\n3. 归档 Markdown 和 JSON review 结果\n4. 暂停并请求人工复核\n\n## Language behavior contract\n\n- Internal reasoning, tool selection, and phase control: English.\n- User-visible messages, section labels, reports, and next-step menus: Chinese unless the user requests another language.\n- Default bilingual labels place Chinese first and English second, separated by `\u002F`.\n\n## Bootstrap boundary\n\nThis skill has no third-party dependency. If Python 3 is unavailable, the only allowed recovery action is the repository bootstrap path when a Python capability is registered for the current platform. If no such capability is registered, stop and report the missing runtime. Do not guess executable paths, download packages, or perform a manual install from inside this skill.\n\n## Routing context\n\n**Upstream entry**: any reverse, forensics, CTF, or authorized security skill that has produced a case package.\n\n**Downstream exit**: `docs-generator\u002F` for a formal report, or the original PRIMARY skill when the graph is incomplete.\n\n**Related modules**: `ops\u002Fevidence-finding-path.md`, `ops\u002Ftimeline-workitem.md`, `digital-forensics\u002F`, `reverse-engineering\u002F`, and `docs-generator\u002F`.\n\n## References\n\n- [NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response](https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F86\u002Ffinal)\n- [SWGDE Best Practices for Computer Forensic Acquisitions](https:\u002F\u002Fwww.swgde.org\u002Fdocuments\u002Fpublished-complete-listing\u002F17-f-002-2-1\u002F)\n- [SWGDE Best Practices for Archiving Digital and Multimedia Evidence](https:\u002F\u002Fwww.swgde.org\u002Fdocuments\u002Fpublished-complete-listing\u002F19-f-003-best-practices-for-archiving-digital-and-multimedia-evidence\u002F)\n\n## 任务完成自检\n\n- [ ] 我是否审查了 scope.md、timeline.md、workitems.md 和 evidence\u002F？\n- [ ] 所有 Finding 是否引用了现存 Evidence？\n- [ ] 所有 Path 是否包含合法 path_type 和 Evidence 引用？\n- [ ] 是否执行了 hash verification，或记录了未执行原因？\n- [ ] 是否以 strict 模式重新运行并保存了 review 结果？\n\n## Limitations\n\n- Expects a structured case layout (scope, evidence, findings); ad-hoc notes need pre-organization.\n- Reviews documentation quality, not the technical correctness of findings.\n\n> Adapted from [zhaoxuya520\u002Freverse-skill](https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill) (MIT).\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"safe","https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill","2026-08-25","zhaoxuya520\u002Freverse-skill","community","https:\u002F\u002Fgithub.com\u002Fzhaoxuya520\u002Freverse-skill\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Fcase-review",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill case-review",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill case-review",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill case-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fcase-review\u002FSKILL.md",true,[],[53,61,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":60},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":60},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":60},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":60},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":60},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]