meeting-analysislisted
Install: claude install-skill sergeiwallace/skills
# meeting-analysis
Turn whatever subset of meeting artifacts exists into a **citation-bearing analysis doc** that a
reader can audit against its sources.
**Usage:**
- `/meeting-analysis <zip-or-directory> [--author NAME] [--date YYYY-MM-DD] [--series NAME] [--kind recording-analysis|standup-update]`
- `/meeting-analysis --retrieve <meeting-name> [--date YYYY-MM-DD] [--time HH:MM]`
- `/meeting-analysis --retrieve --chat "<chat title>" --date YYYY-MM-DD [--time HH:MM]`
## Step 0, only with --retrieve: land the sources first
`--retrieve` is optional. It fetches the meeting's artefacts with the `teams` skill's `meeting`
command from this same repository, then continues at Step 1 with the directory it landed. Without
the `teams` skill, or for a meeting held on another platform, export the sources yourself and
start at Step 1. The command, its named-meetings config and its rules for picking an instance are
in the `teams` skill's SKILL.md; the short form:
```bash
TEAMS_DIR="$(dirname "$(realpath "${CLAUDE_SKILL_DIR}")")/teams"
uv run --script "$TEAMS_DIR/scripts/meeting.py" <meeting-name> [--date D] [--time HH:MM] --json
```
A meeting with no config entry is landed ad hoc with `--chat "<exact chat title>" --date
YYYY-MM-DD` and goes into its own `docs/meetings/<slug>-<date>/` directory
([Step 2](#step-2-the-directory-shape-is-a-convention-not-a-preference)).
**Check the sign-in first, with a read that costs nothing** (the teams skill's cheapest read, for
example a chat looku