meeting-notes-to-actions
Skill1 starsChanged 4 months agoMITView on GitHub
Convert supplied meeting notes or transcripts into a summary, decisions, action items, owners, due dates, dependencies, and open questions while distinguishing discussion, proposals, decisions, and commitments. Use when the source is meeting material; do not invent owners, dates, decisions, or task-system updates, and mark missing fields TBD. 将给定会议记录或转写整理为摘要、决定、行动项、负责人、截止日期、依赖和待确认问题,并区分讨论、建议、决定和承诺。来源是会议材料时使用;不得虚构负责人、日期、决定或任务系统更新,缺失字段标记 TBD。
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
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 10
Read references/productivity-evidence-and-file-safety.md.
- Distinctive: line 13
Read the complete notes before extraction.
- Distinctive: line 14
Create an action only when the notes contain an actionable commitment or the user asks to convert a clearly stated recommendation.
“Common” is measured: kept by at least 6 in 10 of the 7 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
English
Meeting Notes to Actions
Read references/productivity-evidence-and-file-safety.md. Use assets/action-items-template.md for a task-system-ready table.
- Confirm the meeting date only if present, participants only if present, and whether the output should be concise or retain discussion context.
- Read the complete notes before extraction. Separate factual updates, discussion, proposals, explicit decisions, explicit commitments, blockers, and open questions.
- Create an action only when the notes contain an actionable commitment or the user asks to convert a clearly stated recommendation. Preserve the supporting context or source excerpt.
- Copy explicit owners and due dates exactly. Use
TBDwhen absent or ambiguous; never infer ownership from who spoke or infer dates from urgency words. - Merge duplicates only when action, scope, and outcome match. Preserve distinct dependencies, acceptance conditions, and conflicting statements.
- Return a summary, decisions, action table, dependencies, risks, and questions requiring confirmation. Do not claim tasks were created in an external system unless a tool actually completed that action under user authorization.
Output Contract
- Meeting summary
- Explicit decisions
- Action table with owner, due date, dependency, and evidence
- Open questions and TBD fields
- Risks, blockers, and external-system status
简体中文
会议纪要转行动项
读取 references/productivity-evidence-and-file-safety.md。需要适合任务系统的表格时使用 assets/action-items-template.md。
- 会议日期和参会者只在材料明确出现时记录,并确认输出应精简还是保留讨论上下文。
- 完整阅读记录后再提取,区分事实更新、讨论、建议、明确决定、明确承诺、阻塞和待确认问题。
- 只有记录包含可执行承诺,或用户要求把明确建议转为任务时才创建行动项,并保留支持上下文或原文。
- 原样提取明确负责人和截止日期;缺失或歧义时使用
TBD,不根据发言者猜负责人,也不根据“尽快”等词猜日期。 - 只有行动、范围和结果一致时才合并重复项,保留不同依赖、验收条件和冲突表述。
- 输出摘要、决定、行动表、依赖、风险和待确认问题。除非工具在用户授权下真实完成,不得声称已写入外部任务系统。
输出契约
- 会议摘要
- 明确决定
- 含负责人、截止日期、依赖和证据的行动表
- 待确认问题和 TBD 字段
- 风险、阻塞与外部系统状态
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- Lethe044/agentskill-kit★ 48same name
- mDevsLabs/Skills★ 2same name
- rickbauer327-cell/solo-stack-starter★ 2same name
- ahnchen1983/agentic-substrate★ 1same name
- Baba01hacker666/dummyskills★ 0same name
- create-aquarius/business-skills-ja★ 0same name
- kakarot-oncloud/claude-skills★ 0same name
- SkillMedev/remote-team-toolkit★ 0same name
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 repository40 other files it gives its agents.
- api-contract-reviewSkill
- architecture-decision-recordSkill
- architecture-deepening-analysisSkill
- bug-root-cause-analysisSkill
- change-impact-analysisSkill
- ci-failure-diagnosisSkill
- configuration-auditSkill
- content-consistency-checkSkill
- database-migration-reviewSkill
- dead-code-verificationSkill
- decision-prototypeSkill
- dependency-upgrade-analysisSkill
- documentation-syncSkill
- document-reviewSkill
- excel-data-quality-check-basicSkill
- feature-implementationSkill
- pdf-review-basicSkill
- pdf-reviewSkill
- performance-regression-analysisSkill
- presentation-outlineSkill
- project-health-checkSkill
- release-readiness-checkSkill
- repo-doctor-routerSkill
- repo-onboardingSkill
- report-writerSkill
- requirements-clarificationSkill
- requirements-to-specSkill
- research-briefSkill
- safe-change-planSkill
- safe-code-reviewSkill
- safe-fix-implementationSkill
- safe-test-implementationSkill
- security-focused-reviewSkill
- session-handoffSkill
- skill-authoringSkill
- skill-quality-auditSkill
- spec-to-work-itemsSkill
- spreadsheet-data-cleaningSkill
- test-gap-analysisSkill
- word-document-review-basicSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

