Get Your Team Recording Meetings the Same Way
Five people, one format, no more guessing what was decided
One person writes paragraphs, another uses bullet points, a third forgets entirely. You spend Monday mornings chasing what was actually agreed in last week's meetings.
That is the gap this drop closes. It is a operations 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
Team leads whose people take notes differently or not at all
How it works
The skill file does five things, in this order.
1. Build one template the whole team will use. Define the exact sections every meeting note needs: participants, decisions, action items with owners and dates, parking lot items.
2. Write the prompt once, share it as a snippet. Store the formatting prompt in a shared document or chat where anyone can copy it before their meeting.
3. Run a pilot with two meetings first. Pick two different people to test the system, compare outputs, fix what doesn't work before rolling out wider.
4. Set one person as the format keeper. Give someone the job of reviewing notes weekly and flagging anyone who drifts from the template.
5. Make the output location non-negotiable. Everyone posts finished notes to the same folder or channel within two hours of the meeting ending.
What comes back
A team that produces identical note structures without you policing every meeting
The mistake to avoid
Resistance usually comes from people who think their meetings are special. Show them two anonymized examples where the template worked for very different meeting types.
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 meeting documentation assistant. Format these raw meeting notes according to our standard template.
Meeting context: {meeting_type} on {date}
Raw notes or transcript: {input_notes}
Produce output in exactly this structure:
MEETING: {meeting_type}
DATE: {date}
PARTICIPANTS: [list all attendees]
DECISIONS MADE:
1. [each decision as one clear sentence]
2. [continue numbering]
ACTION ITEMS:
- [task description] | Owner: [name] | Due: [specific date]
- [continue format]
DISCUSSION POINTS:
- [key topics discussed without decisions yet]
PARKING LOT:
- [items deferred or requiring future discussion]
Rules:
- Every action item must have both an owner name and a due date
- Decisions are statements of what was agreed, not opinions
- If a due date was not mentioned, flag it as [DATE NEEDED]
- If an owner was not assigned, flag it as [OWNER NEEDED]
- Keep each bullet to one sentence maximum
- No interpretation, only what was stated in the meeting