Install
$ agentstack add skill-enkrateialucca-skills-meeting-recording-to-notes ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Meeting Recording → Notes
Take a meeting recording (local file, downloaded file, or the latest file in a recordings folder) and produce a single structured markdown note the user can act on — not a wall-of-text transcript.
Configuration
Two locations drive this skill. Resolve them in this order: explicit user instruction → environment variable → default.
| Setting | Env var | Default | |---|---|---| | Recordings folder | MEETING_RECORDINGS_DIR | ~/Movies/Meet Recordings | | Notes destination | MEETING_NOTES_DIR | ~/notes/meetings |
If the user keeps recordings in a cloud-synced folder (Google Drive, Dropbox), the synced local path works the same way.
Workflow
1. Locate the recording
- If the user passed a file path or URL, use that. Download URLs to a temp
directory first.
- If the user said "my latest meeting" (or gave no file), pick the most
recently modified audio/video file in the recordings folder: ls -t "$MEETING_RECORDINGS_DIR" | head -5 — confirm the pick with the user only if the top file is ambiguous (e.g. two files within a few minutes of each other).
2. Transcribe
Prefer whatever transcription tool is already on the machine, in this order:
- A local
transcribeCLI if one exists (command -v transcribe) whisper/mlx_whisper(extract audio first if needed:
ffmpeg -i in.mp4 -vn -acodec libmp3lame out.mp3)
- If nothing is installed, ask before installing anything.
Keep the raw transcript in a temp file — do not paste it into the chat.
3. Write the note
One markdown file, named YYYY-MM-DD .md (infer the topic from the transcript, date from the file's timestamp). Structure:
# —
## Summary
2–4 sentences. What was this meeting and what came out of it.
## Key points
- The substance, grouped by theme — not a chronological play-by-play.
## Decisions
- Each decision on one line, with who made the call if identifiable.
## Action items
- [ ] — owner: , due:
## Open questions
- Anything raised but not resolved.
## Files & links mentioned
- Only if any came up; omit the section otherwise.
Rules:
- Action items must be checkboxes with an owner. If no owner was stated, mark
it owner: ? rather than guessing.
- Omit empty sections entirely — a note full of "N/A" headers is noise.
- Keep speaker attribution only where it matters (decisions, disagreements).
4. Report back
Output the full path of the saved note and a one-line summary in the chat. Nothing else — the note is the deliverable.
Cleanup
Delete temp audio extractions and downloaded files when done. Never delete the original recording.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: EnkrateiaLucca
- Source: EnkrateiaLucca/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.