skills/board-minutes/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills board-minutesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Ask for these if not already provided:
[to confirm].Organisation: [Organisation name] Meeting: [Board / Committee name] Date and time: [Date, start–end time] Location: [Location / video conference] Chair: [Name] Minute taker / secretary: [Name]
Present: [Names and roles] Apologies: [Names] In attendance / guests: [Names, roles, agenda items attended for] Quorum: [Confirmed / Not confirmed / To confirm]
[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].]
[Record whether previous minutes were approved, amended, or deferred. Include action follow-up if relevant.]
Repeat this structure for each 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:
Actions: | Action | Owner | Due date | Notes | |---|---|---|---| | [Action] | [Owner] | [Date / TBC] | [Context] |
[Items raised outside the agenda, with any decisions or actions. If none: "No further business was raised."]
Date: [Date / TBC] Location: [Location / TBC] Key agenda items to carry forward: [List]
| # | Action | Owner | Due date | Status | |---|---|---|---|---| | 1 | [Action] | [Owner] | [Date] | Open |
These minutes were approved by the board on [date] as an accurate record of the meeting held on [meeting date].
Chair: ______________________ Date: ______________________
[to confirm]: [List][to confirm][to confirm]business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.