obsidian-meeting-prep
Prepares meeting materials by gathering context from Obsidian vault, enriching with research, and creating comprehensive meeting documentation. Generates both internal prep notes with background and external agendas with structure, all saved as properly linked markdown notes in vault.
What this skill does
# Meeting Preparation
Prepares you for meetings by gathering context from your Obsidian vault, enriching it with research, and creating comprehensive meeting materials. Generates internal prep notes for attendees and external-facing agendas for meetings.
## Quick Start
When asked to prepare for a meeting:
1. **Understand meeting context**: Gather meeting details and objectives
2. **Search vault**: Find related project notes, previous meetings, specs
3. **Read relevant notes**: Extract key context and background
4. **Enrich with research**: Add insights and additional context
5. **Create prep note**: Internal background document for attendees
6. **Create agenda**: External-facing meeting structure
7. **Link resources**: Connect all documents appropriately
## Meeting Prep Workflow
### Step 1: Gather meeting details
Collect essential information:
**Meeting basics:**
- Topic/Title
- Date and time
- Duration
- Location (physical/virtual)
**Participants:**
- Internal attendees
- External participants (clients, partners)
- Meeting owner/facilitator
**Meeting purpose:**
- Decision-making
- Status update
- Brainstorming
- Planning session
- Customer demo
- Problem-solving
- Knowledge sharing
**Context:**
- Related project or initiative
- Background/history
- Key topics to cover
- Desired outcomes
### Step 2: Search vault for context
**Project-related search:**
```bash
# Find project notes
find /path/to/vault/projects -name "*project-name*"
# Search project folder
grep -r "relevant term" /path/to/vault/projects/project-name/
```
**Previous meetings:**
```bash
# Find meeting notes
find /path/to/vault/meetings -name "*topic*" -o -name "*project*"
# Recent meetings
find /path/to/vault/meetings -name "*.md" -mtime -30
```
**Specifications and designs:**
```bash
# Find specs
grep -l "type: specification" /path/to/vault/**/*.md
# Find designs
find /path/to/vault -path "*/designs/*" -name "*.md"
```
**Tasks and issues:**
```bash
# Find related tasks
grep -l "project: \[\[project-name\]\]" /path/to/vault/tasks/*.md
# Find open issues
grep -l "status: open" /path/to/vault/**/*.md | grep -i "issue\|bug"
```
**Decision records:**
```bash
# Find decisions
grep -l "type: decision" /path/to/vault/**/*.md
# Recent decisions for project
grep -l "project.*project-name" /path/to/vault/decisions/*.md
```
**Dataview query:**
```dataview
TABLE type, updated, tags
FROM "projects" OR "meetings" OR "specs"
WHERE contains(file.name, "project-name")
OR contains(tags, "#project-tag")
SORT updated DESC
LIMIT 20
```
### Step 3: Read and extract context
For each relevant note:
```bash
# Read note
cat /path/to/vault/path/to/note.md
```
Extract:
- **Project status**: Current state and progress
- **Recent updates**: What changed recently
- **Decisions made**: Past decisions affecting meeting
- **Open questions**: Unresolved issues
- **Action items**: Outstanding tasks
- **Background**: Historical context
- **Stakeholder info**: Relevant people and roles
Organize information by relevance and importance.
### Step 4: Enrich with additional research
**Add context:**
- Industry best practices
- Technical background
- Competitive landscape
- Relevant frameworks or methodologies
**Anticipate questions:**
- What might participants ask?
- What context might be missing?
- What decisions need background?
**Identify discussion points:**
- Topics needing alignment
- Areas of potential disagreement
- Opportunities for input
### Step 5: Create internal prep note
Generate background document for internal attendees:
```bash
touch /path/to/vault/meetings/prep/meeting-name-prep.md
```
**Prep note structure:**
```markdown
---
type: meeting-prep
meeting: "[[meetings/meeting-name]]"
date: YYYY-MM-DD
project: "[[projects/project-name]]"
attendees:
- "[[people/person-1]]"
- "[[people/person-2]]"
tags:
- meeting-prep
- PROJECT-TAG
visibility: internal
---
# Meeting Prep: [Meeting Name]
> [!info] Meeting Details
> **Date**: YYYY-MM-DD HH:MM
> **Duration**: X hours
> **Location**: [Where/Link]
> **Attendees**: [[person-1]], [[person-2]]
## Purpose
Clear statement of meeting objectives.
## Background
### Project Context
Current state and relevant history.
- Status: [description]
- Recent changes: [what's new]
- Related: [[project-note]], [[spec-note]]
### Previous Discussions
Summary of relevant prior meetings.
- [[previous-meeting-1]]: Key outcomes
- [[previous-meeting-2]]: Decisions made
### Key Decisions
Important decisions affecting this meeting.
- [[decision-1]]: What was decided and why
- [[decision-2]]: Impact and implications
## Current Situation
### What's Working Well
Positive developments and progress.
### Challenges
Current obstacles and issues.
- Challenge 1: [[related-task]]
- Challenge 2: [[related-issue]]
### Open Questions
Unresolved issues needing discussion.
1. Question 1
2. Question 2
## Key Discussion Topics
### Topic 1: [Name]
**Context**: Background and why this matters
**Current state**: Where things stand
**Options**: Potential approaches
**Our position**: Recommended direction
### Topic 2: [Name]
[Continue for each major topic]
## Data & Metrics
Relevant numbers and trends.
- Metric 1: Current value (trend)
- Metric 2: Current value (trend)
## Stakeholder Perspectives
### Internal Team
- View 1: [[person-1]]'s perspective
- View 2: [[person-2]]'s perspective
### External Participants
- Client needs and concerns
- Partner requirements
## Potential Objections
Anticipated concerns and responses.
## Goals for This Meeting
What we want to achieve.
- [ ] Goal 1
- [ ] Goal 2
- [ ] Goal 3
## Materials to Reference
- [[spec-document]]
- [[design-mockups]]
- [[data-report]]
## Follow-Up Considerations
Potential next steps and actions.
## Quick Reference
Critical facts and figures for easy access.
```
See [reference/prep-note-template.md](reference/prep-note-template.md) for full template.
### Step 6: Create meeting agenda
Generate external-facing agenda document:
```bash
touch /path/to/vault/meetings/agenda/meeting-name-agenda.md
```
**Agenda structure:**
```markdown
---
type: meeting-agenda
date: YYYY-MM-DD
project: "[[projects/project-name]]"
duration: X hours
attendees:
- "[[people/internal-1]]"
- "External Person Name"
tags:
- agenda
- PROJECT-TAG
visibility: external
---
# Meeting Agenda: [Meeting Name]
**Date**: YYYY-MM-DD HH:MM
**Duration**: X hours
**Location**: [Where/Video link]
## Attendees
- Internal: [[person-1]], [[person-2]]
- External: Name 1, Name 2
## Meeting Objectives
1. Objective 1
2. Objective 2
3. Objective 3
## Agenda
### 1. Welcome & Introductions (5 min)
- Brief introductions
- Meeting objectives overview
### 2. Topic 1: [Name] (20 min)
**Objective**: What we want to accomplish
**Discussion points**:
- Point 1
- Point 2
- Point 3
**Desired outcome**: Decision/alignment on X
### 3. Topic 2: [Name] (15 min)
[Continue for each topic with time allocations]
### 4. Topic 3: [Name] (20 min)
...
### 5. Action Items & Next Steps (10 min)
- Summarize decisions
- Assign action items
- Schedule follow-up
## Background Materials
- [[Reference document 1]]
- [[Reference document 2]]
## Parking Lot
Topics for future discussion if time doesn't permit.
---
## Post-Meeting
Meeting notes: [[meetings/meeting-name-notes]]
Action items: [[tasks/meeting-name-actions]]
```
See [reference/agenda-template.md](reference/agenda-template.md) for full template.
### Step 7: Link and organize
**Create meeting folder:**
```
meetings/
└── meeting-name/
├── prep.md # Internal prep note
├── agenda.md # External agenda
└── notes.md # Post-meeting notes (placeholder)
```
**Link from project:**
```markdown
## Upcoming Meetings
- [[meetings/meeting-name/agenda]] - YYYY-MM-DD
```
**Link in prep note and agenda:**
```markdown
## Related
- Prep notes: [[meetings/meeting-name/prep]]
- Agenda: [[meetings/meeting-name/agenda]]
- Project: [[projects/project-name]]
- Spec: [[specs/featuRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.