Train Your Team to Brief From Data
Get consistent executive briefings from any analyst on your team
Your analysts produce good data but inconsistent summaries. Some bury the lead, others skip context, and executives get frustrated asking for rewrites.
That is the gap this drop closes. It is a data & analysis 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
Heads of analytics, research or business intelligence teams who need multiple people to produce decision-ready outputs
How it works
The skill file does five things, in this order.
1. Build your briefing template. Define the exact structure every briefing should follow: decision required, three key findings, risks, recommendation.
2. Create the team prompt. Write one reusable prompt that takes any data input and outputs your standard format, then store it where the team can access it.
3. Run three live examples. Have each team member use the prompt on real reports from the past month and compare outputs in a working session.
4. Document the exceptions. Identify which report types need modifications to the standard prompt and create three variant versions maximum.
5. Set the review checkpoint. Decide whether Claude output goes straight to executives or through a lead analyst first, then communicate that gate clearly.
What comes back
Your team produces briefings that look like they came from one person, and new hires get up to speed in days instead of months
The mistake to avoid
Test the prompt with your weakest analyst first. If it works for them, it will work for everyone and you will know where the template needs more guidance.
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
You are a business intelligence analyst preparing an executive briefing.
Source material:
{paste_report_data_or_findings}
Produce a briefing following this exact structure:
1. DECISION REQUIRED
One sentence stating what the executive needs to decide.
2. THREE KEY FINDINGS
Bullet points, each one sentence, in order of impact.
3. RISKS
Two to three specific risks if we proceed, and two to three if we do not.
4. RECOMMENDATION
One clear recommendation with two supporting reasons.
Constraints:
- Total length under 300 words
- No jargon unless defined
- Numbers must include context (versus what, versus when)
- Findings must be specific, not directional language like "improved" or "declined"
If the source material is incomplete, state exactly what information is missing before proceeding.