Meeting To Action
v1.0.0Convert 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.
⭐ 1· 2.8k·7 current·7 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the runtime instructions and supporting docs: the skill only requires a transcript/notes and optional participant/context information. There are no unexpected credentials, binaries, or config paths requested that would be unrelated to summarization.
Instruction Scope
SKILL.md and referenced docs confine the agent to reading transcripts/notes, extracting decisions and action items, and producing drafts. The docs explicitly forbid sending messages, creating tasks/invites automatically, or publishing changes without explicit user confirmation. No instructions ask the agent to read unrelated system files or exfiltrate data.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute. That minimizes on-disk risk and there are no download URLs or package installs to review.
Credentials
The skill declares no required environment variables, credentials, or config paths. References to optional integrations (transcription services, calendar/task APIs, webhooks) are explicitly gated behind user approval and draft-only operations, which is proportionate for an integration-capable summarization skill.
Persistence & Privilege
The skill does not request always: true, does not attempt to modify other skills or system-wide configs, and is user-invocable only. Autonomous invocation is allowed by platform default and is not combined with other concerning privileges here.
Assessment
This skill appears internally consistent and safe to install from a permissions perspective, but consider these operational cautions before using it: only feed transcripts you are allowed to share (they may contain confidential data), confirm any requested integrations (calendar/task APIs or webhooks) explicitly before authorizing them, and verify owners/due dates the skill infers before acting on them. If you plan to connect real calendars or task systems, require explicit user approval and audit tokens/permissions granted at that time.Like a lobster shell, security has layers — review code before you run it.
latestvk975k1s8ww7xahnkfz2dk9mnb180vg7s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.