Meetings
v1.0.0Build a personal meeting system for capturing notes, preparing agendas, and never missing follow-ups.
⭐ 2· 1k·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (meeting notes, agendas, follow-ups) align with the SKILL.md instructions: creating a ~/meetings workspace, extracting decisions/action items from transcripts, preparing prep notes, and tracking follow-ups. The skill does not request unrelated credentials, binaries, or config paths.
Instruction Scope
Instructions are narrowly focused on capturing transcripts/text, organizing notes, extracting action items, and surfacing prep/follow-ups. Two ambiguities to be aware of: (1) 'Proactively alert about meetings' and 'User has upcoming meeting' imply the skill must discover scheduled meetings (calendar access or an explicit upload), but SKILL.md does not explain how meetings are discovered or how alerts will be delivered. (2) It references processing 'voice' input but provides no guidance whether audio is processed locally or sent to an external service. The instructions do not ask the agent to read unrelated system files or env vars.
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk: nothing will be downloaded or written by an installer beyond what the agent chooses to do at runtime (e.g., creating ~/meetings).
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate to the described functionality as long as the user explicitly provides transcripts and any calendar data. If the skill were to perform proactive alerts by reading a calendar or email, it would require additional permissions/credentials which are not declared here.
Persistence & Privilege
always is false (normal). The skill will create and store files under ~/meetings/ per its instructions — persistent local data storage is expected for this purpose. The skill can be invoked autonomously by the agent (platform default); if you enable autonomous behavior, expect it could generate scheduled alerts or modify files in ~/meetings without a direct prompt. The SKILL.md does not request system-wide settings or modify other skills.
Assessment
This skill appears coherent for meeting notes and follow-ups and does not ask for credentials or install code. Before enabling it: (1) Confirm how it discovers upcoming meetings — will you grant calendar access or will you supply events manually? (2) Ask where audio is processed (locally vs. external service) and whether transcripts are uploaded anywhere. (3) Be aware it will create and store files under ~/meetings/ (check retention and deletion procedures). (4) If you enable autonomous invocation, expect it could produce proactive alerts and write to the ~/meetings workspace without prompting. If those behaviours are acceptable and you get clarity on calendar/audio handling, installing is reasonable.Like a lobster shell, security has layers — review code before you run it.
latestvk974bvvz8ejp3qxf3skajtf9y580ygak
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🤝 Clawdis
OSLinux · macOS · Windows