本文へ移動
cccskills
無料GitHub で公開

board-minutes

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

  1. Identify meeting metadata — organisation, board, date, location, chair, secretary, attendees, apologies, guests, and quorum status.
  2. Group notes by agenda item — preserve the board's agenda order where possible.
  3. Extract formal decisions — approvals, rejections, deferrals, delegated authority, and resolutions.
  4. Extract action items — owner, due date, dependency, and follow-up forum.
  5. Flag governance-sensitive items — conflicts of interest, dissent, recusal, privileged discussion, confidential information, and items requiring legal/secretarial review.
  6. Draft minutes in official-record style — concise past tense, neutral tone, no transcript filler.
  7. 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:

ActionOwnerDue dateNotes
[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

#ActionOwnerDue dateStatus
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

Example Trigger Phrases

  • "Draft board minutes from these notes."
  • "Write governance minutes for this meeting."
  • "Turn this transcript into formal board minutes."
  • "Record the board's decisions and actions."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する