agentleFS
RafaelFerSilvaRafaelFerSilva/refinement-agent-skills/skills/meeting-minutes/SKILL.md

meeting-minutes

Skill2 starsChanged 18 days agoMITView on GitHub

Transforms a meeting transcript into auditable minutes: decisions and action items with provenance, presumed agreements for asynchronous confirmation, action items in JSON, and discovery input.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly-report, contract-review and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    weekly-report

    **WORKFLOW SKILL** — Generate weekly executive reports for the azd team. Pulls PR/issue/release data from GitHub, reads changelogs, combines with team notes, and produces a polished markdown report.

    Also in 7 projects that use this

  • AnthropicSkill

    contract-review

    Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal agreement.

    Also in 4 projects that use this

  • shanggqmSkill

    data-analysis

    数据分析技能,提供结构化的数据查询、统计分析和报告生成工作流。当用户需要查询数据库、进行数据统计分析、生成分析报告时使用。按规范输出原始数据、计算结果、Markdown报告和HTML可视化报告。

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

The file

Files
SKILL.md

Meeting minutes

Process a transcript and generate a structured, auditable record. Minutes become facts: three weeks later someone will cite this document as proof of what was agreed. Therefore, everything you record is traceable to the transcript, and everything you presume remains visibly separated from what was explicitly stated. Recording is certifying; your analysis must never disguise itself as attendee speech.

This workflow is synthesis without interview: the meeting has already occurred. Questions left open are directed to their recipients via questionnaires, and requirement content flows to /requirements-discovery.

Transcript: $ARGUMENTS

Provenance boundary

Grounded in requirements-rigor, here provenance assumes three forms:

  • [STATED: speaker, "short paraphrase"] (pt-BR: [DITO: falante, "paráfrase curta"]): stated in the transcript. Every action, decision, and priority carries who stated it and a 5 to 15 word paraphrase. An honest paraphrase suffices for auditing.
  • [ASSUMED: base] (pt-BR: [PRESUMIDO: base]): your analysis inferred from conversational patterns: silence following a proposal, ambiguous "ok", task implied by a decision that no one explicitly assumed. Presumed items never enter Decisions, Action Items Table, or JSON; they live in presumption sections, with the excerpt and who must confirm.
  • [TO BE DEFINED] (pt-BR: [A DEFINIR]): assignee or deadline neither mentioned nor inferable. The placeholder is the correct answer.

Quick test: "if an attendee reads this line and says 'I never said that', can I point to the excerpt?" Yes: STATED. "They didn't say it directly, but implied it": ASSUMED. Neither: TO BE DEFINED, or excluded from minutes. Remaining markers from requirements-rigor, such as [INFERENCE: base], remain valid.

Steps

  1. Metadata. Read docs/agents/refinement.md in the workspace to identify the configured language (en-US or pt-BR, default en-US) and publishing path. Minutes, questionnaires, and generated inputs follow this language. Identify title, date, duration, attendees with roles, project, and glossary terms distorted by automated transcription. Date is mandatory: deadline arithmetic depends on it. If missing, ask in a single line before proceeding. Read CONTEXT.md for glossary terms when present. Completed when: date and attendees are established.
  2. Triage. INTACT (continuous audio, identifiable speakers), DEGRADED (inaudible segments, misassigned speakers, cuts), INSUFFICIENT (too brief, or not the meeting from metadata). INSUFFICIENT: state reason and stop; facade minutes must not circulate as official records. DEGRADED: every gap that might have contained an action or decision becomes an open question ("inaudible segment at ~12min following proposal by X"); gaps are never reconstructed. Distorted terminology: apply glossary spelling and mark [POSSIBLE TRANSCRIPTION ERROR: original -> adopted] (pt-BR: [POSSÍVEL ERRO DE TRANSCRIÇÃO: original -> adotada]) in section 0, using only the adopted term throughout the body. Personal details, health, family, remarks on absent colleagues: omit from all sections; a project commitment embedded in personal context is recorded without the circumstance. Unidentified speaker with commitment: assignee [TO BE DEFINED: unidentified speaker at ~Xmin] and open question. A note that personal content was omitted may appear in triage without details; deadlines mentioned only inside personal context are kept textually without personal circumstance. Completed when: triage is recorded in section 0 with detected transcription errors.
  3. Extract. Apply the rules from RULES.md: retraction and supersedence, action item granularity, priority with provenance, what counts as a decision. Completed when: every decision and action item carries STATED provenance, and presumptions live strictly in sections 4 or 5.
  4. Write minutes following TEMPLATE.md. In "actions mode", write sections 0, 3, 6, 7, and 8 only: the narrative sections are what that mode drops, while triage qualifies how the table reads (a degraded transcript or a corrected term changes what its rows mean) and the self-audit is what proves the table and the JSON agree, which in this mode is the entire deliverable. Completed when: the file exists at .scratch/<project>-<YYYY-MM-DD>/minutes.md (or where configured in docs/agents/refinement.md), with final disclaimer.
  5. Self-audit and report in a single line in section 8: every real action in the table has a matching JSON object and no JSON object exists outside the table; every row and decision carries STATED; no ASSUMED leaked into table or decisions; priorities match between table and JSON; JSON dates are ISO or null. Completed when: section 8 states "Self-Audit: OK" or details corrections.
  6. Route open items. Presumed agreements and open questions with recipients outside the session: write one questionnaire per recipient following QUESTIONNAIRE.md in requirements-rigor, alongside minutes, and link each from the generating section. Excerpts with requirement content (stated needs, capabilities, constraints): write discovery-input.md alongside minutes following the template at the end of TEMPLATE.md, and instruct user that /requirements-discovery begins from it. Completed when: each presumed agreement has a recipient and questionnaire, and discovery input exists when the meeting contained requirement content.

Final notice

Published artifacts only. A triage that stops the workflow and an examination round publish nothing, so they carry no notice: the notice qualifies an artifact someone may circulate.

⚠️ These minutes are an AI-generated draft derived from a transcript. They require attendee validation before circulating as an official record, particularly Presumed Agreements, which were not explicitly verbalized and require confirmation.

In a pt-BR workspace:

⚠️ Esta ata é um rascunho gerado por IA a partir da transcrição. Requer validação dos participantes antes de circular como registro oficial, em especial os Acordos Presumidos, que não foram verbalizados e precisam de confirmação explícita.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.