Meeting To Action
Productivitymeeting-to-actionMeeting To Action is an Agent Skill for productivity published in the InternLM/WildClawBench repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Convert meeting notes or transcripts into clear summaries, decisions, and action items with owners and due dates. Use when a user asks to turn a meeting recording, transcript, or notes into a follow-up plan.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/InternLM/WildClawBench/blob/HEAD/skills/3/meeting-to-action/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/meeting-to-action, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Meeting to Action
Goal
Transform meeting content into an actionable follow-up package with clear ownership and deadlines.
Best fit
- Use when the user provides a transcript or detailed notes.
- Use when the user needs action items, decisions, and next steps.
- Use when a concise recap email or message is required.
Not fit
- Avoid when the user wants tasks or calendar invites created automatically.
- Avoid when the transcript is missing and cannot be summarized reliably.
- Avoid when sensitive content should not be shared.
Quick orientation
references/overview.mdfor workflow and quality bar.references/auth.mdfor access and token handling.references/endpoints.mdfor optional integrations and templates.references/webhooks.mdfor async event handling.references/ux.mdfor intake questions and output formats.references/troubleshooting.mdfor common issues.references/safety.mdfor safety and privacy guardrails.
Required inputs
- Transcript or notes.
- Participant list and roles (if available).
- Preferred due date format and timezone.
- Audience for the recap (internal or external).
Expected output
- Short summary and key decisions.
- Action items with owners, due dates, and status.
- Open questions or risks.
- Draft follow-up message or email.
Operational notes
- Mark any inferred owners or due dates as tentative.
- Use clear, consistent action verbs.
- Deliver drafts only; do not send or update systems.
Security notes
- Treat meeting content as confidential.
- Avoid sharing outputs outside the user context.
Safe mode
- Summarize and draft action items only.
- Do not create tasks, invites, or messages automatically.
Sensitive ops
- Creating tasks, calendar events, or sending messages is out of scope.