The Monthly P&L Narrative
Explain why the numbers moved, in language a non-finance board reads.
Everyone can see revenue fell 8%. What the board pays for is knowing which two customers and which one cost line caused it.
That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Founders and finance managers writing the same commentary every month.
How it works
The skill file does five things, in this order.
1. Export two periods. This month and the comparison period, same chart of accounts.
2. Decompose the variance. Volume, price, mix, and one-offs, separated.
3. Rank drivers by impact. Top three up, top three down, in currency not percentages.
4. Write the plain narrative. Three paragraphs, no jargon, causal not descriptive.
5. Flag what needs a decision. Separate noise from the two things that need action.
What comes back
A variance table, a three-paragraph narrative, and a short decisions-needed list.
The mistake to avoid
Give it last month's narrative too. It will then write this month's as a continuation, which is what a board actually wants to read.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Write the monthly P&L commentary from the attached exports.
1. VARIANCE TABLE, line item | current | comparison | delta (currency) | delta (%).
Sort by absolute currency delta, largest first.
2. DRIVER DECOMPOSITION, for the top 5 movements, split into volume, price,
mix, and one-off effects. State which you inferred versus which the data shows.
3. NARRATIVE, three paragraphs, no accounting jargon, causal. Paragraph one:
what happened to revenue and why. Two: what happened to costs and why.
Three: what this means for the next 90 days.
4. DECISIONS NEEDED, maximum three, each with the number that justifies it.
Never state a cause the data cannot support. Write "cause unclear" instead.
<current>{export}</current><prior>{export}</prior>