Steal This Skill: Twenty Business Documents From One Chat

FREE SKILL

Steal This Skill: Twenty Business Documents From One Chat

Name a document, paste the raw material, and Claude hands back the finished page. A big bold title, four numbers in tiles, the charts drawn for real. A short paragraph under every heading that says what the chart means, and the decision at the end. One HTML file. Open it in a browser, print it to PDF, send it.

Twenty documents. One skill. Nothing to install.

The pack is at the bottom of this page. Everything it knows is also on this page, so you can build the first one before you download anything.

The Problem: The Numbers Exist, the Document Does Not

You have the export. Meta Ads, Stripe, the bank feed, the CRM, two weeks of calendars. You have the notes from twelve customer calls. You know what the numbers say, roughly.

What you do not have is the page someone else can read in five minutes. The investor update slips a week. The pricing proposal stays a spreadsheet nobody opens. The process audit lives in your head, which is why nothing gets automated.

The documents a business runs on are not many, and they all have the same shape. A title that says what it is. Four numbers that matter. A chart or two with a paragraph each. A decision. Nobody writes that shape down, so every document is built from a blank page, and most of them never get built.

This pack writes the shape down, twenty times.

What Is a Business Document, in This Pack?

A single page, 1080 pixels wide, three to four phone screens tall. A meta line with the company and the period. A title at 118 pixels, two lines at most. A subtitle that says what the reader gets. A row of four KPI tiles, or a hero block where tiles make no sense. Tier cards for a pricing proposal, persona cards for customer research, the org tree for the agent chart. A summary paragraph that gives the conclusion first.

Then numbered sections. Every section is a heading, a paragraph of two or three sentences, and one white card holding a graphic and a short note. The graphics are drawn as SVG inside the file. Bars with the value printed on every bar, a line with a dashed trend, a donut with the total in the middle. A funnel, a 2×2 map, progress bars, a gantt. No library, no image, nothing to load.

At the end, when the document needs one, a tinted callout with the decision, the rule, or the next step.

That is the whole design system. Twenty documents use it, so once you have read one you can read all of them. Once Claude has built one, it builds the rest the same way.

The Twenty Documents

Marketing. A quarterly marketing analysis: spend versus leads by channel, the weekly trend with its regression line, the funnel from impressions to closed. Then the three best ads as cards, a zip-code table with scale, hold and cut badges, and three moves for next quarter. A go-to-market plan: a twelve-week gantt, the channel mix, the number you are aiming at. A competitor analysis: a logo row, a positioning map, a feature matrix of ticks, the fee ladder. Then rating against review count, three competitor homepages reduced to headline and button, and the gaps nobody is filling.

Customers and pricing. Customer research: persona cards with their share of the interviews, themes as praise-versus-complaint bars, six quotes with green and red edges. Then the journey with an emotion line and the five changes to make first. A pricing proposal: three tier cards with the middle one raised, the four price-sensitivity curves with the fair price marked, the ladder against competitors. Then three revenue scenarios, the migration of current customers, the objections and their short answers. Unit economics: what a customer costs, what a customer is worth by year, retention by cohort. Market sizing: TAM, SAM and SOM as nested rings, growth by zone.

Operations. A process audit: hours by area, the inventory of every recurring process with an automate, delegate or keep verdict, an effort-versus-impact map with numbered dots. Then hours returned month by month, the first five, a 30-60-90 plan. An org chart for a team that includes AI agents: the owner, the human leads, the agents stacked under them, who does the work. Then a lead's journey across six agents, the decision-rights table, the escalation rules. A standard procedure for client onboarding with owners, artefacts and the checklist. A weekly ops report with four numbers, this week against last, and the items that need a decision. A launch checklist with status badges and launch day hour by hour.

Money and the board. A 13-week cash flow with the closing balance by week and where the money goes. An investor update: KPI tiles with deltas, actual against plan, highlights and lowlights, unit metrics, the team, two asks. A board memo for one decision: the ask, the numbers, the exit if it fails.

People and planning. A hiring scorecard: year-one outcomes with numbers, weighted competencies, the deal-breaker. Quarterly OKRs with a progress bar per key result and what changes this week. A one-page strategic plan: the targets, one rock a quarter, the SWOT in four lines. A pipeline review: deals by stage as a funnel, what is going stale. A client proposal: what is included, the price next to what they pay today, the next step.

Every one of the twenty ships built, for a fictional home-services company, so you see what good looks like before you type anything.

How It Works in the Chat

Install the pack. The start file in the folder shows both ways. Drop it into Claude Code's skills folder, or upload the zip under Settings and Capabilities in the Claude app. Then say something like this:

