nwave-ai/nw-source-verification
Source reputation tiers, cross-referencing methodology, bias detection, and citation format requirements
npx skills add https://github.com/nWave-ai/nWave --skill nw-source-verification
Validate every source against the trusted source domains provided via prompt context.
| Tier | Score | Examples | Verification |
|------|-------|---------|-------------|
| High | 1.0 | Academic (*.edu, arxiv.org, ieee.org), Official (*.gov, w3.org, ietf.org), Tech docs (developer.mozilla.org), OSS foundations (apache.org, cncf.io) | Standard citation |
| Medium-High | 0.8 | Industry leaders (martinfowler.com, stackoverflow.com, infoq.com) | Cross-ref with 1+ high-tier |
| Medium | 0.6 | Community (medium.com verified experts, dev.to, hashnode.com) | Author verification + 3-source cross-ref |
| Excluded | 0.0 | Unverified blogs (*.blogspot.com, wordpress.com), quora.com, pastebin.com | Reject, log warning, find alternative |
Evaluate before citing:
When bias detected: note in Source Analysis, reduce confidence.
[1] {Author/Organization}. "{Title}". {Publication/Website}. {Date}. {Full URL}. Accessed {YYYY-MM-DD}.
Source URL | Domain | Access date | Reputation score (from tiers) | Verification status
Mark "[Paywalled]"/"[Restricted Access]" | Provide URL | Find open-access alternative | Note in Knowledge Gaps
Take nwave-ai/nw-source-verification from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.