菜单
Maintains an anchored-text feedback inbox for a knowledge store where every item attaches to an exact text anchor, carries an explicit resolution state, and is never silently deleted. Use when collecting, triaging, or resolving review feedback on extracted or generated pages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Runs the right deterministic extraction lane per office/email format and records each format's KNOWN losses UNDER A TEXT/CSV LANE in a coverage ledger so a faithful extract never masquerades as complete. Use when extracting docx/xlsx/msg/pdf/pptx sources whose richest content (formulas, charts, diagrams, attachments, images, speaker notes) does not survive a text/CSV dump.
Extracts a compressed archive (RAR/ZIP/7z) and then proves the extraction is byte-faithful by re-hashing every extracted file against the container's stored per-entry checksums — because an open-source decoder can report success while silently writing wrong bytes at the correct size (presence and size are NOT fidelity). Falls back across decoders (7z, bsdtar, official unrar) for entries one engine mis-decodes, and reports the exact set of files that no available decoder can reproduce. Use when extracting any archive before its contents enter an ingestion pipeline, especially RAR4 archives or when only partial decoders (p7zip, libarchive) are installed.
Scores committed extracts against an independent extraction engine (a different codebase than the pipeline lane) to produce measured per-lane precision/recall, with two-tier numeric scoring and a hard rule that every sub-1.0 number is attributed to a named cause. Use when a conversion lane needs correctness evidence beyond the fidelity verify loop — turning "we believe the extracts are faithful" into per-lane measured numbers.
Runs an independent adversarial verification loop on a produced change (extraction code, corpus batch, or page set) until a clean PASS — the producer never self-certifies, the reviewer is prompted to refute and to build runnable reproducers for code findings, and every fix is gated on re-running the reviewer's own reproducer. Use when a change must earn justified confidence before merge, especially pipeline-code changes where a plausible fix can be narrower than the defect class.
Independently reviews a batch of source-extract reference pages against the source binary so that no prose claims more than the committed extract supports — checking hash match, extract fidelity, and that every quoted figure traces to a committed extract with a cross-reference treated as not-a-quote and a derived number as not-quoted. Use when reviewing extracted/source-derived pages before merge, especially text-faithful pages whose prose may overreach.
Classifies XLS/XLSX workbooks before extraction and requires a traceable input data or logic contract, code artifact, and verified output artifact for a ten-file canary. Use when spreadsheet files may contain formulas, named ranges, charts, cached values, protection, or mixed data and calculation logic.
| name | audit-feedback-loop |
| description | Maintains an anchored-text feedback inbox for a knowledge store where every item attaches to an exact text anchor, carries an explicit resolution state, and is never silently deleted. Use when collecting, triaging, or resolving review feedback on extracted or generated pages. |
| license | CC-BY-4.0 |
| compatibility | Requires a feedback store keyed by stable text anchors; no external dependency |
| metadata | {"version":"1.0","enforcement_level":"L1","status":"template","incident_refs":"feedback-silent-delete","params":"action:enum(add,list,resolve)"} |
Template skill (doc 08). Feedback that is deleted on resolution loses the audit trail that makes a knowledge store defensible. Every item is anchored and state-tracked instead.
/audit-feedback <add|list|resolve> [args]
open → acknowledged → resolved | wontfix | superseded
(Never deleted. A resolved item is closed with a reason, kept for audit.)
open.open/acknowledged
items past an age threshold.| Rule | Why |
|---|---|
| Anchored to exact text | Vague feedback can't be verified as addressed |
| Never silently delete | Resolved-with-reason preserves the audit trail |