Capability Collateral
The PRODUCE stage of the marketing operating system (see ../INDEX.md).
Turns the campaign message + proof into sendable, branded assets.
Use when
The user asks for a "one-pager", "capability statement", "pamphlet/brochure", "leave-behind",
"work-sample sheet", or a "PDF for management/clients", or to refresh existing collateral.
Goal
A single-page (or tight multi-page), on-brand asset that says who/what/why-us with
concrete proof, tailored to its audience, and rendered to a clean PDF — reusing pre-cleared
claims rather than re-writing them.
Inputs to gather
- Brief: audience/segment, use-context (cold intro vs live pursuit), the win-theme.
- Proof: past performance, metrics, credentials, testimonials, work samples — pulled
from
../_shared/claims-library.md where possible.
- Brand assets: logo, palette, contact block, voice.
- Output format: web page, print PDF, or both.
Method
- Write the brief (one paragraph): who it's for, where it's used, the single win-theme.
- Draft the spine: headline → who we are (credibility line) → what we do (scoped) →
why us (differentiators + proof) → one clear CTA.
- Pull proof from the claims library; if a claim isn't cleared, flag it — don't invent
numbers or imply work/relationships that don't exist.
- Tailor to the segment (operators vs EPCs vs legal/insurance vs renewables) — a general
version plus a targeted variant for live pursuits.
- Lay out in the house style: keep page 1 short/scannable; detail on following pages;
use cards, a hooks/funnel diagram, or a comparison table where it earns its space.
- Brand + voice + accuracy check.
- Render to PDF via headless Chrome — see
references/html-to-pdf.md.
- Version + store in the collateral library; provide a clickable link to the PDF.
Output
HTML source + rendered PDF (and any QR/links). Store both in the engagement's collateral
folder; keep the HTML so it can be re-rendered and versioned.
Definition of done
Guardrails / pitfalls
- No invented or uncleared claims — opposing counsel and procurement both check.
Especially for the expert-witness lane, keep CV/profile/collateral identical + verifiable.
- PII / public hygiene — sanitize before any public or external surface; real client
detail stays in the private engagement repo.
- Don't bury the ask — one CTA, prominent.
- Reuse, don't re-write — feed and pull from the claims library.
Related skills
Fed by marketing-campaign-plan (message/proof) and
content-calendar (asset list). Used by
targeted-outreach-sequence as the attachment.
1---2name: capability-collateral3description: Produce and refresh branded, single-page capability one-pagers, pamphlets, and management decks/plans — brief → who/what/why-us + concrete proof → segment tailoring → brand/voice + claims check → clean layout → render HTML to PDF. Reuses an approved-claims library so claims are written once and reused (incl. proposal/expert-witness support).4---56# Capability Collateral78The **PRODUCE** stage of the marketing operating system (see [`../INDEX.md`](../INDEX.md)).9Turns the campaign message + proof into sendable, branded assets.1011## Use when12The user asks for a "one-pager", "capability statement", "pamphlet/brochure", "leave-behind",13"work-sample sheet", or a "PDF for management/clients", or to refresh existing collateral.1415## Goal16A **single-page (or tight multi-page), on-brand asset** that says who/what/why-us with17concrete proof, tailored to its audience, and rendered to a clean PDF — reusing pre-cleared18claims rather than re-writing them.1920## Inputs to gather211. **Brief**: audience/segment, use-context (cold intro vs live pursuit), the win-theme.222. **Proof**: past performance, metrics, credentials, testimonials, work samples — pulled23 from [`../_shared/claims-library.md`](../_shared/claims-library.md) where possible.243. Brand assets: logo, palette, contact block, voice.254. Output format: web page, print PDF, or both.2627## Method281. **Write the brief** (one paragraph): who it's for, where it's used, the single win-theme.292. **Draft the spine**: headline → who we are (credibility line) → what we do (scoped) →30 why us (differentiators + proof) → one clear CTA.313. **Pull proof from the claims library**; if a claim isn't cleared, flag it — don't invent32 numbers or imply work/relationships that don't exist.334. **Tailor to the segment** (operators vs EPCs vs legal/insurance vs renewables) — a general34 version plus a targeted variant for live pursuits.355. **Lay out** in the house style: keep page 1 short/scannable; detail on following pages;36 use cards, a hooks/funnel diagram, or a comparison table where it earns its space.376. **Brand + voice + accuracy check.**387. **Render to PDF** via headless Chrome — see39 [`references/html-to-pdf.md`](references/html-to-pdf.md).408. **Version + store** in the collateral library; provide a clickable link to the PDF.4142## Output43HTML source + rendered PDF (and any QR/links). Store both in the engagement's collateral44folder; keep the HTML so it can be re-rendered and versioned.4546## Definition of done47- [ ] Single clear audience + win-theme.48- [ ] Who/what/why-us + ≥1 concrete, cleared proof point.49- [ ] Segment-tailored (general + targeted variant where there's a live pursuit).50- [ ] On-brand; voice + accuracy checked.51- [ ] Clean PDF rendered; page 1 scannable.52- [ ] Versioned in the library; claims sourced from the claims library.5354## Guardrails / pitfalls55- **No invented or uncleared claims** — opposing counsel and procurement both check.56 Especially for the expert-witness lane, keep CV/profile/collateral identical + verifiable.57- **PII / public hygiene** — sanitize before any public or external surface; real client58 detail stays in the private engagement repo.59- **Don't bury the ask** — one CTA, prominent.60- **Reuse, don't re-write** — feed and pull from the claims library.6162## Related skills63Fed by [`marketing-campaign-plan`](../marketing-campaign-plan/SKILL.md) (message/proof) and64[`content-calendar`](../content-calendar/SKILL.md) (asset list). Used by65[`targeted-outreach-sequence`](../targeted-outreach-sequence/SKILL.md) as the attachment.