Meeting Assistant

v1.0.1

AI meeting partner for solopreneurs and professionals. Generates pre-meeting briefs from your notes and context, captures structured meeting notes during the...

0· 230·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (meeting briefs, notes, action items, follow-ups) match the SKILL.md instructions which only operate on local meetings/ files and coordinate with other agent skills (project-tracker, crm, research-assistant). No unrelated credentials, binaries, or installs are requested.
Instruction Scope
Instructions direct the agent to create and update a meetings/ directory, initialize meeting-log.md and open-actions.md, scan meeting files for metrics and overdue items, draft follow-ups (explicitly marked as drafts), and chain to other agent skills for research. This file I/O and directory scanning are expected for a meeting assistant, but you should be aware the agent will read and write those local files and scan the meetings/ hierarchy if enabled.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by an install process beyond the agent's normal file creation when following the instructions.
Credentials
The skill declares no environment variables, no credentials, and no config paths. References to integrations (CRM, project-tracker, research-assistant) are plausible but those integrations are external and not requested here — you should verify those other skills separately if you enable chains.
Persistence & Privilege
always:false (normal). The setup asks you to add standing instructions to AGENTS.md and to create meetings/ files, which makes the behavior persistent only if you follow those steps. The skill suggests heartbeat-like periodic checks; if you enable autonomous agent invocation or scheduled heartbeats elsewhere, the agent could routinely scan meetings/ and surface overdue items — review those settings before enabling autonomous runs.
Scan Findings in Context
[no_findings] expected: The scanner found no code files or suspicious patterns. This is expected for an instruction-only skill; the SKILL.md itself is the runtime instruction surface and has been reviewed above.
Assessment
This skill is coherent with its stated meeting-management purpose, but before installing: (1) review and approve the AGENTS.md additions you paste in — they give the agent standing rules about meetings; (2) check and control which directory the agent can write to (meetings/) and back up any existing files there; (3) confirm you want the agent to scan meeting files automatically (heartbeat behavior) and consider disabling autonomous invocation if you prefer manual runs; (4) when enabling integrated chains (research-assistant, CRM, project-tracker), review those skills separately because they may request network access or credentials; (5) follow the explicit guidance to review follow-up email drafts before sending and never enable automatic sending unless you trust the automation fully.

Like a lobster shell, security has layers — review code before you run it.

latestvk9775wk4we2xgkdrgtvc4q22tn82hqgy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments