[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AT1FQJAE1FQYAMDTF490Y4":3,"skill-same:01M7AT1FQJAE1FQYAMDTF490Y4":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing",null,"Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: white-paper-writing\ndescription: Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.\n---\n\n# White Paper Writing: The Complete Guide\n\n## What a white paper actually is\n\nA white paper is an **authoritative, evidence-driven document that educates readers about a complex issue while advancing a specific position or solution**. The critical tension: informational in form, persuasive in function.\n\nThe term traces to British government practice. The **Churchill White Paper of 1922** on Palestine is the earliest widely cited example — British government reports with blue covers (\"Blue Books\") were comprehensive; shorter reports received plain white covers. Subsequent landmark white papers shaped geopolitics. By the 1990s the term migrated into technology and business.\n\nToday the term encompasses four meaningfully different document types:\n\n| Type | Purpose | Audience | Key difference |\n|------|---------|---------|----------------|\n| **Government** | Policy proposals for future legislation | Parliamentarians, civil servants, public | Follows a Green Paper consultation; proposes legislation |\n| **Academic** (working paper) | Circulates preliminary findings without formal peer review | Researchers, funding agencies, fellow scholars | No external validation; credibility depends on institution + evidence quality |\n| **Corporate** | B2B lead generation and trust building | Technical evaluators, C-suite, purchasing teams | Educates potential buyers while positioning the sponsoring organization |\n| **Technical** | Specifications and architecture documentation | Engineers and implementers | More reference document than persuasive document |\n\n**Recognizing which tradition you are writing in determines everything** — citation density, length, structure, tone, and whether you include a call to action.\n\n## How white papers differ from neighboring genres\n\nWhite papers occupy a unique rhetorical niche. Knowing what they are not helps:\n\n| Document type | How it differs from a white paper |\n|--------------|----------------------------------|\n| **Case study** | Narrow focus on one customer's experience — \"looking down through a magnifying glass at one flower\" vs. white paper's \"looking up through a telescope at a whole galaxy\" |\n| **Research paper** | Communicates original findings with full methodological transparency; a white paper can selectively marshal evidence for a position |\n| **Technical report** | Comprehensive data and analysis without necessarily advocating a solution |\n| **Position paper** | Openly advocates; a white paper persuades through the *appearance* of objectivity |\n| **Blog post** | 300-2,000 words, informal; a white paper develops an idea rigorously across 2,500-7,000 words with cited evidence |\n\n## The three rhetorical foundations\n\nThe Purdue OWL captures the central discipline: \"If you advertise before convincing your readers of the truths of your argument, they are more likely to be turned off.\"\n\n**Ethos** (credibility): established through depth of research, institutional credibility, professional presentation, and citation of reputable third-party sources. Every claim needs a named, verifiable source. Citing Gartner, Forrester, academic journals, or government statistics builds credibility far more than citing your own materials.\n\n**Logos** (logical argument): the problem framing, evidence marshaling, and logical solution development. The argument structure must be airtight. Problem → cause analysis → solution that addresses the cause.\n\n**Pathos** (connecting to reader pain): enters through the problem statement, which connects to the reader's specific pain points and creates urgency. Without pathos, readers do not feel the problem is their problem.\n\n**The 80\u002F20 rule**: 80% of content should be genuinely educational and valuable; only 20% should reference your organization or offering. Invert this ratio and you have produced a brochure, not a white paper.\n\n## Audience types and how to adapt\n\n**C-suite readers** want: ROI implications, risk exposure, strategic fit, competitive implications. Give them: quantified business impact, regulatory risk, benchmark comparisons. They will read the executive summary and the conclusion; the body should stand alone for their direct reports.\n\n**Technical evaluators** want: architecture details, integration complexity, security posture, operational requirements. Give them: diagrams, specifications, comparison tables, technical proof points, references to standards.\n\n**Policy analysts** want: regulatory feasibility, precedent, stakeholder impact, implementation challenges. Give them: regulatory citations, cross-jurisdiction comparisons, case studies from comparable implementations.\n\n**Practical rule**: if you do not know who will read this, write for the technical evaluator — they are the most demanding audience and their approval is usually required before a purchase decision reaches the executive.\n\n## Classic structure for the corporate white paper (problem\u002Fsolution format)\n\nThis is Gordon Graham's \"chocolate\" format — the richest and most impactful. Use for: top-of-funnel thought leadership, executive influence, lead generation.\n\n### Cover page\nBenefit-oriented title. Five proven title formats:\n1. How-to: \"How to [achieve outcome] Without [common obstacle]\"\n2. Numbered: \"Five Ways [specific audience] Can [achieve outcome]\"\n3. Question: \"Why [common approach] Fails [specific audience] — and What to Do Instead\"\n4. Provocative: \"[Surprising claim that reframes the problem]\"\n5. New approach: \"The [New Approach] to [Established Problem]\"\n\nNothing undermines a white paper faster than an amateurish cover. Subtitle, company logo, author name and title, date, professional design.\n\n### Executive summary (250-350 words, ~7% of total)\nState: the problem, why it matters now, the proposed approach, key findings, who this is for. **Must stand alone** — many decision-makers read only this section. Write it last, after the rest of the paper is complete.\n\n### Introduction \u002F hook (450-700 words, ~13%)\nOpen with a compelling statistic, scenario, or provocative question. Establish relevance to the reader's world. State the paper's purpose and preview the structure. **Do not sell. Do not start with company history.**\n\nBad opening: \"This white paper introduces ABC company's new freight service.\"\nGood opening: \"This white paper discusses how to choose a freight service that best fits your needs.\"\n\n### Problem definition (600-900 words, ~18%)\nThree required elements per the George Mason University Writing Center:\n1. **Core problem**: the situation that needs to change\n2. **Cause**: what creates it (critical — how you characterize the cause determines which solutions appear logical)\n3. **Impact**: the harmful consequences, quantified with specific data\n\nReplace vague assertions with specific evidence: not \"employee engagement is low\" but \"across a 2024 survey of 500 enterprise IT teams, 67% reported [specific metric], costing an estimated $X per year in [specific consequence].\"\n\n**Do not mention your product.** Do not pose problems you cannot solve. Do not exaggerate — the reader will discount everything else if the problem feels inflated.\n\n### Background \u002F context (400-700 words, ~12%)\nProvide industry context, historical perspective, and an honest assessment of why prior approaches fell short. Demonstrate authoritative knowledge while keeping the narrative moving forward.\n\n### Solution overview (900-1,400 words, ~25% — the centerpiece)\nPresent your approach, framework, or methodology. Explain how it addresses the root causes identified in the problem section. Differentiate from prior approaches. Use case studies or analogies to illustrate.\n\n**Critical rule: do not name your specific product until the final paragraphs, if at all.** The reader should feel the solution is the logical, inevitable conclusion of the preceding analysis. If the solution section reads as a product pitch, the entire edifice collapses — the reader realizes they were manipulated, not educated.\n\n### Benefits and evidence (500-900 words, ~13%)\nQuantify ROI, efficiency gains, or risk reduction. Include case studies, third-party research validation, and expert citations. Use specific, verifiable data from named sources. Before-and-after comparisons are powerful. Avoid unsubstantiated claims and cherry-picked statistics.\n\n### Implementation considerations (300-600 words, ~9%)\nA realistic roadmap: steps, prerequisites, potential challenges, timeline, success indicators. Build confidence that the solution is achievable. **Do not make everything sound effortless** — readers distrust claims that understate complexity.\n\n### Conclusion and call to action (200-350 words, ~5%)\nSummarize the key argument. Restate urgency. Include a clear but subtle next step — schedule a consultation, download a tool, contact the team. Do not introduce new arguments. Do not pivot into a hard sell.\n\n### About the company (150-250 words)\nBrief overview of relevant expertise, credentials, notable clients, and contact information. Think credibility stamp, not brochure.\n\n### References\nCite all sources consistently. Hyperlink URLs for digital distribution.\n\n## Academic white paper structure (working paper \u002F technical report)\n\nApproximately 8,000 words \u002F 20 pages. Each section with recommended proportions:\n\n| Section | Length (words) | % of total |\n|---------|----------------|-----------|\n| Title page + abstract | 150-300 | 2% |\n| Table of contents | auto-generated | — |\n| Introduction | 800-1,200 | ~12% |\n| Literature review | 1,200-1,600 | ~18% |\n| Methodology | 800-1,200 | ~12% |\n| Analysis and discussion | 2,400-3,200 | ~35% |\n| Conclusions | 400-640 | ~6% |\n| Recommendations | 240-400 | ~4% |\n| References + appendices | as needed | — |\n\n**The abstract** (academic) vs. **executive summary** (corporate): abstracts are 150-300 words, self-contained, oriented toward scholarly readers; executive summaries are longer (1-2 pages), may include graphics, and target decision-makers who need actionable recommendations without reading the full document.\n\n**Literature review discipline**: organize thematically, not chronologically. Synthesize across sources to identify patterns, contradictions, and gaps. Conclude by showing how the literature identifies the gap your work fills. Avoid the annotated-bibliography-in-disguise format.\n\n## Evidence standards and citation\n\nCredibility hierarchy (highest to lowest):\n1. Primary research you conducted\n2. Peer-reviewed academic research\n3. Government and NGO data (NIST, Gartner, Forrester, IDC with sponsor disclosure)\n4. Industry analyst data (know that analysts are often funded by vendors being analyzed)\n5. Vendor-sponsored studies (must disclose; readers heavily discount)\n\n**Statistics need context**: \"40% improvement\" means nothing without a baseline, a sample size, a methodology, and a time frame. Always include: who collected the data, when, from how many respondents\u002Fsystems, using what methodology.\n\n**The 42% rule**: a 2021 survey found 42% of B2B buyers rated white papers as the most valuable content when researching a purchase, with 57% preferring them early in the buying process. The white paper is the most trusted format in the B2B buying journey — which is exactly why debasing the format with premature selling is so damaging.\n\n## Narrative arc: the story beneath the structure\n\nThe most memorable white papers have an underlying narrative arc:\n\n**Ordinary world**: the reader's current reality, the status quo. Establish this in concrete, specific terms — not abstract industry platitudes but the actual experience your reader is having.\n\n**Complication**: why the ordinary world is failing. The problem is getting worse, or the stakes just increased, or a new development makes the old approach obsolete. This is where urgency is established.\n\n**Resolution**: your approach, framework, or insight. This arrives only after the reader has fully understood the complication — the resolution is earned, not advertised.\n\n**Transformed world**: what the reader's world looks like after applying the approach. Specific, measurable, believable.\n\nThis arc maps to the classical white paper structure: Problem Definition = Ordinary World + Complication; Solution Overview = Resolution; Benefits = Transformed World.\n\n## The most common mistakes\n\n**The sales pitch in disguise** (48.1% of white papers reviewed in one survey were blatant product promotions): if the reader reaches the end feeling sold to rather than educated, the white paper has failed. The test: could you remove all company branding and still have a valuable document?\n\n**Vagueness without data**: every major claim needs a specific, sourced statistic or case study.\n\n**Excessive length**: the trend is toward shorter documents. A well-reasoned 6-page white paper beats a padded 15-page one.\n\n**Jargon overload**: define technical terms. Do not assume the reader has your acronym vocabulary.\n\n**Weak conclusions that restate the introduction**: conclusions should synthesize — draw together the threads into a landing that is more than the sum of the parts.\n\n**Poor alignment between problem and solution**: if the solution does not directly address the cause as characterized in the problem section, the argument collapses. Work backward: define the solution first, then characterize the cause in a way that makes your solution the logical response.\n\n## Formatting and length specifications\n\n**Length**: 2,500-7,000 words; 8-15 pages typical B2B corporate; government = variable; academic = 8,000-15,000 words.\n\n**Typography**:\n- Body: 11-12pt (Calibri, Garamond, or Georgia for digital; Times New Roman for print)\n- H1: 18-24pt\n- H2: 14-18pt\n- Captions: 8-10pt\n- Line spacing: 1.2-1.5× for published versions; double-space for review drafts\n- Optimal line length: 65-75 characters (45-90 maximum for readability)\n\n**Data visualization**: 65% of information is retained with visuals, compared to 10-20% with text alone. Use bar charts for comparisons, line graphs for trends, donut charts (preferred over pie) for part-to-whole. Apply brand colors consistently. Always label directly rather than using legends where possible.\n\n**Accessibility**: 4.5:1 minimum contrast ratio (WCAG 2.1 Level AA). Alt text for all meaningful images. Tagged PDFs for screen reader navigation.\n\n## Toolchain recommendations\n\n**Academic\u002Ftechnical**: LaTeX (Overleaf for collaboration) — precise typesetting, automated cross-referencing, BibLaTeX for citations. Essential packages: `geometry`, `hyperref`, `biblatex`, `booktabs`, `cleveref`.\n\n**Corporate**: Word + Styles system for consistent formatting and auto-generated TOC. Export to PDF. For highly designed versions, Adobe InDesign or Affinity Publisher.\n\n**Version-controlled technical writing**: Markdown + Pandoc + Git. Write in Markdown (one sentence per line for clean diffs), use YAML front matter for metadata, compile to PDF\u002FDOCX via Pandoc with `--citeproc` for citations.\n\n**Citation management**: Zotero (free, open-source, best browser capture) for most users; BibLaTeX\u002FBiber for LaTeX workflows; EndNote for large-scale systematic reviews with institutional licenses.\n","# White Paper Writing: The Complete Guide\n\n## What a white paper actually is\n\nA white paper is an **authoritative, evidence-driven document that educates readers about a complex issue while advancing a specific position or solution**. The critical tension: informational in form, persuasive in function.\n\nThe term traces to British government practice. The **Churchill White Paper of 1922** on Palestine is the earliest widely cited example — British government reports with blue covers (\"Blue Books\") were comprehensive; shorter reports received plain white covers. Subsequent landmark white papers shaped geopolitics. By the 1990s the term migrated into technology and business.\n\nToday the term encompasses four meaningfully different document types:\n\n| Type | Purpose | Audience | Key difference |\n|------|---------|---------|----------------|\n| **Government** | Policy proposals for future legislation | Parliamentarians, civil servants, public | Follows a Green Paper consultation; proposes legislation |\n| **Academic** (working paper) | Circulates preliminary findings without formal peer review | Researchers, funding agencies, fellow scholars | No external validation; credibility depends on institution + evidence quality |\n| **Corporate** | B2B lead generation and trust building | Technical evaluators, C-suite, purchasing teams | Educates potential buyers while positioning the sponsoring organization |\n| **Technical** | Specifications and architecture documentation | Engineers and implementers | More reference document than persuasive document |\n\n**Recognizing which tradition you are writing in determines everything** — citation density, length, structure, tone, and whether you include a call to action.\n\n## How white papers differ from neighboring genres\n\nWhite papers occupy a unique rhetorical niche. Knowing what they are not helps:\n\n| Document type | How it differs from a white paper |\n|--------------|----------------------------------|\n| **Case study** | Narrow focus on one customer's experience — \"looking down through a magnifying glass at one flower\" vs. white paper's \"looking up through a telescope at a whole galaxy\" |\n| **Research paper** | Communicates original findings with full methodological transparency; a white paper can selectively marshal evidence for a position |\n| **Technical report** | Comprehensive data and analysis without necessarily advocating a solution |\n| **Position paper** | Openly advocates; a white paper persuades through the *appearance* of objectivity |\n| **Blog post** | 300-2,000 words, informal; a white paper develops an idea rigorously across 2,500-7,000 words with cited evidence |\n\n## The three rhetorical foundations\n\nThe Purdue OWL captures the central discipline: \"If you advertise before convincing your readers of the truths of your argument, they are more likely to be turned off.\"\n\n**Ethos** (credibility): established through depth of research, institutional credibility, professional presentation, and citation of reputable third-party sources. Every claim needs a named, verifiable source. Citing Gartner, Forrester, academic journals, or government statistics builds credibility far more than citing your own materials.\n\n**Logos** (logical argument): the problem framing, evidence marshaling, and logical solution development. The argument structure must be airtight. Problem → cause analysis → solution that addresses the cause.\n\n**Pathos** (connecting to reader pain): enters through the problem statement, which connects to the reader's specific pain points and creates urgency. Without pathos, readers do not feel the problem is their problem.\n\n**The 80\u002F20 rule**: 80% of content should be genuinely educational and valuable; only 20% should reference your organization or offering. Invert this ratio and you have produced a brochure, not a white paper.\n\n## Audience types and how to adapt\n\n**C-suite readers** want: ROI implications, risk exposure, strategic fit, competitive implications. Give them: quantified business impact, regulatory risk, benchmark comparisons. They will read the executive summary and the conclusion; the body should stand alone for their direct reports.\n\n**Technical evaluators** want: architecture details, integration complexity, security posture, operational requirements. Give them: diagrams, specifications, comparison tables, technical proof points, references to standards.\n\n**Policy analysts** want: regulatory feasibility, precedent, stakeholder impact, implementation challenges. Give them: regulatory citations, cross-jurisdiction comparisons, case studies from comparable implementations.\n\n**Practical rule**: if you do not know who will read this, write for the technical evaluator — they are the most demanding audience and their approval is usually required before a purchase decision reaches the executive.\n\n## Classic structure for the corporate white paper (problem\u002Fsolution format)\n\nThis is Gordon Graham's \"chocolate\" format — the richest and most impactful. Use for: top-of-funnel thought leadership, executive influence, lead generation.\n\n### Cover page\nBenefit-oriented title. Five proven title formats:\n1. How-to: \"How to [achieve outcome] Without [common obstacle]\"\n2. Numbered: \"Five Ways [specific audience] Can [achieve outcome]\"\n3. Question: \"Why [common approach] Fails [specific audience] — and What to Do Instead\"\n4. Provocative: \"[Surprising claim that reframes the problem]\"\n5. New approach: \"The [New Approach] to [Established Problem]\"\n\nNothing undermines a white paper faster than an amateurish cover. Subtitle, company logo, author name and title, date, professional design.\n\n### Executive summary (250-350 words, ~7% of total)\nState: the problem, why it matters now, the proposed approach, key findings, who this is for. **Must stand alone** — many decision-makers read only this section. Write it last, after the rest of the paper is complete.\n\n### Introduction \u002F hook (450-700 words, ~13%)\nOpen with a compelling statistic, scenario, or provocative question. Establish relevance to the reader's world. State the paper's purpose and preview the structure. **Do not sell. Do not start with company history.**\n\nBad opening: \"This white paper introduces ABC company's new freight service.\"\nGood opening: \"This white paper discusses how to choose a freight service that best fits your needs.\"\n\n### Problem definition (600-900 words, ~18%)\nThree required elements per the George Mason University Writing Center:\n1. **Core problem**: the situation that needs to change\n2. **Cause**: what creates it (critical — how you characterize the cause determines which solutions appear logical)\n3. **Impact**: the harmful consequences, quantified with specific data\n\nReplace vague assertions with specific evidence: not \"employee engagement is low\" but \"across a 2024 survey of 500 enterprise IT teams, 67% reported [specific metric], costing an estimated $X per year in [specific consequence].\"\n\n**Do not mention your product.** Do not pose problems you cannot solve. Do not exaggerate — the reader will discount everything else if the problem feels inflated.\n\n### Background \u002F context (400-700 words, ~12%)\nProvide industry context, historical perspective, and an honest assessment of why prior approaches fell short. Demonstrate authoritative knowledge while keeping the narrative moving forward.\n\n### Solution overview (900-1,400 words, ~25% — the centerpiece)\nPresent your approach, framework, or methodology. Explain how it addresses the root causes identified in the problem section. Differentiate from prior approaches. Use case studies or analogies to illustrate.\n\n**Critical rule: do not name your specific product until the final paragraphs, if at all.** The reader should feel the solution is the logical, inevitable conclusion of the preceding analysis. If the solution section reads as a product pitch, the entire edifice collapses — the reader realizes they were manipulated, not educated.\n\n### Benefits and evidence (500-900 words, ~13%)\nQuantify ROI, efficiency gains, or risk reduction. Include case studies, third-party research validation, and expert citations. Use specific, verifiable data from named sources. Before-and-after comparisons are powerful. Avoid unsubstantiated claims and cherry-picked statistics.\n\n### Implementation considerations (300-600 words, ~9%)\nA realistic roadmap: steps, prerequisites, potential challenges, timeline, success indicators. Build confidence that the solution is achievable. **Do not make everything sound effortless** — readers distrust claims that understate complexity.\n\n### Conclusion and call to action (200-350 words, ~5%)\nSummarize the key argument. Restate urgency. Include a clear but subtle next step — schedule a consultation, download a tool, contact the team. Do not introduce new arguments. Do not pivot into a hard sell.\n\n### About the company (150-250 words)\nBrief overview of relevant expertise, credentials, notable clients, and contact information. Think credibility stamp, not brochure.\n\n### References\nCite all sources consistently. Hyperlink URLs for digital distribution.\n\n## Academic white paper structure (working paper \u002F technical report)\n\nApproximately 8,000 words \u002F 20 pages. Each section with recommended proportions:\n\n| Section | Length (words) | % of total |\n|---------|----------------|-----------|\n| Title page + abstract | 150-300 | 2% |\n| Table of contents | auto-generated | — |\n| Introduction | 800-1,200 | ~12% |\n| Literature review | 1,200-1,600 | ~18% |\n| Methodology | 800-1,200 | ~12% |\n| Analysis and discussion | 2,400-3,200 | ~35% |\n| Conclusions | 400-640 | ~6% |\n| Recommendations | 240-400 | ~4% |\n| References + appendices | as needed | — |\n\n**The abstract** (academic) vs. **executive summary** (corporate): abstracts are 150-300 words, self-contained, oriented toward scholarly readers; executive summaries are longer (1-2 pages), may include graphics, and target decision-makers who need actionable recommendations without reading the full document.\n\n**Literature review discipline**: organize thematically, not chronologically. Synthesize across sources to identify patterns, contradictions, and gaps. Conclude by showing how the literature identifies the gap your work fills. Avoid the annotated-bibliography-in-disguise format.\n\n## Evidence standards and citation\n\nCredibility hierarchy (highest to lowest):\n1. Primary research you conducted\n2. Peer-reviewed academic research\n3. Government and NGO data (NIST, Gartner, Forrester, IDC with sponsor disclosure)\n4. Industry analyst data (know that analysts are often funded by vendors being analyzed)\n5. Vendor-sponsored studies (must disclose; readers heavily discount)\n\n**Statistics need context**: \"40% improvement\" means nothing without a baseline, a sample size, a methodology, and a time frame. Always include: who collected the data, when, from how many respondents\u002Fsystems, using what methodology.\n\n**The 42% rule**: a 2021 survey found 42% of B2B buyers rated white papers as the most valuable content when researching a purchase, with 57% preferring them early in the buying process. The white paper is the most trusted format in the B2B buying journey — which is exactly why debasing the format with premature selling is so damaging.\n\n## Narrative arc: the story beneath the structure\n\nThe most memorable white papers have an underlying narrative arc:\n\n**Ordinary world**: the reader's current reality, the status quo. Establish this in concrete, specific terms — not abstract industry platitudes but the actual experience your reader is having.\n\n**Complication**: why the ordinary world is failing. The problem is getting worse, or the stakes just increased, or a new development makes the old approach obsolete. This is where urgency is established.\n\n**Resolution**: your approach, framework, or insight. This arrives only after the reader has fully understood the complication — the resolution is earned, not advertised.\n\n**Transformed world**: what the reader's world looks like after applying the approach. Specific, measurable, believable.\n\nThis arc maps to the classical white paper structure: Problem Definition = Ordinary World + Complication; Solution Overview = Resolution; Benefits = Transformed World.\n\n## The most common mistakes\n\n**The sales pitch in disguise** (48.1% of white papers reviewed in one survey were blatant product promotions): if the reader reaches the end feeling sold to rather than educated, the white paper has failed. The test: could you remove all company branding and still have a valuable document?\n\n**Vagueness without data**: every major claim needs a specific, sourced statistic or case study.\n\n**Excessive length**: the trend is toward shorter documents. A well-reasoned 6-page white paper beats a padded 15-page one.\n\n**Jargon overload**: define technical terms. Do not assume the reader has your acronym vocabulary.\n\n**Weak conclusions that restate the introduction**: conclusions should synthesize — draw together the threads into a landing that is more than the sum of the parts.\n\n**Poor alignment between problem and solution**: if the solution does not directly address the cause as characterized in the problem section, the argument collapses. Work backward: define the solution first, then characterize the cause in a way that makes your solution the logical response.\n\n## Formatting and length specifications\n\n**Length**: 2,500-7,000 words; 8-15 pages typical B2B corporate; government = variable; academic = 8,000-15,000 words.\n\n**Typography**:\n- Body: 11-12pt (Calibri, Garamond, or Georgia for digital; Times New Roman for print)\n- H1: 18-24pt\n- H2: 14-18pt\n- Captions: 8-10pt\n- Line spacing: 1.2-1.5× for published versions; double-space for review drafts\n- Optimal line length: 65-75 characters (45-90 maximum for readability)\n\n**Data visualization**: 65% of information is retained with visuals, compared to 10-20% with text alone. Use bar charts for comparisons, line graphs for trends, donut charts (preferred over pie) for part-to-whole. Apply brand colors consistently. Always label directly rather than using legends where possible.\n\n**Accessibility**: 4.5:1 minimum contrast ratio (WCAG 2.1 Level AA). Alt text for all meaningful images. Tagged PDFs for screen reader navigation.\n\n## Toolchain recommendations\n\n**Academic\u002Ftechnical**: LaTeX (Overleaf for collaboration) — precise typesetting, automated cross-referencing, BibLaTeX for citations. Essential packages: `geometry`, `hyperref`, `biblatex`, `booktabs`, `cleveref`.\n\n**Corporate**: Word + Styles system for consistent formatting and auto-generated TOC. Export to PDF. For highly designed versions, Adobe InDesign or Affinity Publisher.\n\n**Version-controlled technical writing**: Markdown + Pandoc + Git. Write in Markdown (one sentence per line for clean diffs), use YAML front matter for metadata, compile to PDF\u002FDOCX via Pandoc with `--citeproc` for citations.\n\n**Citation management**: Zotero (free, open-source, best browser capture) for most users; BibLaTeX\u002FBiber for LaTeX workflows; EndNote for large-scale systematic reviews with institutional licenses.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill white-paper-writing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill white-paper-writing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill white-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ASZST75DDT0C7CS1502JVS","shop-woodworking-tools-sharpening-joinery-and-finishing","Use for woodworking operations: layout and marking, hand tools and how to use them well, sharpening and why it is the skill everything else depends on, the shop machines, the table saw specifically including kickback and the guarding that prevents it, joinery technique, glue-ups and clamping strategy, and wood finishing from surface preparation through film and penetrating finishes.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fworking-with-wood-and-metal\u002Fskills\u002Fshop-woodworking-tools-sharpening-joinery-and-finishing\u002FSKILL.md",[],[]]