coaching-session-summarizer
This skill should be used to summarize coaching or therapy session transcripts after a Fathom/Granola sync. The agent analyzes the transcript itself (no API key, runs on the subscription) and appends key insights, decisions, action items, and trail connections. Supports quick extraction or deep analysis with cross-session pattern detection.
What this skill does
# Coaching Session Summarizer ## Overview Analyzes a coaching/therapy session transcript and appends a structured summary (key insights, decisions, action items, deep analysis, connected trails) to the note. **The agent (Claude Code) performs the analysis directly** — reading the transcript and writing the summary in this session. There is **no Anthropic API call and no billing**; it runs entirely on the active subscription. A legacy API-based script is kept only as a headless fallback (see bottom). ## When to Use This Skill - A new Fathom/Granola transcript was synced to the vault (coaching or therapy) - User asks to summarize/analyze a session (`/summarize-session [file]` or similar) - After `calendar-sync` or a Granola export, when a new `*-coaching.md`, `*-therapy.md`, or `*-session.md` file appears — offer to summarize it ## Workflow (agent-driven — default) Do this in-session with native tools. No API key required. ### Step 1 — Gather context Run the deterministic helper to get the transcript text, previous sessions, and the trail list in one shot: ```bash python3 ~/.claude/skills/coaching-session-summarizer/scripts/gather_context.py \ <transcript-file> --vault ~/Brains/brain ``` It prints: - **Previous sessions** with the same participant (paths) — `Read` these only in deep mode, for cross-session pattern detection - **Available trails** — pick 2–4 most relevant to link - **Session content** — the summary + transcript to analyze (any prior AI-Generated Summary is stripped so re-runs stay clean) Pass `--participant <name-slug>` if the filename doesn't encode the person (e.g. Granola exports titled by topic): `--participant gleb-kalinin`. ### Step 2 — Analyze Read the session content and extract, in the analytical voice of a session analyst (objective, using the speaker's authentic language where it matters): - **Key Insights** — 3–5 main realizations / breakthroughs / observations - **Decisions Made** — concrete choices or commitments - **Action Items** — specific next steps; prefix time-sensitive ones with `[URGENT]` and scheduling items with `[SCHEDULING]` - **Session Themes** — 2–3 recurring topics or patterns **Deep mode** (default for therapy and milestone sessions) — also `Read` the previous sessions and add: - **Pattern Detection** — themes recurring across sessions - **Progress Assessment** — movement on earlier commitments - **Energy/Motivation Markers** — shifts in energy, resistance, affect - **Potential Obstacles** — what might block progress ### Step 3 — Append with Edit Append the summary to the **end** of the transcript file using `Edit` (never overwrite existing content). Match this exact structure: ```markdown ## AI-Generated Summary *Generated: YYYY-MM-DD* ### Key Insights - ... ### Decisions Made - ... ### Action Items - [URGENT] ... - ... ### Session Themes - ... ## Deep Analysis - **Pattern Detection**: ... - **Progress Assessment**: ... - **Energy/Motivation Markers**: ... - **Potential Obstacles**: ... ## Connected Trails - [[Trails/Trail - <Name>|<Name>]] - [[Trails/Trail - <Name>|<Name>]] ``` Use the current date (`date +%Y-%m-%d`) in the Generated line. Omit the Deep Analysis section in quick mode. Verify trail link names against the printed trail list — case and exact wording matter for Obsidian links. ## Modes - **quick** — Key Insights, Decisions, Action Items, Themes. Skip Deep Analysis and previous-session reads. - **deep** (recommended for therapy / milestones) — everything, including reading previous sessions for pattern detection. ## Integration with Sync After `calendar-sync` or a Granola/Fathom export, check for new session files (`*-coaching.md`, `*-therapy.md`, `*-session.md`). If one appears, offer: "New session detected — summarize now?" Default to deep mode for therapy. ## Notes - Preserves the original transcript intact; the summary is always appended. - Trail linking requires the `Trails/` directory in the vault root. - Cross-session comparison works best with consistent naming: `YYYYMMDD-name-coaching.md` / `YYYYMMDD-name-therapy.md`. - Re-running is safe: `gather_context.py` strips any prior AI-Generated Summary before printing, so the agent analyzes only the raw session. (Delete the old `## AI-Generated Summary` block from the file before re-appending if you want to replace rather than stack summaries.) ## Resources ### scripts/ - **gather_context.py** — *(default path)* deterministic context gatherer, no API. Prints transcript text + previous sessions + trail list for the agent to analyze in-session. - **summarize_session.py** — *legacy / headless fallback.* Calls the Anthropic API directly (model via `SUMMARIZER_MODEL`, default `claude-sonnet-4-6`) and bills a funded `ANTHROPIC_API_KEY`. Use only when no interactive agent is available (e.g. cron). Exits with a clear message if the key has no credit.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.