From prose
Source tier definitions, citation formatting, verification patterns, and hallucination prevention. Load when writing content that requires external evidence, statistics, or expert claims. Covers what sources to use, how to cite them, and what to avoid.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prose:citation-sourcingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every statistic needs a named source. Every claim needs evidence or an explicit opinion label. Content backed by named research gets cited; content backed by "studies show" does not.
Every statistic needs a named source. Every claim needs evidence or an explicit opinion label. Content backed by named research gets cited; content backed by "studies show" does not.
Use the highest-tier source available for each claim.
| Tier | Authority | Examples | Use For |
|---|---|---|---|
| Tier 1 | Highest | Academic journals, government data (BLS, Census), Gartner, Forrester, McKinsey | Key statistics, research findings, industry benchmarks |
| Tier 2 | High | HBR, WSJ, major news outlets, respected industry publications | Trends, expert opinions, case studies |
| Tier 3 | Acceptable | Established industry blogs with named authors, company research with methodology disclosed | Definitions, background, general context |
| Avoid | Insufficient | Anonymous blogs, content farms, undisclosed vendor marketing | Should never be primary sources |
Wikipedia is useful for discovering primary sources via its references — cite those primary sources directly rather than citing Wikipedia itself.
tavily_search to find the primary source.Make every reference traceable:
In the markdown output, cite sources inline. When a URL is available, use hyperlinks: "According to Gartner's 2024 CMO Survey, 73% of CMOs...". When no URL is available, use inline attribution: "According to Gartner's 2024 CMO Survey, 73% of CMOs...". Do not use footnotes or endnote-style references.
Target 2-5 external citations per 1,000 words for substantive content. More is fine for data-heavy pieces. Fewer is acceptable for opinion-focused content where claims are clearly framed as perspective.
Source recency depends on topic pace:
| Topic Type | Maximum Age | Examples |
|---|---|---|
| Fast-moving | 1-2 years | AI, social media, tech trends |
| Industry | 2-3 years | Marketing benchmarks, business strategy |
| Stable | 5+ years acceptable | Accounting principles, programming fundamentals |
When you recall a statistic but cannot name its specific source, use tavily_search to find the original. If the source can't be found: round the number and attribute it generally ("industry estimates suggest roughly half..."), or cut the statistic entirely. Never cite a precise number without a named source.
When credible sources disagree, present both: "Source A reports X, while Source B found Y." Don't silently pick one. Acknowledged disagreement builds trust.
When uncertain about a fact, verify it with tavily_search. If verification fails, generalize without a specific number, or cut the claim. An unverified number damages credibility more than a gap.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub birdseyeglobal/portage --plugin prose