// Analyze coding-agent session transcripts to discover patterns that could become AGENTS.md rules, skills, or prompt templates. Mines your usage history for automation opportunities across local coding-agent tools.
Reference for the features supported by presenterm, a terminal-based markdown slideshow tool. Use this skill whenever the user works with presenterm: building or editing a presenterm deck, asking which presenterm features/commands/themes exist, how slides/columns/code blocks/diagrams/images/themes/exports work, what a comment command does, or mentions "presenterm", "terminal slides", or "markdown presentation" rendered in the terminal. This skill documents what presenterm supports — it does not prescribe slide content, wording, or presentation design.
Convert an article, newsletter, or document into a short Kokoro-narrated audio read-up and upload it as a private episode to the user's "📥 Listen Later" Spotify show. ONLY trigger on explicit phrases like "listen later", "read-up", "save as audio for the commute", "add to my listen-later feed". Do NOT trigger on generic summarize, TTS, save-to-spotify, podcast, or cover-art requests — those route to the `save-to-spotify` skill.
Low-level provider web search via codex, claude-code, or openai-cli. Use only when user names ai-search/codex/claude/openai-cli search, compares providers, or wants native search; otherwise use web-search.
Default for web lookup/research/latest/current/URL/package/docs questions. Uses kagi→codex→claude-code→openai-cli→perplexity, escalating only if needed. Prefer this over provider skills unless user explicitly names kagi, perplexity, codex/claude-code/openai-cli, or ai-search.
Manage and deploy projects on exe.dev VMs. Use this whenever the user mentions exe.dev, exe.xyz hosts, `ssh exe.dev`, deploying Docker/GHCR apps to exe.dev, replacing or updating VMs, configuring exe.dev proxy/public access/custom domains, or setting up GitHub Actions/secrets/API tokens for exe.dev deployments.
Must read guide on creating/editing mermaid charts with valiation tools
| name | session-analyzer |
| description | Analyze coding-agent session transcripts to discover patterns that could become AGENTS.md rules, skills, or prompt templates. Mines your usage history for automation opportunities across local coding-agent tools. |
Extracts and analyzes your coding-agent session transcripts to find recurring patterns that could be automated.
# Extract transcripts for current directory
{baseDir}/analyze.js
# Extract transcripts for specific directory
{baseDir}/analyze.js /path/to/project
# Match multiple dirs by pattern (worktrees, variants, etc.)
{baseDir}/analyze.js --pattern orders-app
# Extract + analyze with helper agents / parallel analyzers
{baseDir}/analyze.js --analyze
# Pattern + analyze (finds all matching session dirs)
{baseDir}/analyze.js --pattern orders-app --analyze
# Custom output directory
{baseDir}/analyze.js --output ./my-analysis --analyze
--pattern to match multiple directories (e.g., worktrees, feature branches)Without --analyze:
session-transcripts/
├── session-transcripts-000.txt
├── session-transcripts-001.txt
└── ...
With --analyze:
session-transcripts/
├── session-transcripts-000.txt
├── session-transcripts-000.summary.txt # Pattern analysis
├── session-transcripts-001.txt
├── session-transcripts-001.summary.txt
└── FINAL-SUMMARY.txt # Aggregated findings
Install dependencies (run once):
cd {baseDir}
npm install
Adapted from badlogic/pi-mono gist