rampstackco/claude-skills / skills/long-form-content-frameworks
long-form-content-frameworks
VerifiedPatterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 369 B |
| SKILL.md | skill md | 29.4 KB |
| references/attention-sustaining-techniques.md | markdown | 9.7 KB |
| references/breakouts-and-visualization.md | markdown | 10.4 KB |
| references/citation-and-source-authority.md | markdown | 10.4 KB |
| references/closing-patterns.md | markdown | 12.0 KB |
| references/common-long-form-failures.md | markdown | 11.6 KB |
| references/format-decision-framework.md | markdown | 10.6 KB |
| references/lede-patterns-for-long-form.md | markdown | 9.9 KB |
| references/section-weight-calibration.md | markdown | 9.4 KB |
| references/structural-archetype-patterns.md | markdown | 10.4 KB |
references/citation-and-source-authority.md
View on GitHub# Citation and source authority
Source hierarchy for long-form, citation density discipline, freshness norms, inline vs endnote conventions, and the citation-laundering anti-pattern.
Long-form pieces cite more, and cite more authoritatively, than blog posts. The reader is investing 30+ minutes; the writer owes them claims they can verify. Pieces that fail at citation discipline read as if the writer wanted authority without paying the verification cost.
---
## Source hierarchy
Sources are not interchangeable. The same claim cited from a peer-reviewed paper carries different weight than the same claim cited from a vendor blog post.
**Tier 1: Primary research.** Original studies, datasets, interviews, the writer's own data work. The writer is producing the data, not citing it. Highest authority. Pieces with primary research signal that the writer or team did the work.
**Tier 2: Authoritative secondary sources.** Peer-reviewed papers, government data (BLS, Census, equivalent), established research firms (Gartner, Forrester, Pew, IDC, etc.), primary reporting from credible outlets. The writer is citing rigorous secondary work where the source's reputation does the verification work.
**Tier 3: Industry-credible sources.** Vendor research with disclosed methodology, reputable trade publications, recognized expert practitioners with track records. The writer is citing sources that practitioners in the field would recognize as substantive even if they are not academically rigorous.
**Tier 4: Linked-aware secondary sources.** Reputable blogs, publications, and commentary where the source is verifying claims rather than just amplifying them. The writer is citing sources that did some level of verification work, even if the source is a blog post rather than a study.
**Tier 5 and below: Avoid.** Other content marketing pieces (citation laundering), "studies show" claims with no link, anonymous "experts," reposts of reposts, vendor marketing pages cited as research, AI-generated synthesis cited as primary source.
The discipline. Long-form arguments should cite from tiers 1-3 wherever possible. Tier 4 is fine for color and context but should not bear primary argumentative load. Tier 5 sources signal the writer did not do the verification work.
---
## Citation density
Citations should be roughly proportional to claim density.
**A piece making 30 falsifiable claims.** Roughly 30 citations or attributions to primary analysis. Each claim either points to a verifiable source or is identified as the writer's own analysis (in which case the analysis itself should be defended).
**A piece making 5 strong claims with extensive elaboration.** May need only 5 citations if the elaboration is reasoning rather than fact-claim. Manifestos and position pieces often work this way: a small number of central claims, deeply argued, with citations supporting the claims rather than every elaboration.
**The audit.** Mark every falsifiable claim in the piece. For each claim, check: is it cited, is it identified as the writer's own analysis, or is it floating? Floating claims are the failure mode. Either cite, attribute to the writer, or cut.
**The over-citation failure.** Some long-form pieces cite every sentence as if academic rigor were the goal. The result reads as a literature review, not a piece of editorial writing. Citations should support the argument, not perform credibility theater.
---
## Source freshness
Statistics older than 3 years for fast-moving topics need refresh or explicit acknowledgment.
**Fast-moving topics.** Technology, marketing tactics, AI capabilities, software stacks, social platforms. A 2018 stat in a 2026 piece on these topics signals stale research unless the writer is citing it specifically as historical context.
**Stable topics.** Behavioral psychology research, structural economics, mathematical results, established scientific consensus. A 2015 stat on these topics may be perfectly current.
**The acknowledgment pattern.** When citing older data on a fast-moving topic deliberately, acknowledge it: "A 2018 survey, the most recent rigorous data on the question, found..." The acknowledgment signals the writer knows the data is old and chose to cite it anyway, with reasoning.
**The hidden-stale-data failure.** Citing a "2024 study" that turns out to be a 2024 republication of 2019 data. Verify primary publication date before citing.
---
## Inline vs endnote citations
Two conventions for how citations appear.
**Inline links.** The cited source appears as a hyperlink within the prose. Reader clicks to verify. Common in editorial long-form, content marketing whitepapers, and most web-published research reports.
- Strength: keeps reader momentum; the prose flows without numerical interruptions.
- Weakness: harder to verify without leaving the page; less academically formal.
**Endnote-style citations.** Numbered footnotes at the end of the piece, with each citation numbered in the prose. Common in academic-influenced research reports, policy whitepapers, and some long-form published with print-style conventions.
- Strength: signals academic rigor; preserves the citation list for verification.
- Weakness: interrupts reading flow; readers rarely follow endnotes in web reading.
**The convention rule.** Pick one and stay consistent within the piece. Mixing conventions (some claims inline-linked, some endnoted) reads as inconsistent. The choice depends on audience expectations: B2B technical research often expects endnotes; editorial whitepapers usually expect inline.
**Hybrid: inline + bibliography.** Inline links throughout the piece plus a "sources" or "further reading" section at the end. Common compromise. Works well when the piece has both casual references and core sources.
---
## The citation-laundering anti-pattern
Citing other content marketing pieces as authoritative when the cited piece itself does not have primary support.
**The pattern.** Piece A claims X with a citation. Piece B cites A as the source for X. Piece C cites B. The original claim X may have been weak, made-up, or misinterpreted; each successive citation amplifies the appearance of authority without adding verification.
**How it happens.** A writer searching for support for a claim finds another content marketing piece making the same claim and links to it. The writer feels they have cited a source. The source is itself unsourced or weakly sourced. The chain of laundering can run several pieces deep.
**The cure.** When citing, follow the chain back. If the cited piece does not have primary or authoritative-secondary support, do not cite it. Either find a primary source, or remove the claim, or attribute it as the writer's own observation.
**Why it matters in long-form.** The reader is investing time. Citation laundering produces pieces that read as authoritative because of citation count but fall apart under verification. Readers who verify discover the laundering; readers who do not develop a slow-decaying trust in the writer.
---
## The own-analysis citation
When the writer is making a claim from their own analysis rather than citing a source, the claim should be visibly the writer's analysis with the analytical work shown.
**The pattern.** "Looking at the data across [scope], the pattern that emerges is X." The pattern claim is the writer's; the data is cited; the analytical work is described.
**The discipline.** Own-analysis claims still need defensibility. The writer should be able to defend, if challenged: where the data came from, how the analysis was performed, what alternative interpretations were considered.
**The hidden-claim failure.** Sentences that read as fact ("The reality is that programmatic SEO is dying") without acknowledgment that the claim is the writer's interpretation. If the claim is contested, frame it as the writer's view; if the claim is empirical, cite a source. The hidden middle (claim presented as fact when it is interpretation) is where readers lose trust.
---
## Quote attribution
Long-form pieces often include quotes from named experts, executives, or practitioners.
**Verification.** Every quote should be from a real person who actually said the words attributed to them. Hallucinated quotes (especially in AI-assisted long-form) are an ethical failure regardless of whether the position is plausibly something the named person might say. See `editorial-qa`'s fact-accuracy reference for the discipline.
**Context.** Quotes work best when the person's role is identified, the context of the statement is clear (interview, public statement, prior writing), and the quote earns its place by saying something specific.
**The throwaway-quote failure.** A generic quote ("Content is king," John Smith, CEO) that does not advance the argument. If the quote does not say something specific the prose alone cannot convey, cut it.
---
## Citation in research reports specifically
Research reports have particularly strict citation expectations because they are claiming primary research authority.
- **Methodology disclosed.** Sample size, recruitment method, dates, instrument design. Without these, the research is not verifiable.
- **Sample limits acknowledged.** What the sample does and does not represent. A sample of 300 marketers in B2B SaaS does not represent "marketers"; the report should not claim it does.
- **Statistical limits acknowledged.** Confidence intervals, margins of error, significance tests where applicable. Reports presenting cherry-picked data points without distribution context are weak research.
- **Original data made available.** Where possible, the underlying data should be shareable for verification. Reports that hide the data behind the headline findings invite skepticism.
---
## Methodology-level choices that stay in the public skill
The source hierarchy and tier definitions, the citation-density principle, the freshness rule and acknowledgment pattern, the inline-vs-endnote convention rule, the citation-laundering anti-pattern, the own-analysis discipline, the quote-attribution rules, the research-report citation expectations.
## Implementation choices that stay internal
Specific citation management tools the team uses. Specific bibliography generators integrated with the team's writing system. Specific link-checking automation that catches dead links and stale data. Specific data-publication conventions for research reports the team produces. The team's own internal source-tier classification when sources are ambiguous. These vary by team and tooling.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |