k2f-media-kit
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.
- Installs
- 2.2K
- Last 24h
- +107
- Trending rank
- #1914
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/suzheng/k2f --skill k2f-media-kit- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads k2f-media-kit automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
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 →
TBD,Not provided, orNEEDS USER INPUT. 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.
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).
FAQ
What does the k2f-media-kit skill do?
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.
How do I install k2f-media-kit?
Run npx skills add https://github.com/suzheng/k2f --skill k2f-media-kit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/k2f-media-kit/ (personal) or .claude/skills/k2f-media-kit/ (project).
Which AI agents can use k2f-media-kit?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is k2f-media-kit safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains k2f-media-kit?
It is published by suzheng in suzheng/k2f. It has 2,179 recorded installs.
More from suzheng/k2f
k2f-worksheet
suzheng/k2f
Design printable, fill-in-ready worksheets—practice sets, graphic organizers, lab records, reflections, or gap-closure forms—from learning goals and source material. Use when the user asks for a worksheet, handout with answer spaces, practice problems, graphic organizer, or structured questions students complete in class or at home. Create worksheets 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-quotation
suzheng/k2f
Create client-ready sales quotations from scope notes, line items, rates, and terms—structured so buyers can compare options, accept, or convert to an invoice without rework. Use when the user asks for a quotation, quote, estimate, proposal pricing, or RFQ response. Create quotations 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-idml
suzheng/k2f
Blueprint multi-page print publications—brochures, magazines, catalogs, annual reports, lookbooks—for designer handoff with spread-aware story flow, typed editorial blocks, and art direction before layout. Use when the user asks for InDesign, IDML, editorial layout, print collateral, or an editable package for a production designer. Create idmls 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-sales-deck
suzheng/k2f
Turn discovery notes, proposals, and product proof into buyer-ready sales decks with a prospect-centered story, one objective per meeting, and evidence-backed slides. Use when the user asks for a sales deck, demo presentation, proposal deck, executive briefing, or sales slides (not a fundraising pitch deck or generic company overview). Create sales decks 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-invitation
suzheng/k2f
Turn event facts and tone notes into print or digital invitations with ceremonial copy, layered logistics, and suite-consistent visual intent—not posters, programs, or slide decks. Use when the user asks for a wedding invitation, party invite, gala card, save-the-date, RSVP insert, or mobile e-invite. Create invitations 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-flyer
suzheng/k2f
Turn event details, offers, or brand notes into a single-page flyer with a scannable headline, one primary call to action, and mood-matched visual intent—not a brochure, slide deck, or poster wall. Use when the user asks for a flyer, leaflet, handout, promo sheet, open-house sheet, or print/digital one-pager for events, sales, restaurants, fitness, real estate, hiring, or community campaigns. Create flyers 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.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.