From obsidian
Clean up rough meeting notes, extract action items, create tasks, and write summary
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian:meeting-cleanupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps clean up rough meeting notes after a meeting.
This skill helps clean up rough meeting notes after a meeting.
Follow these steps:
READ the meeting note file (user should provide path or it should be clear from context)
REORGANIZE rough discussion notes into clear sections:
EXTRACT action items and create tasks:
- [ ] task 📅 YYYY-MM-DD #task #tagsWRITE a summary (2-3 sentences):
ASK clarifying questions if:
DON'T:
After cleanup, show the user what you changed and ask if they want any adjustments.
npx claudepluginhub gavinsdavies/obsidian-skills --plugin obsidianGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.