Whitepaper skill
The evidence-led method Okara’s Writer Agent uses to write a whitepaper that survives a skeptical technical reader: a real thesis, sourced claims, published methodology, and stated limitations.
Download the methodology, see how the agent structures an evidence-led document, or run it live inside the Writer Agent.
- Category
- Writer
- Agent
- Writer Agent
- Format
- whitepaper.md
- Price
- Free to download
The skill file
--- name: whitepaper description: Write an evidence-led whitepaper that stands up to a skeptical technical reader — a real thesis, sourced claims, honest limitations, and a methodology section that survives scrutiny. owner: Okara Writer Agent --- # Whitepaper A whitepaper is not a long brochure. It's an argument supported by evidence, written for a reader who will check your sources and forward the PDF to someone more skeptical than they are. This skill writes to that standard.
Log in to view, copy, and download the complete skill file.
About this skill
What is the Whitepaper?
The Whitepaper skill is the exact approach Okara’s Writer Agent follows to produce a document that holds up under scrutiny. It insists on a thesis rather than a topic, separates evidence from interpretation, publishes the methodology, and states the limitations explicitly — because naming your own boundary conditions is the strongest credibility signal the format has.
It’s written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Use it when a technical buyer has veto power, when you have original data worth publishing formally, or when a claim needs evidence rather than assertion.
Downloading the instructions is free with an Okara account. Running the skill — the full document drafted, sourced, and maintained as your data updates — is part of the Writer Agent.
Example
See it in action
You ask: “We benchmarked our ingestion pipeline against three alternatives. Turn it into a whitepaper.”
Agent does: It converts your topic into a thesis with a threshold in it — the specific event volume above which the tradeoff flips — and puts that finding on page one, because most readers never get past the executive summary. Evidence goes in its own section ahead of any interpretation, so a skeptical reader can evaluate your numbers without accepting your reading of them. The methodology section states hardware, versions, sample sizes, and what you excluded. Then it writes the limitations section naming the two workloads where your advantage disappears — which is what makes the rest believable — and confines the product pitch to one clearly marked section near the end.
How it works
From input to output
- 1
You bring the evidence
Share the data, benchmarks, or research plus the technical audience you need to convince.
- 2
Okara sharpens it to a thesis
The Writer Agent turns the topic into a specific, arguable claim the document can actually defend.
- 3
It separates evidence from argument
Data and methodology get their own sections, so a reader can check your work before accepting your reading of it.
- 4
You publish with limitations stated
The agent names where the finding does not hold, which is what makes the rest of it credible.
What's included
Everything it covers
Thesis extraction
Converts a topic into a specific, arguable claim with a testable boundary.
Executive summary
The finding, evidence class, and implication on one page — the only page many readers read.
Evidence before interpretation
Data and results presented so they can be evaluated independently of your argument.
Published methodology
How it was measured, what was excluded, and why — the section that separates research from marketing.
Stated limitations
Names where the finding fails, the strongest credibility signal the format has.
Checkable citations
Sources with dates, versions, and sample sizes, because one unsourced claim taints the rest.
Use cases
When to reach for it
- Win over a technical buyer who holds veto power in an enterprise deal.
- Publish original benchmark data in a format that survives scrutiny.
- Give procurement and security review a document they can evaluate.
- Support a bold claim with evidence rather than assertion.
- Replace a "whitepaper" that is really a twelve-page brochure.
Frequently Asked Questions
Related skills
Pair it with these skills
Blog Post
The blog-writing methodology Okara’s Writer Agent follows to turn a keyword into a focused, SEO-aware post that ranks and reads like a human wrote it.
--- name: blog-post description: Write a single, focused, SEO-aware blog post — one topic, one reader, one takeaway — that ranks in search and reads like a human wrote it. owner: Okara Writer Agent --- # Blog Post Write one publish-ready blog post built around a single topic and a single reader intent, structured to earn the search click and hold attention to the
Long-Form Content
The pillar-content methodology Okara’s Writer Agent uses to write comprehensive, authoritative guides that own a topic and earn links over time.
--- name: long-form-content description: Write a comprehensive, authoritative pillar guide (2,000-5,000+ words) that covers a topic end to end, anchors a content cluster, and earns links and rankings over time. owner: Okara Writer Agent --- # Long-Form Content Produce a definitive, in-depth guide that owns a broad topic — the page a reader bookmarks and other sites link to — not a quick post. Depth, structure,
Listicle
The list-article methodology Okara’s Writer Agent uses to write scannable, curated listicles where every item earns its place and the framing makes the choice easy.
--- name: listicle description: Write a scannable list article — "N X for Y" — with a curated set of items, parallel structure, and a framing that makes the reader's decision easier. owner: Okara Writer Agent --- # Listicle Write a list-format article that's genuinely useful, not padded. Every item earns its place, the structure is consistent, and the intro and wrap-up turn a