meeting-minutes
Skill420 starsChanged 57 days agoMITView on GitHub
Turn supplied meeting notes or transcripts into sourced minutes, keeping discussion, statements, confirmed/proposed decisions and proposed actions distinct.
45 other projects use a version of this.
Adopted by
Most recently taken up by
- netarz/gisoo-skills-registrytheir own version, first seen Nov 15, 2026
- CT-masato-hino/claude-code-project-packtheir own version, first seen Nov 15, 2026
- methylo/claude-skill-booktheir own version, first seen Nov 8, 2026
- Vantus-ai/construction-ai-librarytheir own version, first seen Nov 8, 2026
- ActuallyNodejam/openpaperworktheir own version, first seen Nov 8, 2026
- tang1693/yunduan-ai-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use weekly-report, contract-review and 5 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 AzureSkillweekly-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
AnthropicSkillcontract-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
shanggqmSkilldata-analysis
数据分析技能,提供结构化的数据查询、统计分析和报告生成工作流。当用户需要查询数据库、进行数据统计分析、生成分析报告时使用。按规范输出原始数据、计算结果、Markdown报告和HTML可视化报告。
Also in 3 projects that use this
asterkinSkilladr
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
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
SentrySkillskill-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
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- github/awesome-copilot★ 41ksame name
- genspark-ai/genoffice★ 12ksame name
- CatCatUncle/openworkbuddy★ 413same name
- bam-bam-2/solo-skills★ 366same name
- modimihir07/agentic-os★ 209same name
- cookyman74/llmwiki-harness★ 34same name
- ulises-jeremias/agent-toolkit★ 20same name
- marc-ing/marc-skills★ 14same name
- methylo/claude-skill-book★ 12same name
- z-Zihan/Evir★ 11same name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- docs/agents.mdAGENTS.md
- skills/project/templates/AGENTS.mdAGENTS.md
- skills/project/templates/CLAUDE.mdCLAUDE.md
- agreementSkill
- architecture-knowledgeSkill
- color-palette-generatorSkill
- csv-to-sifSkill
- demographics-analysisSkill
- drawing-quantity-extractSkill
- environmental-analysisSkill
- epd-compareSkill
- epd-parserSkill
- epd-researchSkill
- epd-to-specSkill
- ffe-spec-bookSkill
- invoiceSkill
- learnSkill
- lighting-report-extractSkill
- master-scheduleSkill
- mobility-analysisSkill
- normaSkill
- norma-supportSkill
- nyc-acrisSkill
- nyc-bsaSkill
- nyc-dob-permitsSkill
- nyc-dob-violationsSkill
- nyc-hpdSkill
- nyc-landmarksSkill
- nyc-property-reportSkill
- occupancy-calculatorSkill
- product-auditSkill
- product-cut-sheetSkill
- product-data-cleanupSkill
- product-data-importSkill
- product-enrichSkill
- product-image-processorSkill
- product-librarySkill
- product-matchSkill
- product-pairSkill
- product-researchSkill
- product-spec-bulk-fetchSkill
- product-spec-pdf-parserSkill
- product-url-clipSkill
- projectSkill
- proposalSkill
- receiveSkill
- resize-imagesSkill
- schedule-quantity-reconcileSkill
- sif-to-csvSkill
- site-historySkill
- site-visit-reportSkill
- skill-makerSkill
- slide-deck-generatorSkill
- spec-writerSkill
- studio-feedbackSkill
- studioSkill
- tasklistSkill
- timetrackerSkill
- tool-catalogSkill
- workplace-programmerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Before acting, read the host contract, this component's declaration (skill:meeting-minutes), and applicable workspace semantics.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/as:meeting-minutes
Before acting, read the host contract, this component's declaration (skill:meeting-minutes), and applicable workspace semantics. Load only the required modes from the shared catalog.
<!-- architecture-studio:harness-compatibility -->Use the host adapter and available native tools or ordinary task-specific code. Apply the receive-owned semantic document rules directly; no installed library, nested skill invocation, runner or executable reconstruction is required. Resolve context before durable work. Existing exact authorization persists; ask only for material missing information or missing permission.
Own authored event documents of kind meeting. Preserve the minutes template distinctions: discussion, stated information, confirmed decisions in the meeting, proposed decisions, proposed tasks and open questions. A meeting-confirmed choice is not automatically a durable project decision. Unknown attendees, attribution, dates or actions remain unknown.
Resolve the project and source scope. Distinguish event date, source date, creation date and revision. Use only supplied/authorized evidence; no access or transcript completeness is inferred. List stable item IDs so later promotions cite exact statements.
Before changing records
Before persistent changes, follow the native mutation sequence: Inspect → Prepare → Verify preparation → Apply → Verify result → Complete. Inspect pending work first. Finish and verify preparation before the first canonical write: separately reread every saved original and prepared file, check its complete actual bytes, establish durable saving, and inspect actual permissions, ownership and ACLs. Merely writing recovery files does not finish verification. Apply only that verified set. Mark complete only after fresh readback validates the entire affected result and its relationships. Read-only requests and inline drafts need no publication sequence.
Saving minutes affects the complete meeting document plus DOCUMENTS.csv and any explicitly authorized attachment registrations. Prepare and verify that full set before writing the first member. Source notes/transcripts remain read guards; a saved meeting record does not authorize changes to PROJECT.md, TASKS.csv or decision records.
Prepare the minutes, confirm missing phase/stage/scope/originator/date/kind coordinates, then apply documents.resolve and documents.register as native semantic procedures with kind meeting. Preserve received attachment names; attachments use their own registered IDs and actual links. Explicit revisions receive a new record with supersedes; do not overwrite prior bytes or silently invent numbering to disguise collision.
Read back the saved document before offering promotion. Show selected fact, decision and task candidates separately; general approval of minutes does not promote them. Project owns sourced current facts/decisions, tasklist owns TASKS.csv. Preserve reported/proposed status throughout the handoff. Direct invocation works without a coordinator or another skill-call tool; print the bounded next action if unavailable.
meeting.prepare means the authored preparation procedure above; it may produce an inline draft without a workspace write. Persistence uses the shared native document contract, restricted here to kind meeting and authorized attachments. A saved record does not authorize its proposed actions or promote facts/decisions automatically.
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
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.

