meeting-briefing-action-item-best-practices
Sub-skill of meeting-briefing: Action Item Best Practices (+2).
Best use case
meeting-briefing-action-item-best-practices is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of meeting-briefing: Action Item Best Practices (+2).
Teams using meeting-briefing-action-item-best-practices should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/action-item-best-practices/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How meeting-briefing-action-item-best-practices Compares
| Feature / Agent | meeting-briefing-action-item-best-practices | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of meeting-briefing: Action Item Best Practices (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Action Item Best Practices (+2) ## Action Item Best Practices - **Be specific**: "Send redline of Section 4.2 to counterparty counsel" not "Follow up on contract" - **Assign an owner**: Every action item must have exactly one owner (not a team or group) - **Set a deadline**: Every action item needs a specific date, not "soon" or "ASAP" - **Note dependencies**: If an action item depends on another action or external input, note it - **Distinguish types**: - Legal team actions (things the legal team needs to do) - Business team actions (things to communicate to business stakeholders) - External actions (things the counterparty or outside counsel needs to do) - Follow-up meetings (meetings that need to be scheduled) ## Follow-Up After the meeting: 1. **Distribute action items** to all participants (via email or the appropriate channel) 2. **Set calendar reminders** for deadlines 3. **Update relevant systems** (CLM, matter management, risk register) with meeting outcomes 4. **File meeting notes** in the appropriate document repository 5. **Flag urgent items** that need immediate attention ## Tracking Cadence - **High priority items**: Check daily until completed - **Medium priority items**: Check at next team sync or weekly review - **Low priority items**: Check at next scheduled meeting or monthly review - **Overdue items**: Escalate to the owner and their manager; flag in next relevant meeting
Related Skills
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
context-compaction-handoff
Guardrails for resuming work after context compaction or transcript handoff blocks; prioritize the latest real user request over stale summarized tasks and verify before answering.
portable-baseline-pattern-extraction
Extract and separate portable baseline config from machine-specific overrides in multi-environment projects
multi-format-transaction-parser
Parse and consolidate financial transaction data across multiple CSV formats and years
github-actions-trigger-and-shell-gotchas
Prevent false verification gaps in GitHub Actions by checking push path filters, shell compatibility, and shared CI environment failures before concluding a workflow fix worked or failed.
github-actions-cross-platform-validation-gotchas
Execution-time GitHub Actions pitfalls discovered while fixing cross-platform CI workflows — path-filter non-triggers, Windows shell parsing mismatches, and job-scoped validation.
github-interaction-limits-hardening
Lock down public GitHub repositories so only collaborators can interact with issues, PRs, comments, discussions, and other user-generated surfaces using repository interaction limits; includes expiry verification and renewal handling.
diffraction-analysis
Master skill for hydrodynamic diffraction analysis - AQWA, OrcaWave, and BEMRosetta integration
doc-extraction-naval-architecture
Layer 3 domain sub-skill for extracting naval architecture data from SNAME PNA, IMO stability codes, IACS structural rules, and classification society guidelines. Provides detection heuristics for stability constants, resistance equations, hull form coefficients, hydrostatic curves, IMO stability criteria, and structural scantling tables. type: reference
doc-extraction-drilling-riser
Layer 3 domain sub-skill for extracting drilling riser data from API RP 16Q, DNV-RP-C205, and riser analysis reports. Provides detection heuristics for VIV parameters, kill/choke line specs, and BOP stack configurations. type: reference
doc-extraction
Classify and extract structured content from engineering documents using a 3-layer taxonomy: generic content types, engineering patterns, and domain sub-skills. Use when ingesting standards, reports, or technical manuals into structured data for downstream analysis. type: reference