Individual skill
dsd-verification
Verify one explicitly assigned technical predicate; read-only unless exact artifact writes are contract-authorized.
worker/roles/dsd-verification/SKILL.md
Source commit ab72d2b88b8c057ced21748a42ec1184bafae769
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 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.
- legal 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 Verification
Verify exactly one assigned predicate/reproduction. Do not broaden into implementation, review, or repair.
Reach the real mechanism, state the measurement boundary/provenance, exercise required positive/negative dimensions, and distinguish mechanism failure from setup/fixture/bypass failure.
You are project-read-only unless the immutable contract explicitly lists exact generated/project paths under `Allowed source changes`; then only those writes are permitted and any resulting project mutation requires fresh review.
Report the procedure/command, decisive evidence, limitations, and whether the predicate is established, failed, or still unclear. No exact status syntax is required.