k2f-company-deck
Turn company facts, brand inputs, and stakeholder goals into a polished company overview deck with clear positioning, proof, and contact-ready closure. Use when the user asks for a company deck, corporate overview, company profile presentation, or brand deck (not a fundraising pitch or sales proposal). Create company 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.
- Installs
- 2.4K
- Last 24h
- +110
- Trending rank
- #1877
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/suzheng/k2f --skill k2f-company-deck- 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-company-deck 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 Company Deck — AI-Native Aesthetic Design
Purpose
Teach agents to blueprint company decks before layout: a stakeholder-ready story that explains who the company is, what it delivers, and why it matters—without inventing funding, customers, metrics, or leadership the user did not supply.
Built on K2F
This skill produces company decks 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 (slide roles, narrative, 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
- Introducing the company to partners, enterprise buyers, recruits, press, or board guests (no investment ask).
- Consolidating website copy and bios into one coherent overview.
- Refreshing a generic “about us” deck for skimmable positioning and contact in under ten minutes.
Workflow
Step 1. Generate the content_and_design.md
Single blueprint for semantic content and aesthetic intent. Use labeled blocks per slide (role, headline, body, visual type) that the k2f skill can map later.
Sub-steps
-
Deck frame — Primary audience (partner, customer, talent, media), setting (first meeting, conference, onboarding), and time budget. Choose emphasis: credibility + capabilities for B2B; mission + culture for talent; news + proof for press. Drop fundraising slides unless the user explicitly wants a hybrid.
-
Input audit — Inventory verified inputs: positioning, products, public pricing, permitted logos, milestones, team, partnerships, news. Flag
NEEDS USER INPUTfor gaps—never fabricate headcount, revenue, clients, or awards. -
Narrative spine — Plan flow before titles: identity → problem space → offer → how it works → proof → difference → people & scale → direction (vision, not roadmap dump) → engage. Opening = name + tagline; closing = one CTA.
-
Slide architecture (include / cut) — Default overview stack (~12–16 slides); merge or omit when inputs are thin:
- Title → Company snapshot → Mission / values (optional) → Problem & opportunity (light) → Solutions / product lines → How we work or platform → Customers & outcomes → Differentiation → Team → Milestones / footprint → Partners or ecosystem (optional) → Vision → Contact.
- Cut investor-only blocks (TAM essay, use-of-funds, cap table), duplicate product slides, long feature lists, and internal org charts unless audience is recruits.
- Split when identity and product story share one slide, or when two products each need a hero proof point.
-
Per-slide content contract — For each slide specify:
- Headline: outcome or position, not a section label (“Payments infrastructure for internet businesses” not “About us”).
- Body: max 3–5 bullets or one visual; ~2 lines per bullet; parallel grammar on lists.
- Visual type: logo strip, product frame, workflow diagram, metric callouts, timeline, team grid, map—prefer visual intent over paragraphs for comparisons, milestones, and portfolios.
- Footnotes: source + year for external claims; logo approval notes if needed.
-
Proof layering — Permitted logos or named references first; anonymize if required. Scale metrics only when user-supplied; else qualitative proof with TBD.
-
Design intent — For the engine: tone institutional, from user brand voice—not generic hype; hierarchy one hero per slide, calm contact block; density one message per slide, grids for portfolios; palette user colors or neutral + one accent, WCAG AA, consistent logos/timelines.
Rules & constraints
- Audience gate: every slide must earn its place for the chosen audience; recruit slides ≠ partner slides unless user wants one master deck.
- Truth gate: metrics, customers, funding, and headcount match user materials or are marked TBD—no rounded-up fiction.
- One-idea gate: if the headline needs “and,” split or cut.
- Brand gate: tagline, product names, and legal entity spelling identical everywhere.
- Logo gate: only logos the user confirmed; otherwise “category examples” or omit.
Common failure modes
- Pitch deck as company deck → drop ask, financials, TAM; strengthen identity and contact.
- Website walls of text → headline + proof only; detail in blueprint notes.
- Feature lists without outcomes → tie capabilities to customer results.
- Weak differentiation → two-column comparison or cut.
- Long team bios → name, role, one line each.
- Cluttered closing → one CTA plus minimal contact.
Quality checklist
- Tagline and company snapshot appear in the first three slides; contact/CTA on the last slide.
- Every slide has one headline claim and a declared visual type.
- No slide exceeds density limits; external stats have sources or TBD flags.
- Product and company names spelled consistently; repeated metrics match.
- Audience-irrelevant sections removed or moved to optional appendix notes in the blueprint.
- Design intent names tone, hero emphasis, and accent usage for the full deck.
Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.
Follow k2f skill to instantiate slides from the blueprint, apply roles from design intent, verify, and export the stakeholder-ready deliverable.
FAQ
What does the k2f-company-deck skill do?
Turn company facts, brand inputs, and stakeholder goals into a polished company overview deck with clear positioning, proof, and contact-ready closure. Use when the user asks for a company deck, corporate overview, company profile presentation, or brand deck (not a fundraising pitch or sales proposal). Create company 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.
How do I install k2f-company-deck?
Run npx skills add https://github.com/suzheng/k2f --skill k2f-company-deck 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-company-deck/ (personal) or .claude/skills/k2f-company-deck/ (project).
Which AI agents can use k2f-company-deck?
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-company-deck 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-company-deck?
It is published by suzheng in suzheng/k2f. It has 2,400 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.