Teach agents to author
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.
This skill produces media kits as
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
.
-
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).
-
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.
-
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.
-
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.
-
Honesty & permissions — No invented revenue, customers, logos, awards, or quotes. Missing inputs →
,
, or
. Logo/customer blocks only when user confirmed; else category-only or omit.
-
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.
-
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.
Follow the
k2f skill to build the
package from the blueprint, verify, and export (typically PDF).