Explore skills

Trigger on "what did I decide about X", "why did I pick X", "did I choose X over Y", "what was my call on X", "ADR for X", "is there a decision on X", "have I picked between X and Y". Use when the user wants to recall a settled past decision, not make a new one. NOT for fresh tradeoff analysis (route to Claude or timeln-find).

Trigger on "search my memory", "look up in my memory", "recall from my notes", "second brain", "thinking partner", "what should I learn today", "connect my ideas", "show my knowledge gaps", "build a knowledge graph", "what's in my brain", or any question prefixed with "based on my past data" / "from my knowledge graph". Use for open-ended search, synthesis, and exploration over the user's Timeln m

Trigger on "plan my saves", "plan my week from Timeln", "cascade my last X days", "prioritize my recent saves", "what should I do with my saves", "turn my saves into actions", "run the framework cascade", "eisenhower my saves". Use when the user wants to convert recent Timeln captures into a ranked action plan. NOT for quick recall (use timeln-quickly) or open-ended exploration (use timeln-find).

Trigger on "weekly podcast", "timeln podcast", "podcast from my saves", "turn my saves into audio", "listen to my saves". Produces one Timeln Podcast MP3 from Timeln saves (default: last 7 days). Full pipeline: pull, connect, TTS script, local render. NOT for text-only search (timeln-find) or action plans (timeln-plan).

Trigger on "have I shipped X", "have I built X before", "show me proof of X", "case study for X", "past work on X", "what have I delivered on X", "who have I done X for". Use when the user needs proof of actually-shipped work mid-pitch or in a proposal. NOT for past learning (use timeln-find) or past failures (use timeln-warned).

Trigger on "what bit me on X", "have I been burned by X", "gotchas with X", "what went wrong last time with X", "warn me about X", "any retros on X", "past incidents with X". Use when the user wants to sanity-check an approach against their own failure history. NOT for general pitfalls (ask Claude directly) or past decisions (use timeln-decided).

Remove dead code, fix duplication, and optimize imports in modified files

Configure deployment script and run it, verifying it succeeds

Create or update the data flow architecture document (docs/pages/data-flow.md).

Update stale documentation and comments to match current code

List your GitHub-owned local clones under PROJECTS_ROOT that have pending work (uncommitted changes, unpushed commits, or inbound remote commits), with branch, counts, age of oldest pending work, and a per-repo summary. Each run fetches every repo's origin in parallel so the counts reflect the current remote. TRIGGER when: user asks "/github-status", wants a cross-project overview of their repos,

Complete Claude Code environment: global guidelines, skills, hooks, settings, version-controlled memory and learnings, and shared git config