preetamnath/vet-fact
skills/vet-fact/SKILL.md
Judge whether a candidate fact earns a durable-doc line: keep only what a future agent would get the wrong answer without; cut anything derivable from code, setup, breadcrumb, or a restated default. TRIGGER when: user asks 'does this belong in CLAUDE.md / a rule / the docs', 'is this worth keeping/writing down', 'should this be a comment'; vetting or pruning a fact before it's filed or shaped.
$ install --global
skillsauthnpx skillsauth add preetamnath/agent-skills vet-factInstall 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: Jun 13, 2026, 6:49 AM134.5s1 file scanned
SKILL.md
- name:
- vet-fact
- description:
- Judge whether a candidate fact earns a durable-doc line: keep only what a future agent would get the wrong answer without; cut anything derivable from code, setup, breadcrumb, or a restated default. TRIGGER when: user asks 'does this belong in CLAUDE.md / a rule / the docs', 'is this worth keeping/writing down', 'should this be a comment'; vetting or pruning a fact before it's filed or shaped.
Vet Fact
Primitive: WORTH — does this candidate fact deserve a durable-doc line at all?
Steps
- State the fact in one line, then apply the gate: would a future agent get the wrong answer without it? If the agent could recover it from the code,
ls, or lint config, it fails — don't write it. - Run the does-NOT-belong filter — cut on any hit:
- Setup / onboarding (belongs in README).
- Historical breadcrumbs: dates, plan IDs, commit SHAs, supersedes/originally notes, completion summaries, deferred-item lists.
- Restated framework or harness defaults.
- Drift-prone literals: hex codes, version pins, exact syntax — unless the literal is itself load-bearing.
- Confirm it matches a belongs category:
- Gotcha, anti-pattern, or dead-code warning.
- A cross-file coupling invisible from any single file.
- A convention that contradicts the obvious default.
- Design rationale that clears Step 5's selection filter.
- A pointer carrying a must-know-before-you-touch obligation.
- Provenance carve-out — don't mistake evidence for breadcrumb. A quirk's
Discovered: YYYY-MM (sha)stamp is a freshness anchor (how stale the workaround's premise is), not historical narrative. Keep it; a TRIM must never strip per-entry provenance. - If it's rationale ("why"), keep it only when a tempting wrong alternative existed. That rejected alternative is the selection filter: no tempting wrong path → the choice is self-evident → don't record it. (E.g. "polls every 60s — webhooks drop silently during bulk ops" earns a line because webhooks were the tempting wrong path.) A kept rationale is a constraint — the reason is the fact itself; emit it as the
rationalecategory (Step 7). - Check it isn't already carried. WORTH is corpus-relative: a fact an existing doc, rule, or comment already states is not a fresh keep. Single-file-visible duplication you catch alone; coupling and cross-doc dedup need the other file(s) — flag, don't force.
- Verdict: keep or cut, with the one-line reason — and, on a keep, the fact's category (gotcha / coupling / convention / rationale / pointer).
Related Skills
preetamnath/refine-file
testing
VerifiedTrustedCommunity
Audit one instruction file by composing the durable-instruction lenses over it — vet-fact (WORTH: does each fact earn a line?), place-fact (PLACE: is it in the right home?), tighten-instruction (SHAPE: tighten the line). Pick the subset the file needs: shape-only, worth+shape, or worth+place+shape. A misplaced fact can be relocated to its right home on your approval, or deferred for a durable-docs-update batch. TRIGGER when: user wants a skill file or durable doc (CLAUDE.md, a rule, ARCHITECTURE.md) audited for what to keep, where it belongs, and how it reads; user says 'refine/audit this file', 'prune and tighten this doc', 'what here is worth keeping'. For shape-only tightening, tighten-file is the leaner sibling.
2SKILL.mdUpdated Jun 13, 2026
preetamnath/place-fact
development
VerifiedTrustedCommunity
Route a kept fact to its durable home by delivery trigger and most-local-wins — across in-file comment, nested CLAUDE.md, path-scoped rule, root CLAUDE.md, ARCHITECTURE.md, or a skill. TRIGGER when: user asks 'where should this go', 'which file/rule/home does this belong in', 'is this in the right place', 'should this be a pointer'; placing or re-homing a fact already judged worth keeping.
2SKILL.mdUpdated Jun 13, 2026
preetamnath/write-plan
development
VerifiedTrustedCommunity
Sequence a locked spec into dependency-ordered, wave-grouped tasks. TRIGGER when: user says 'build the plan' or 'sequence this'; a spec needs slicing into parallel-safe waves.
2SKILL.mdUpdated Jun 12, 2026
preetamnath/tech-design
testing
VerifiedTrustedCommunity
Turn a locked product/UX spec into technical design — the HOW: architecture, data shapes, signatures, file layout. TRIGGER when: user asks how to implement a spec'd feature; user wants architecture, data-shape, or file-layout decisions; user says 'tech design' or 'design the implementation'.
2SKILL.mdUpdated Jun 12, 2026