Meetings

Build a personal meeting system for capturing notes, preparing agendas, and never missing follow-ups.

Security Scan

The skill's files and runtime instructions are coherent with a personal meetings/notes system: it stores notes under ~/meetings, extracts items from user-provided transcripts, and prepares meeting prep — there are no unexpected credentials, installs, or code files requested.

Purpose & 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.

Core Behavior

• User shares transcript/audio → extract key points and action items
• User has upcoming meeting → help prepare with context
• Proactively alert about meetings and pending follow-ups
• Create ~/meetings/ as workspace

File Structure

~/meetings/
├── upcoming/
│   └── 2024-02-15-client-review.md
├── past/
│   └── 2024/
├── recurring/
│   └── weekly-standup.md
├── people/
│   └── sarah-chen.md
└── follow-ups.md

After Meeting Capture

User pastes transcript or describes meeting:

# 2024-02-11-product-sync.md
## Meeting
Product Sync with Engineering

## Date
February 11, 2024, 2:00 PM

## Attendees
Sarah, Mike, Lisa

## Key Points
- Launch pushed to March 15 (was March 1)
- Need additional QA resources
- Design approved, no changes

## Decisions Made
- Hire contractor for QA
- Keep current feature scope

## Action Items
- [ ] Sarah: Send contractor requirements by Wed
- [ ] Mike: Update timeline in Jira
- [ ] Me: Notify stakeholders of new date

## Open Questions
- Budget approval for contractor?

## Next Meeting
Feb 18, same time

Quick Capture

From voice or brief text: "Just had product sync. Launch moved to March 15. Sarah handling QA contractor. I need to notify stakeholders."

→ Auto-organize into structured format → Extract action items → Flag follow-ups

Pre-Meeting Prep

Before scheduled meeting, surface:

# Prep: Client Review (Tomorrow 10am)
## Context
- Last met: Jan 15
- Project: Website redesign
- Status: Phase 2, 60% complete

## From Last Meeting
- They wanted mobile mockups — did we deliver?
- Budget concern raised — was it resolved?

## Open Action Items
- [ ] Send revised timeline (was due last week)

## Their Recent Activity
- Sarah emailed about invoice Tuesday

## Suggested Agenda
1. Phase 2 progress update
2. Mobile mockups review
3. Timeline discussion
4. Budget clarification

Follow-ups Tracking

# follow-ups.md
## Overdue
- [ ] Send stakeholder update (due Feb 10) — Product Sync
- [ ] Review contract terms (due Feb 8) — Legal Call

## Due This Week
- [ ] Contractor requirements to Sarah (Wed)
- [ ] Timeline update (Fri)

## Waiting On Others
- Mike: Jira update
- Lisa: Design assets

Recurring Meetings

# recurring/weekly-standup.md
## Meeting
Weekly Team Standup

## Schedule
Mondays 9:00 AM

## Usual Attendees
Full product team

## Running Notes
### Feb 11
- Sprint on track
- John out next week

### Feb 4
- Delayed by design review
- Added Lisa to project

People Context

# people/sarah-chen.md
## Role
VP Product, Acme Corp

## Meeting History
- Feb 11: Product sync — discussed launch delay
- Jan 15: Kickoff — aligned on scope

## Communication Style
- Prefers concise updates
- Wants data to back decisions

## Notes
- Reports to CEO directly
- Budget authority up to $50k

Proactive Alerts

• "Meeting with Sarah in 2 hours — prep ready"
• "3 overdue follow-ups from last week"
• "You promised Mike an update by today"
• "Recurring standup in 30 minutes"

What To Extract

From transcripts/audio:

• Decisions made
• Action items (who, what, when)
• Open questions
• Key discussion points
• Next meeting date

What To Surface

• Prep notes before meetings
• Overdue and upcoming follow-ups
• Context on attendees
• Promises you made

Progressive Enhancement

• Start: capture notes after meetings
• Track action items and follow-ups
• Add prep for important meetings
• Build context on recurring attendees

What NOT To Do

• Let action items disappear
• Go into meetings without context
• Forget promises made
• Miss recurring meeting patterns