board-minutes
Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary
Install / Use
npx skills add mohitagw15856/pm-claude-skills --skill board-minutesInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of board-minutes
board-minutes scores 82/100 on our quality scale, 2272nd of 4,140 Development & Engineering skills we index.
Its SKILL.md is 6.6 KB long, well organised into 19 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,396 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 6 days ago, so board-minutes is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
board-minutes compared with similar skills
All 4 of these similar skills score higher than board-minutes; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| board-minutes (this skill)by mohitagw15856 | 82 | 1.4k | 6d ago | SKILL.md |
| ai-job-searchby MadsLorentzen | 100 | 44.6k | 1d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.7k | today | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 8d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 8d ago | SKILL.md |
Frequently asked questions
- How do I install board-minutes?
- Run
npx skills add mohitagw15856/pm-claude-skills --skill board-minutes. The install tabs above show the steps for each supported agent. - Which AI agents does board-minutes work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is board-minutes safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is board-minutes still maintained?
- The repository was last updated 6 days ago, so board-minutes is actively maintained.
Skill content
View source on GitHubname: board-minutes description: "Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeting minutes for a board, or a formal record of decisions and actions. Produces structured board minutes with attendees, agenda items, resolutions, decisions, action register, and approval-ready wording."
Board Minutes Skill
Produce formal board meeting minutes that are concise, defensible, and useful as the official record. The minutes should capture what the board considered, what was decided, what actions were assigned, and any formal resolutions — without turning the document into a transcript.
What This Skill Produces
- Formal board minutes ready for review by the chair, company secretary, or governance lead
- A clear record of attendees, apologies, quorum, conflicts of interest, agenda items, decisions, resolutions, and actions
- An action register with owners, due dates, and status
- Optional draft approval wording for the next board meeting
Required Inputs
Ask for these if not already provided:
- Organisation / company name and board or committee name
- Meeting date, time, location, and meeting type (regular / special / committee)
- Attendees, apologies, guests, and chair / secretary names
- Agenda or topic list
- Meeting notes, transcript, or bullet summary of the discussion
- Decisions made, formal resolutions passed, votes, abstentions, or objections
- Actions agreed — owner and due date for each, if known
- Any conflicts of interest, confidential items, or matters to redact from circulation
Minute-Taking Principles
- Record decisions, rationale, and actions — not a verbatim transcript.
- Use neutral, factual language. Avoid attributing opinions unless attribution is necessary for a conflict, dissent, or formal record.
- Separate discussion from decisions. A reader should be able to find what was approved and who must do what next.
- Preserve exact resolution wording when the source materials provide it; formal resolutions often need verbatim treatment.
- Keep legal precision without over-lawyering. If the notes mention regulated, legal, employment, or financial matters, flag that the draft should be reviewed by the appropriate governance or legal owner.
- Do not invent quorum, votes, attendees, or resolutions. Mark unknown items as
[to confirm].
Process
- Identify meeting metadata — organisation, board, date, location, chair, secretary, attendees, apologies, guests, and quorum status.
- Group notes by agenda item — preserve the board's agenda order where possible.
- Extract formal decisions — approvals, rejections, deferrals, delegated authority, and resolutions.
- Extract action items — owner, due date, dependency, and follow-up forum.
- Flag governance-sensitive items — conflicts of interest, dissent, recusal, privileged discussion, confidential information, and items requiring legal/secretarial review.
- Draft minutes in official-record style — concise past tense, neutral tone, no transcript filler.
- Add an action register and approval footer — make follow-up and next-meeting approval straightforward.
Output Format
Minutes of the [Board / Committee] Meeting
Organisation: [Organisation name] Meeting: [Board / Committee name] Date and time: [Date, start–end time] Location: [Location / video conference] Chair: [Name] Minute taker / secretary: [Name]
1. Attendance
Present: [Names and roles] Apologies: [Names] In attendance / guests: [Names, roles, agenda items attended for] Quorum: [Confirmed / Not confirmed / To confirm]
2. Conflicts of Interest
[State whether any conflicts were declared. If a conflict was declared, record the person, agenda item, and whether they recused themselves. If unknown, write [to confirm].]
3. Approval of Previous Minutes
[Record whether previous minutes were approved, amended, or deferred. Include action follow-up if relevant.]
4. Agenda Items
Repeat this structure for each agenda item.
4.[N] [Agenda Item]
Paper / presenter: [Paper reference or presenter, if known]
Discussion summary: [Concise factual summary of the material points considered by the board. Capture key risks, options, and rationale. Do not write a transcript.]
Decision / resolution:
- [Approved / Not approved / Deferred / Noted]
- Formal resolution wording, if applicable: "Resolved that [exact decision]."
Actions: | Action | Owner | Due date | Notes | |---|---|---|---| | [Action] | [Owner] | [Date / TBC] | [Context] |
5. Any Other Business
[Items raised outside the agenda, with any decisions or actions. If none: "No further business was raised."]
6. Next Meeting
Date: [Date / TBC] Location: [Location / TBC] Key agenda items to carry forward: [List]
Action Register
| # | Action | Owner | Due date | Status | |---|---|---|---|---| | 1 | [Action] | [Owner] | [Date] | Open |
Approval
These minutes were approved by the board on [date] as an accurate record of the meeting held on [meeting date].
Chair: ______________________ Date: ______________________
Governance Review Notes
- Items marked
[to confirm]: [List] - Potentially sensitive items for review: [Legal / financial / employment / confidentiality / conflict-of-interest items]
- Open drafting questions: [Anything the minute taker must verify before circulation]
Quality Checks
- [ ] The minutes are concise and not a transcript
- [ ] Every formal decision or resolution is clearly separated from discussion
- [ ] Every action has an owner and due date, or is marked
[to confirm] - [ ] Attendance, apologies, guests, chair, secretary, and quorum are recorded or marked
[to confirm] - [ ] Conflicts of interest and recusals are captured if present
- [ ] Sensitive or uncertain items are flagged for governance/legal review rather than guessed
- [ ] The final draft can be approved as an official record without relying on hidden context
Anti-Patterns
- [ ] Do not invent resolutions, votes, attendees, quorum, or action owners when the notes are silent
- [ ] Do not write a blow-by-blow transcript; minutes capture material discussion, decisions, and actions
- [ ] Do not use emotive or blame-heavy language; keep the official record neutral and factual
- [ ] Do not bury decisions inside long paragraphs; make approvals, deferrals, and actions easy to find
- [ ] Do not omit conflicts of interest, dissent, abstentions, or recusals when they appear in the source notes
- [ ] Do not provide legal advice; flag governance-sensitive items for qualified review
Related Skills
ai-job-search
44.6kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
