skills/CitationHygiene/SKILL.md
Cite origins for every factual data point (number, date, limit, rate, threshold) via markdown reference-style links. USE WHEN writing docs, ADRs, READMEs, or any file that asserts factual claims.
npx skillsauth add n4m3z/forge-core CitationHygieneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Every factual data point (number, date, limit, rate, threshold) must cite its origin via a markdown reference-style link. Unsourced claims are unreliable and unverifiable.
Inline reference: ([source][OWASP]) with [OWASP]: https://... at the bottom of the file. Labels are mnemonic abbreviations derived from the source name, not numbers.
Good:
OWASP lists SQL injection as #1 in the top 10 ([2021 list][OWASP]).
[OWASP]: https://owasp.org/Top10/
Bad:
OWASP lists SQL injection as #1 in the top 10.
(Missing citation — reader cannot verify.)
OWASP lists SQL injection as #1 in the top 10 ([source][1]).
[1]: https://owasp.org/Top10/
(Numeric label — unreadable at the call site.)
[OWASP], [MADR], [RFC7519]) — not [1], [2]development
Reactive correction and root-cause fix. USE WHEN something went wrong, user is frustrated, demands a correction, says wtf, what the hell, why did you, that's wrong, this is broken, no not that, stop. Executes the immediate fix, then hunts the upstream artifact that caused it and creates a corrective change.
development
Decompose a research question into sub-queries, spawn parallel WebResearcher agents per angle, synthesize findings with citations and explicit confidence. USE WHEN the user asks to research, investigate, look online, look up, dig into, find sources, gather evidence, or survey what's known about a topic. Single-pass; for multi-round adversarial research use ResearchCouncil in forge-council.
tools
Author project documentation that future humans (and AI sessions) actually read. Covers TLDRs for tools, READMEs, runbooks, journals. USE WHEN write documentation, create tldr, tool one-pager, document a cli, write readme, runbook, journal entry, capture knowledge about a tool, distill a session into reusable notes.
development
Review your own staged changes via a code-review TUI before triggering a commit. USE WHEN about to commit, walking through your own staged diff, self-reviewing before approval, tuicr, revdiff, git diff cached.