Verification Before Recommend
- Apply verification discipline before recommending state-changing actions or making load-bearing claims about local or external state that has not been directly observed this session. Use for installs, setup commands, config/file changes, repo/tool/package claims, factual disagreements, and next-step recommendations that depend on current state. Skip pure explanation, already-observed facts, user intent claims, and scratch-only operations with no claims about their effect.
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Install (Claude Code):
cp -r verification-before-recommend ~/.claude/skills/- Adoption: 1 repos
- Upkeep: 52.0
- Freshness: 73.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- GitHub stars: 1
- Contributors: 1
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
source ↗ · skill:shadiazzeh11/verification-before-recommend
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-09 · scorer s5 · how · something wrong here?