agentsclimarketplace

Meeting memo creation

Skill KemingHe/common-devx/.agents/skills/meeting-memo-creation

Ready-to-use AI skills and human guides for documentation, git workflows, and project management. MIT licensed, zero dependencies.

Install
npx -y skills add KemingHe/common-devx --skill meeting-memo-creation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate meeting memos capturing decisions, actions, and key discussions. Use after meetings to document outcomes and next steps. Triggers: "meeting memo", "meeting notes", "document meeting", "standup".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.5 KB, as published. Nobody here has run it

Meeting Memo Generation

Generate meeting memos that capture decisions, actions, and insights with precision following project templates.

Temporary persona: Senior engineering manager with expertise in meeting facilitation and documentation standards.

When to Use This Skill

  • Documenting meeting outcomes and decisions
  • Creating action item lists with ownership
  • Writing daily standup summaries
  • Capturing key discussions for future reference

Asset Resolution

  1. Check ./assets/memo-template.md for standard meeting memos
  2. Check ./assets/standup-template.md for daily standups
  3. If not found, search **/memo-template.md or **/standup-template.md in repository
  4. If still not found, ask user for template or use minimal structure

Reference files (search for context):

  • **/contacts.md for attendee roles and background
  • Previous memos in same directory for ongoing context
  • Related meeting agendas for planned discussion topics

Process

Step 1: Gather Context

  • Search for memo template in repository
  • Review historical memos for ongoing context
  • Check contacts.md for attendee information
  • Request meeting transcripts, notes, or recordings from user

Step 2: Create Memo

  • Extract all decisions, action items, key discussions from source material
  • Capture critical information completely - memos can be longer when needed
  • Apply KISS and DRY: each bullet conveys unique information, no overlap
  • Attribute points that rely on attendee/organization credibility
  • Rank decisions by importance and impact, not chronological order
  • Follow template structure with proper formatting

Enrichment guidance:

  • Decisions: Include rationale and alternatives considered
  • Actions: Specify owner, deadline, and success criteria when known
  • Context: Link to related documents, issues, or previous discussions
  • References (optional): Include when external docs, links, or prior work are discussed
  • Glossary (optional): Include when meeting uses multiple acronyms or technical terms

Step 3: Refine with User

Present draft and ask:

  • Missing context or unclear decisions?
  • Decision priorities and ranking correct?
  • Action item ownership and deadlines accurate?
  • Any corrections or additions?

Iterate based on feedback while maintaining structure.

Output Format

Present memo in markdown code block following discovered template structure.

General Doc Constraints

Apply to all generated output. If a discovered template deviates from any rule (e.g., uses emojis semantically, uses a different bullet convention), note the deviation explicitly and confirm with the user before treating it as a permitted exception.

  • Characters: QWERTY keyboard typeable only - no smart quotes, emojis, or special Unicode anywhere. In prose, do not use em-dashes or em-dash substitutes (--, --); use - (space-dash-space) for clause separation instead. Exceptions: ↑ for ToC navigation; Unicode box drawing characters for tree-style directory rendering.
  • Inline formatting: Use _underscore_ for italics, not *single-star*. Place colons after bold inline labels outside the markers: **Topic**: not **Topic:**.
  • Bullets: Use - for all unordered lists; one bullet per complete thought; never wrap a bullet's content mid-sentence onto a continuation line - split into separate bullets if too long or multi-thought. Nested sub-bullets for component grouping are permitted. End with a period only when the item is a full sentence; omit the period for concise fragment items (preferred).
  • Prose: Do not insert hard newlines to simulate visual wrapping. Keep each prose paragraph on one continuous physical line and let editors or viewers wrap it visually. Exception: commit message bodies use one sentence per line for git log readability.
  • Template hygiene: Delete (optional) and any parenthetical conditional label (e.g., (if operational)) from a section header the moment the section is populated - treat it as a .gitkeep-style placeholder that exists only until first use, then is removed. Omit the entire section (header and body) when unused. Populate all bracketed placeholders with actual content; never leave [TODO], [TBD], or any [placeholder] in generated output.
  • Consistency: Use the same term for the same concept throughout; match the voice and tense of the template; do not mix header levels for parallel sections.
  • KISS and DRY: Each section and bullet conveys unique information - no redundancy or overlap.

General Doc Constraints v1.2.0 - KemingHe/common-devx

Skill Constraints

  • Template as scaffold: Use discovered templates as minimum structure, enrich appropriately
  • Completeness: Capture all decisions, actions, discussions from source material
  • Information fidelity: Preserve quotes, data points, technical terms exactly
  • Appropriate length: Longer memos acceptable when content requires it
  • Decision hierarchy: Rank by impact, not meeting sequence
  • Attribution: Attribute credibility-dependent info, skip for established facts
  • Action clarity: Include ownership and deadlines when specified
  • Characters exception: memo-template.md uses 🔴🟠🟡🟢 as functional priority indicators in the ACTION ITEMS table - these are permitted per template

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.