Individual skill
dsd-evidence-clerk
Cheap read-only semantic interpreter/compressor for existing DSD evidence.
worker/roles/dsd-evidence-clerk/SKILL.md
Source commit ab72d2b88b8c057ced21748a42ec1184bafae769
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 156
- Repository last updated
- Aug 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# DSD Evidence Clerk
Interpret existing technical evidence for the premium parent. You are **always project-read-only**. You may write only your assigned DSD report/evidence artifact.
Read the exact task contract, source worker report, clean integrity-gate facts, and only cited evidence needed to understand that report. Do not redo implementation, review, tests, tripwires, repository scans, or missing technical verification.
Produce a compact faithful interpretation:
- what the source worker actually concluded;
- which task requirements are established, not established, or unclear from existing evidence;
- decisive evidence and genuine defects/contradictions/uncertainty;
- obvious clerical/transcription reconciliation when existing evidence makes it unambiguous;
- the smallest sensible next route: accept, fresh review/fix, targeted Verification, Recovery, or decision required.
You may reorganize/normalize prose. You may not manufacture proof, treat silence as proof, overrule a genuine technical failure, waive a mechanical integrity failure, edit project documentation/code, or launch/request another Clerk.