Claude asks for anything missing, in one message. Then it does the one thing that makes this work: it writes the brief before the page. The title, the subtitle, the four tile values, the summary, and one line per section with the exact numbers that section will show. You check the numbers there. A page is cheap to rebuild; a wrong number in a sent PDF is not.

Say "build it" and it returns the whole HTML file. In Claude Code it saves the file next to your input. In the app it gives you the code to save as process-audit.html. Open it, scroll it once, and if one number is wrong, say which and it rewrites only that block.

The first document takes a few minutes because the brief is new. By the third, you are mostly pasting exports.

Copy This Prompt

If you want to try one document before installing anything, paste this into any Claude chat. It carries the page rules and one document's blueprint inside it.

You are my document designer. I will give you raw input about my business
and you return ONE finished document as a single HTML file, 1080 px wide,
with every chart drawn as inline SVG. No external scripts, no images.

The page, top to bottom:
- A meta line: company and period on the left in small caps grey, the
  document type on the right in a dark rounded tag.
- A title at 118 px, weight 800, two lines at most.
- A subtitle at 33 px grey: one or two sentences, what the reader gets.
- Four KPI tiles: white, a small caps label, a 62 px number, a delta line
  in green (good), red (bad) or grey (neutral).
- One summary paragraph: the conclusion first.
- Numbered sections. Each one: a 52 px heading with the number in
  [MY ACCENT COLOR, default #6245C5], a two-to-three-sentence paragraph
  that names the number that matters below, then one white card
  (30 px corners, 1 px #E4E1EA border, 38 px padding) with the chart and
  a short grey note.
- Charts: every bar and point carries its value in bold; no gridlines;
  one baseline; rounded bar ends; axis labels in grey at 22 to 24 px;
  SVG with a viewBox and width 100%.
- Fonts: Inter from Google Fonts with a system sans fallback.
  Background #FAFAF7, text #15131D, paragraphs #3A3748.
- Never invent a number. If one is missing, ask me once; if unknown,
  write "estimate" next to it.

The document: PROCESS AUDIT.
KPI tiles: processes mapped, hours a week, ready to automate, hours
returned.
Sections: 01 Where the week goes (a donut of hours by area with a legend
list); 02 The inventory (a table: process, owner, hours a week, cadence,
and a verdict badge: automate green, delegate amber, keep grey);
03 Effort versus impact (a 2×2 map, one numbered dot per process, effort
on x, hours returned on y, the quick-wins quadrant top left);
04 Hours returned, month by month (bars, five months, assuming one
process goes live each week); 05 The first five (a table: process, how,
hours, live date); 06 30 · 60 · 90 (three tinted cards).

Before the page, write the brief: title, subtitle, the four tile values,
the summary, one line per section with the exact numbers it will show.
Wait for my "build it". Then return the complete HTML file and end with
"Done."

My company: [NAME, WHAT IT DOES, SIZE]
My input: [TWO WEEKS OF CALENDARS, INBOXES, THE TASK BOARD, OR A LIST
OF WHAT EACH PERSON DOES EVERY WEEK]

Swap the document block for any of the other nineteen using the sections described above. The pack has all twenty written out, with the worked example for each.

What You Get Back

1. The brief: every number the page will show, on one sheet, before any layout.

2. The page: one self-contained HTML file with the title, the tiles, the charts and the paragraphs, built to the same system as the other nineteen.

3. A PDF when you need one: Chrome, print, save as PDF, background graphics on.

4. A reusable blueprint. Next quarter you paste the new export and the same document comes back with the new numbers.

5. Twenty worked examples, so the first one you build already has a reference to match.

Honest Limits

Claude draws charts from the numbers you give it. It does not pull data from your ad account, your bank or your CRM; you paste the export. In Claude Code it can read a CSV file you point it at, which saves the paste.

The page is a web page, not a Word document. It prints to PDF cleanly from Chrome and it opens anywhere, but if your board wants a .docx, this is not that.

The charts are hand-drawn SVG, which is why they look the same on every machine and need nothing installed. It also means a chart type the pack does not have, a map or a sankey, needs a sentence from you describing it. The result will be plainer.

The quality of the document is the quality of the input. Twelve real interview transcripts give you real customer research. Three lines of memory give you three lines of memory with a nice title.

If you want the reel version of this idea, the AI editing pack is the other build: six short-form video formats from one chat. This one is for the documents your business runs on.

Do This First

Take the one export you already have open. The ad account, the bank feed, the calendar. Run the matching document on it with the prompt above or the pack. Read the brief, fix one number, say "build it".

Ten minutes. If you do not like the page, you lost ten minutes and kept a blueprint that builds every version after it.

Done.