raisedadead/evidence-protocol
plugins/dp-cab/skills/evidence-protocol/SKILL.md
Use when an implementation agent needs to verify claims are grounded in evidence, not generated from memory.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins evidence-protocolInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:48 PM1.8s1 file scanned
SKILL.md
- name:
- evidence-protocol
- description:
- Use when an implementation agent needs to verify claims are grounded in evidence, not generated from memory.
- user-invocable:
- false
Evidence Protocol
Before claiming any fact, follow this sequence:
- IDENTIFY — What command or file read proves this claim?
- RUN — Execute the command or read the file. Full, fresh, complete.
- READ — Read the full output. Check exit code.
- VERIFY — Does the output confirm the claim?
- CLAIM — Only now may you make the claim.
"Should pass" is not evidence. Run the command and paste the output.
Rules
- Every claim must cite file:line or be marked [UNVERIFIED]
- Verify before assuming — run --help, read docs, check source
- Never fabricate external tool behavior
- Never assert facts about libraries, APIs, or tools without checking
- Default severity SUGGESTION for unverified findings
- If your task has a
## Ground Truthsection, use those values directly — do not research what is already provided
Related Skills
raisedadead/self-develop
development
VerifiedTrustedCommunity
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/setup
tools
VerifiedTrustedCommunity
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/tdd
development
VerifiedTrustedCommunity
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/spec
testing
VerifiedTrustedCommunity
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.
4SKILL.mdUpdated Apr 18, 2026