# Tiger Whitepaper

> Generate a branded Tiger Claw white paper as a print-ready PDF, anywhere on the technical-to-marketing scale — a science paper, a technology paper (with some marketing), or a marketing paper (with some technology). Every paper carries the same signature: a dark branded cover, a numbered + signable confidentiality receipt, the brand palette/fonts, bigger type, no emojis, and honest live/built/pending labeling. Use when Brent says "white paper", "make a white paper", "team white-label pitch", "science/technical white paper", references white-paper No. NNN, or asks to turn a pitch into a branded PDF for a leader/partner.

- Skill: `bbrysonelite-max/tiger-whitepaper` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add bbrysonelite-max/tiger-whitepaper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bbrysonelite-max/tiger-whitepaper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: bbrysonelite-max (https://skillmd.com/u/bbrysonelite-max)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bbrysonelite-max/tiger-whitepaper

---


# Tiger Claw White Paper

Builds a branded white paper at one of three points on a scale. The cover and the
numbered confidentiality receipt are the fixed **signature** (generated by the build
script, identical every time). You author the body to fit the chosen variation.

## The scale — pick one

| `variation` | Reader | The question it answers | Lead with |
|---|---|---|---|
| `science` | Researcher / skeptic | "Is this rigorous and true?" | Problem, method, evidence, data, references. Marketing is a quiet frame only. |
| `technology` | Technical buyer / leader evaluating | "How does it work and will it hold up — and why care?" | Architecture, data, security, isolation, maturity. Open + close on benefit. |
| `marketing` | Buyer | "What's in it for me?" (every few seconds) | Benefit, their pain, the outcome, proof, one CTA. Just enough tech to be credible. |

All three get the confidentiality receipt + control numbering. See [REFERENCE.md](REFERENCE.md)
for the full doctrine of each variation, the brand system, and the body CSS classes.

## Workflow

1. **Gather inputs** (ask only what you can't infer): recipient, variation, the
   single next step (CTA), and any facts to feature. Keep pricing out unless Brent says otherwise.
2. **Assign the control number.** Read [LEDGER.md](LEDGER.md), take the next number,
   and append an entry (number, recipient, date, variation). Numbering is internal —
   the recipient never learns the others exist.
3. **Ground-truth every claim** against the source white papers / live state. Label
   capabilities **live / built-but-dark / pending** honestly — never oversell. No emojis.
4. **Write the body** as an HTML fragment of `<section class="sheet dark">` pages using
   the documented classes (see REFERENCE.md and `assets/body.example.html`). ~2 sections
   per page. Match tone + structure to the variation.
5. **Write the spec JSON** (see `assets/spec.example.json`) — cover meta, receipt clause,
   `bodyHtmlPath`, `outPath`.
6. **Build:** `node scripts/build-whitepaper.mjs <spec.json>`
7. **VERIFY by reading the PDF pages as images** — do not claim it rendered, look.
   Watch for an overflow/blank page (a sheet exceeding 11in). If a sheet overflows,
   move a section to a new sheet or trim spacing, then re-render. Confirm the receipt
   sits on exactly one page.
8. **Deliver** the PDF (copy to `~/Desktop/` if Brent wants to open it) and report
   page count + what's in it.

## Quick start

```bash
node scripts/build-whitepaper.mjs assets/spec.example.json   # renders the worked example
```

The worked example (`assets/body.example.html` + `spec.example.json`) is the Example Recipient
marketing paper, No. 004 — copy its patterns.

## Codex Runtime

Never expose or print secret, credential, or token values.

Mandatory dependencies:
- `Node.js`
- `Google Chrome`

Preflight each dependency using MCP/app capability discovery, CLI availability/version checks, read-only filesystem or Git checks for repositories, and provider auth-status commands without printing secrets, credentials, or tokens.
If any mandatory dependency is unavailable, stop and report a concise blocked state naming the missing dependency and the next action needed.