Meeting
v2.0.0A Meeting Execution Operator. Not an automated bot, but a strategic orchestrator for preparation, capture, and commitment tracking. Operates on a "Draft-Firs...
⭐ 0· 351·2 current·2 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/description (meeting orchestration, drafts-first, tracking via host connectors) match the SKILL.md and skill.json capabilities. It reasonably relies on the host platform's connectors rather than asking for its own credentials.
Instruction Scope
SKILL.md instructs the agent to use calendar context, user-provided fragments, and existing transcripts; it explicitly forbids autonomous recording and automatic distribution without user confirmation. The instructions do not ask for unrelated files, system paths, or hidden exfiltration.
Install Mechanism
No install spec and no code files—this is instruction-only, so nothing is downloaded or written to disk. This is proportionate for an orchestration/advisory skill.
Credentials
The skill declares no required environment variables or credentials, which is coherent because it depends on the host's existing connectors. However, the exact connector permissions (calendar, tasks, email access) are not enumerated here — consumers should verify what host-scoped permissions will be granted when they enable the connector integration.
Persistence & Privilege
The skill stores meeting intelligence in the agent's private memory and uses host task systems for persistent tracking when available. always:false (no forced inclusion) and normal autonomous-invocation settings are used. Users should confirm agent memory retention/visibility policies and connector write permissions before enabling distribution features.
Assessment
This skill appears internally consistent and does not request extra credentials or perform hidden installs. Before enabling it, check: (1) what host connector permissions will be granted (calendar read, task create, email send) and only approve scopes you accept; (2) your agent's memory retention and who can read stored meeting intelligence; (3) that distribution actions are always drafted for your explicit approval (test the 'Distribute' flow with a harmless meeting); and (4) the skill publisher/source (skill.json lists a GitHub URL but registry 'source' was unknown) if you want provenance. If those checks are satisfactory, the skill's behavior matches its description.Like a lobster shell, security has layers — review code before you run it.
action-itemsvk97ajz9rzqjnqy91a2sev8kkvh82kxmnlatestvk976yfjyymv5xt98g7k68yvzw182qbdnmeetingvk97ajz9rzqjnqy91a2sev8kkvh82kxmnnotesvk97ajz9rzqjnqy91a2sev8kkvh82kxmnproductivityvk97ajz9rzqjnqy91a2sev8kkvh82kxmnworkvk97ajz9rzqjnqy91a2sev8kkvh82kxmn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.