k2f-media-kit — Claude Code skill: build a press kit
Turns verified company, product and leadership facts into a journalist-ready media kit with boilerplate and an asset manifest. Built on the K2F format.
npx skills add suzheng/k2f --skill k2f-media-kit -a claude-codeWhat k2f-media-kit does
The skill walks the agent through a fixed sequence. First you lock the audience, the kit's job, the channel and what may legally be named. Then you pick one archetype — ongoing company press, product launch, executive profile or creator pack — and stick to it instead of merging incompatible kits.
Content is split into layers: glance facts, grab-and-quote copy, reference tables and the operational block with the media contact. Honesty rules are explicit. Invented revenue, customers, logos, awards or quotes are out; missing inputs become TBD or NEEDS USER INPUT. Boilerplate comes in two lengths with identical facts, bios run roughly 80–120 words, and the asset manifest lists type, description and availability rather than fake download links.
The blueprint lands in content_and_design.md, which the k2f skill packs into a .K2F package and exports, usually as PDF. Install that core skill first with npx skills add suzheng/k2f --skill k2f — without it the pack and verify steps have nothing to run. This is for press and partner materials, not investor decks or internal one-pagers.
What it helps with
- produce a press kit with paste-ready copy
- tier company facts so a reporter can scan them
- describe assets so journalists know what to request
- keep short and long boilerplate factually identical
- separate a launch news angle from evergreen company copy
Example prompts for the agent
- Build a media kit for our product launch: facts, boilerplate, bios, asset list
- Draft a company press kit using the ongoing press archetype and export it to PDF
- Create a creator pack with talking points, disclosure rules and contact details
How to install k2f-media-kit
1Skills CLI (Vercel)
npx skills add suzheng/k2f --skill k2f-media-kit -a claude-code2Manually: put the files in place
~/.claude/skills/k2f-media-kit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/k2f-media-kit/
1Skills CLI (Vercel)
npx skills add suzheng/k2f --skill k2f-media-kit -a codex2Manually: put the files in place
.agents/skills/k2f-media-kit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add suzheng/k2f --skill k2f-media-kit -a cursor2Manually: put the files in place
.cursor/skills/k2f-media-kit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install suzheng/k2f k2f-media-kit2Manually: put the files in place
.github/skills/k2f-media-kit/SKILL.md1Skills CLI (Vercel)
npx skills add suzheng/k2f --skill k2f-media-kit -a gemini-cli2Platform CLI
gemini skills install https://github.com/suzheng/k2f --path skills/marketing/k2f-media-kitManually: put the files in place
.devin/skills/k2f-media-kit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add suzheng/k2f --skill k2f-media-kit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about k2f-media-kit
How do I install k2f-media-kit in Claude?
Run npx skills add suzheng/k2f --skill k2f-media-kit -a claude-code. The skill lands in ~/.claude/skills/k2f-media-kit/SKILL.md.
What does k2f-media-kit do?
It guides the agent in writing content_and_design.md for a media kit: information layers, boilerplate, bios, asset manifest and design intent. The k2f skill then packs and exports the .K2F file.
What do I need before using it?
The core k2f skill, which handles packaging and verification. Install it with npx skills add suzheng/k2f --skill k2f.
Source text
SKILL.md · Apache-2.0
--- name: k2f-media-kit description: Turn verified company, product, and leadership inputs into a journalist-ready media kit with scannable facts, boilerplate, and asset guidance—not a pitch deck or sales one-pager. Use when the user asks for a media kit, press kit, PR kit, or creator resource pack. Create media kits with AI-native design and the highest aesthetic standards, powered by the K2F format and engine. Purpose-built for AI agents, K2F lets them focus on semantic content and design intent while automatically handling layout, typography, and formatting complexity. --- # K2F Media Kit — AI-Native Aesthetic Design ## Purpose Teach agents to author `content_and_design.md` for **press- and partner-facing media kits**: what belongs in the kit, how to tier information for grab-and-quote use, and aesthetic intent (tone, hierarchy, density)—not K2F packaging or export. ## Built on K2F This skill produces media kits as `.K2F` packages. Follow the **k2f** skill for authoring: unpack or init a workspace, edit the semantic tree, pack/verify, and export. K2F keeps agents on *meaning* (sections, boilerplate, fact blocks, visual intent)—not coordinates—while the engine compiles layout, typography, and theme into export-ready output. Before you build, install the core skill: `npx skills add suzheng/k2f --skill k2f`. ## When to Use - Launch or refresh materials for **press, podcast hosts, analysts, or creators** who need facts and approved copy fast. - Packaging boilerplate, leadership bios, product snapshots, milestones, and **asset inventory** in one coherent kit. - **Modular reference** journalists can excerpt—not fundraising decks (**k2f-pitch-deck**), event promos (**k2f-flyer**), or single-page internal briefs (**k2f-one-pager**). **Not for:** investor narratives or exhaustive brand bibles unless the user wants a hybrid (usage intent only). ## Workflow ### Step 1. Generate the content_and_design.md Blueprint **semantic content** and **design intent** in labeled blocks reporters can scan and excerpt independently. **Sub-steps** 1. **Kit lock** — Primary user (beat reporter, creator, partner comms), **kit job** (launch coverage, ongoing press room, product drop, executive profile), channel (downloadable PDF, emailed ZIP companion, on-site sections), and legal posture (what may be named vs anonymized). 2. **Kit archetype & section order** — Pick one skeleton; do not merge incompatible kits: - **Company / ongoing press**: cover identity → quick facts → short + long boilerplate → key messages (3–5) → products/services snapshot → milestones → leadership (short bios) → customers/partners (permitted only) → news highlights → awards → asset manifest → media contact. - **Product launch**: product hook → problem context (factual) → what’s new → availability/pricing (public only) → specs at outcome level → launch quotes (user-supplied) → boilerplate → assets → contact. - **Founder / executive**: headline role → bio (neutral third person) → expertise themes → select quotes → company tie-in → headshot intent → contact via comms. - **Creator pack**: brand one-liner → do/don’t talking points → deliverable expectations → disclosure rules → links/handles → asset list → contact. 3. **Information layers** — **Glance**: name, descriptor, founded, HQ, URL, category. **Grab-and-quote**: 50- and 150-word boilerplate, key messages, approved quotes. **Reference**: fact table, timelines, bios, product cards. **Operational**: asset manifest, usage notes, media email—never buried under marketing prose. 4. **Content tiers** — **Approved copy** (paste-ready), **Verified facts** (sourced or TBD), **Pointer** (link to press page, DAM, or “request via…”). Park website essays, roadmap fiction, and internal metrics in **omit** or appendix pointer—not inline. 5. **Honesty & permissions** — No invented revenue, customers, logos, awards, or quotes. Missing inputs → `TBD`, `Not provided`, or `NEEDS USER INPUT`. Logo/customer blocks only when user confirmed; else category-only or omit. 6. **Cut pass** — Remove pitch-deck slides as paragraphs, duplicate bios, feature catalogs, and multiple CTAs. One **primary media contact**; secondary routes in a single line. Replace adjectives with one verifiable fact per message. 7. **Design intent** (no coordinates): - **Tone**: editorial-neutral, third-person ready; confident only where proof exists—state one voice pair (e.g., “factual, approachable”). - **Hierarchy**: kit title and descriptor dominate; boilerplate and fact tables as distinct bands; bios and news as repeatable modules. - **Density**: facts in tables or labeled rows; bios ~80–120 words; key messages as parallel bullets; avoid walls of prose. - **Rhythm**: alternate **copy blocks** with **fact strips** and **visual intent** (hero product frame, headshot grid, logo row)—modules should feel extractable. - **Contrast**: calm ground; accent on labels and pull quotes; legible roles for boilerplate. **Rules & constraints** - Every section must be **excerpt-friendly**—no “see above” dependencies across modules. - Boilerplate: two lengths (short/long) with identical facts; spelling of legal name and product names locked. - Quotes: attributed, dated if possible, user-supplied only. - Asset manifest: list type, description, and availability (attached / URL / on request)—no fake download links. - Launch kits: separate **news angle** (what changed) from evergreen company boilerplate. **Common failure modes** | Failure | Fix | |--------|-----| | Pitch deck pasted in | Map to archetype; move ask/financials out; keep facts + boilerplate. | | Marketing fluff, no paste-ready copy | Add short/long boilerplate and key messages first. | | Missing fact layer | Quick-facts table before narrative. | | Fabricated logos/quotes/stats | Stub, anonymize, or NEEDS USER INPUT. | | One giant bio essay | Short bio + optional extended in subordinate block. | | Asset section vague | Manifest rows: asset, format, use, source. | | Sales CTA overload | Single media contact + optional press page URL. | **Quality checklist** - [ ] Lock: audience, kit job, archetype, channel, permissions. - [ ] Section order matches archetype; modules stand alone. - [ ] Glance / grab-and-quote / reference / operational layers present. - [ ] Short + long boilerplate consistent; key messages parallel. - [ ] Facts traceable or TBD; quotes and logos permitted only. - [ ] Asset manifest complete or explicitly incomplete. - [ ] Design intent: tone, hierarchy, density, rhythm, contrast. - [ ] One primary media contact; no placeholder URLs. ### Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format. Follow the **k2f** skill to build the `.K2F` package from the blueprint, verify, and export (typically PDF).
© suzheng · Apache-2.0 · suzheng/k2f