business-one-pager
Skill0 starsChanged 2 months agoMITView on GitHub
Draft a polished one-page overview of a company, product, service, project, program, practice, or team in clean markdown from whatever inputs the user provides — a few sentences or a full deck. For founders, sales and BD leads, agency and consulting principals, program managers, nonprofit directors, recruiters, and fund managers who need a top-of-funnel document for prospects, partners, recruits, donors, or investors. Trigger on phrases like "one-pager," "company overview," "product overview," "service overview," "program summary," "marketing doc," "capabilities summary," "write up our company," "draft our overview," "what do I send prospects," "leave-behind," or any request to produce a short document that describes an offering to an outside audience. Also trigger when the user uploads or pastes a pitch deck, proposal, questionnaire response, prior marketing document, website copy, or strategy description and asks to turn it into a one-pager. Input-agnostic. Do NOT use for a periodic update to existing stakeholders — use the stakeholder-update-generator skill. Do NOT use to check marketing claims for substantiation problems — use the marketing-claims-prescreen skill. Do NOT use for a LinkedIn post — use the linkedin-post-generator skill.
In this repository39 other files it gives its agents.
- audit-request-binderSkill
- call-notes-followupSkill
- company-first-passSkill
- conference-prep-plannerSkill
- contract-obligations-extractorSkill
- counterparty-diligenceSkill
- decision-memo-drafterSkill
- document-redline-diffSkill
- executive-briefingSkill
- expert-interview-synthesisSkill
- hundred-day-plan-drafterSkill
- inbox-triageSkill
- intro-email-generatorSkill
- linkedin-post-generatorSkill
- marketing-claims-prescreenSkill
- market-map-builderSkill
- meeting-minutes-generatorSkill
- nda-reviewSkill
- payout-reconciliation-checkerSkill
- performance-attribution-narratorSkill
- periodic-report-synthesizerSkill
- podcast-episode-analyzerSkill
- presentation-transcript-extractorSkill
- private-company-tear-sheetSkill
- professional-profile-briefSkill
- project-folder-organizerSkill
- proposal-first-passSkill
- questionnaire-red-flag-scannerSkill
- questionnaire-response-drafterSkill
- red-team-premortemSkill
- relationship-status-summarizerSkill
- side-letter-term-extractorSkill
- skill-idea-generatorSkill
- stakeholder-update-generatorSkill
- teach-meSkill
- unit-economics-memoSkill
- watchlist-news-alertSkill
- weekly-recap-writerSkill
- workflow-to-ai-solverSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
If the user provides only minimal inputs, produce a clean template with [INSERT ...] placeholders and append a list of what would …
- Distinctive: line 67
Only use what the user provides: Do not invent results, fabricate credentials, name customers the user has not named, or add claims the …
- Distinctive: line 69
Extract and reorganize, don't generate: When the user uploads source materials, the job is to pull out what matters and restructure it into …
- Distinctive: line 155
Read the uploaded content carefully.
- Very specific: line 158
Use the description as-is for the sections it covers.
- Distinctive: line 165
Default to: precise, professional, understated.
- Distinctive: line 172
If the user provides prior marketing materials, match that voice and register.
- Distinctive: line 184
Always list the Why Us section first if it's missing or thin — that is the section readers most scrutinize.
- Distinctive: line 188
Before delivering the draft, verify:
- Distinctive: line 190
No invented facts, credentials, customers, or results figures
- Very specific: line 191
All missing data marked with [INSERT ...] placeholders
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Business One-Pager
Draft a polished one-page overview from whatever the user provides — a few sentences, pasted bullet points, or uploaded materials.
Why This Skill Exists
Most small companies, agencies, practices, programs, and internal teams don't have a dedicated marketing writer or a designer on call. Getting a clean, professional overview in front of a prospect, partner, recruit, or investor often means starting from scratch or reformatting an unwieldy deck. This skill turns raw information into a structured, well-written overview that's ready to share or hand off to a designer.
The output is polished markdown — structured cleanly enough to drop into a template, email, or document without heavy editing, but not a finished designed file. That keeps the skill flexible regardless of what tools the user has available.
What This Skill Does Not Do
- It does not invent strategy, results, team backgrounds, customers, or differentiators. Everything in the output comes from what the user provides.
- It does not calculate or derive metrics. If numbers are provided, they are presented as given.
- It does not make compliance or legal determinations. Marketing materials may be subject to review requirements — that is the user's responsibility.
- It does not produce a designed PDF or formatted document. The output is markdown intended as a draft for further editing or design work.
Inputs
The skill works on a spectrum. More context produces a tighter, more specific draft. Less context produces a clean placeholder-filled template. Either is useful.
Rich inputs (if available):
- Uploaded pitch deck, proposal, RFP response, or prior marketing document
- Customer or stakeholder updates, case studies, testimonials with permission
- Description of the offering in any form
- Team bios or professional profiles
- Results, traction, or select metrics (revenue, customers, outcomes, retention, throughput, impact numbers)
- Target audience profile (enterprise buyers, small businesses, patients, grant funders, institutional investors, candidates, etc.)
- Commercial terms (pricing model, engagement model, minimums, contract length, fund terms)
- Geographic, sector, or segment focus
Minimal inputs (enough to start):
- Name and category (e.g., "B2B payroll software," "outpatient physical therapy clinic," "brand design studio," "workforce re-entry program," "early-stage venture fund")
- A sentence or two on what makes it different
- Founder, principal, or team background in any form
If the user provides only minimal inputs, produce a clean template with [INSERT ...] placeholders and append a list of what would strengthen the draft. Do not refuse to proceed because inputs are limited.
Core Principles
Only use what the user provides. Do not invent results, fabricate credentials, name customers the user has not named, or add claims the user has not made. A marketing document with invented content is worse than a sparse one.
Extract and reorganize, don't generate. When the user uploads source materials, the job is to pull out what matters and restructure it into the one-pager format — not to rewrite the organization's strategy from scratch.
Be specific where possible, honest about gaps otherwise. Vague language like "experienced team with a strong track record" is weaker than actual specifics. If specifics aren't provided, use placeholders that prompt the user to fill them in.
Write for a sophisticated audience. Prospects, procurement teams, partners, grant committees, senior candidates, and investors are professionals who read many of these. The tone should be confident and direct without being promotional or overselling.
Shorter is better. A genuine one-pager is 400–600 words. Resist the urge to fill space. Readers skim; every sentence should earn its place.
Output Format
Produce the one-pager in the structure below. Omit sections where no information is available and there is no meaningful placeholder to offer. Tailor the headers and emphasis to the offering and the audience — a software product, a consulting practice, a community program, and an investment fund have different priorities, and a recruiting one-pager leads with mission and team where a sales one-pager leads with the problem solved.
One-Pager Structure
# [Name]
**[Category] | [Stage / Founded / Size if known] | [Headline metric if known]**
---
## What We Do
[2–4 sentences describing the offering, who it serves, and what outcome it
delivers. Be specific about segment, geography, and delivery model if
provided. If not provided, use placeholders.]
---
## Why Us
[What makes this organization or offering differentiated. This is the most
important section — if the user has a clear view on their edge, it goes
here. If not, use a placeholder and note that this needs to be the sharpest
section of the document.]
---
## Team
[Key people: name, title, and the most relevant prior experience or
credential. Keep to 1–2 sentences per person. Only include what the user
provides — do not look up or infer backgrounds.]
---
## Results
[If results, traction, outcomes, or performance data are provided, present
them here exactly as given — customer counts, retention, throughput, impact
measures, case study outcomes, track record. If nothing is available yet
(e.g., pre-launch, first program cycle, first fund), omit this section or
acknowledge it briefly and pivot to relevant prior experience instead. Do
not estimate or derive figures.]
---
## How We Work
[How the offering is delivered, sourced, evaluated, or managed. For a
product: onboarding, integration, support model. For a service: engagement
model, process, deliverables. For a program: intake, curriculum, follow-up.
For a fund: sourcing, evaluation, portfolio construction. Only include what
the user provides.]
---
## Commercials
[Pricing model, engagement terms, minimums, contract length, fees, or fund
terms as the user provides them. Use placeholders for anything missing.]
---
## Who It's For
[The audience this is right for — e.g., mid-market finance teams, hospital
systems, first-time managers, community foundations, institutional
investors. If the user hasn't specified, omit or use a light placeholder.]
---
[Contact / Organization Name]
[Website if provided]
[Contact information if provided]Adapting to Input Level
When source materials are uploaded
Read the uploaded content carefully. Extract the core offering, team, differentiation, and any results data. Restructure into the one-pager format — do not simply summarize the source document, actively reorganize it into this tighter structure. Flag any sections that are weak or missing in the original.
When only a description is provided
Use the description as-is for the sections it covers. Fill gaps with clearly marked [INSERT ...] placeholders. Append a completion checklist.
When input is minimal (a sentence or two)
Produce a clean template with the name and category populated where known, [INSERT ...] placeholders everywhere else, and a prioritized list of what to fill in first. The Why Us section is always the highest priority — note that explicitly.
Tone
Default to: precise, professional, understated. Overviews that oversell raise flags with experienced readers — procurement teams, grant reviewers, senior candidates, and investors alike. Avoid:
- Superlatives without evidence ("exceptional results," "best-in-class process," "industry-leading")
- Vague differentiation claims ("we have a unique approach")
- Buzzwords that don't mean anything ("value-add," "proprietary" without explanation, "synergies")
- Excessive length — if a section can be one sentence, it should be one sentence
If the user provides prior marketing materials, match that voice and register.
When Context Is Limited
Append the following at the end of any draft where meaningful inputs are missing:
---
**To sharpen this one-pager, consider adding:**
- [Prioritized list of missing inputs, starting with the most impactful]Always list the Why Us section first if it's missing or thin — that is the section readers most scrutinize.
Quality Checks
Before delivering the draft, verify:
- No invented facts, credentials, customers, or results figures
- All missing data marked with
[INSERT ...]placeholders - Length is 400–600 words (excluding placeholders and the completion checklist)
- The Why Us section is specific — if it reads as generic, flag it explicitly
- Tone is consistent: professional, direct, not promotional
- Headers and emphasis fit the offering and the audience, not a generic template
- The document reads like something a principal would hand to a serious buyer, partner, funder, or candidate
Important Reminder
This is a draft. Marketing materials are subject to common advertising-substantiation and consumer-protection principles, and in regulated industries — financial services, healthcare, legal, education, alcohol, and others — to specific rules on claims, testimonials, and disclosures. The user is responsible for compliance and legal review before distributing to an outside audience. Run marketing-claims-prescreen on the draft when the audience is external and the claims are load-bearing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

