This skill should be used when the user or another agent asks to "create a handoff", "write a handoff payload", "generate a handoff for another agent", "build a context handoff", "configure a tmux relay", "hand off this work", "hand off to another claude", "relay this to another agent", "send context to a teammate", "transfer this to another pane", "pass this to <agent-name>", "/handoff", or otherwise wants to transfer structured work context from this Claude session to another Claude — whether a teammate spawned via SendMessage, a Claude process running in a separate tmux pane, or via clipboard for human-mediated handoff. Do NOT use for tmux pane management generally (use terminal-guru) or for end-of-session file-based recap intended for a future fresh Claude session unrelated to any live recipient (that is a different problem domain).
This skill should be used when the user asks to "configure mise.toml", "create a mise task", "set up tool versions", "manage environments with mise", "debug mise config", "task_config includes", "mise task DRY", "mise profiles", "mise env not loading", "create mise run command", or needs help with mise (jdx/mise) for tool versioning, environment variables, or task automation. Also trigger on mentions of mise.toml, .miserc.toml, mise run, mise env, mise tasks, mise profiles, task_config, or exec() in env. Do NOT use for shell configuration or function generation (use zsh-dev instead). Do NOT use for sesh/tmux session management (use environment-composition instead). Do NOT use for signal handling or logging (use signals-monitoring instead). Mise + sesh integration questions should route here for the mise side and environment-composition for the sesh side.
This skill should be used PROACTIVELY to "create a friction report", "check for broken tooling", or "run a friction check" when you hit confusing errors, bad docs, missing prereqs, broken tools, misleading skills, flaky tests, auth/MCP failures, or any "this should've been easier" moment. Also trigger when the user says "file an issue", "report this friction", "log this feedback", "wtf", or "this should be easier". Do NOT use for fixing the friction itself (use skillsmith or agentsmith instead).
This skill should be used when querying OmniFocus data, managing tasks, running GTD diagnostics, or configuring perspectives. Triggers when user asks "show tasks", "overdue items", "check inbox", "stalled projects", "waiting for list", "someday maybe", "GTD health check", "AI Agent tasks", "publish plan to OmniFocus", "set up perspectives", "perspective inventory", "configure perspective", "quick stats", or "missing perspectives". Also triggers when the user pastes an `omnifocus://` URL — parse the entity type and ID from the URL, then use `/ofo:info <url>` to look it up directly. Do NOT trigger for: "create OmniFocus plugin" (use omnifocus-generator skill), "analyze my system" or "discover my patterns" (use attache-analyst skill), pure GTD methodology questions (use gtd-coach skill).
This skill should be used when analyzing OmniFocus system structure, discovering workflow patterns, running AI-enhanced GTD coaching, or learning the user's tool stack. Triggers when user asks "analyze my OmniFocus", "discover my system", "what's my structure", "AI coaching", "project health analysis", "system insights", "learn my workflow", "understand my patterns", "suggest improvements", "what tools do I use", or "update my tool stack". Do NOT trigger for: "show tasks" or "check inbox" (use omnifocus-core), "create OmniFocus plugin" (use omnifocus-generator), "what makes a good next action" (use gtd-coach for pure methodology). This skill is read-only against OmniFocus. It discovers patterns, infers structure, and persists learned insights via the Attache preferenceManager. It can read and update vault tool notes (status, usage patterns) via the archivist agent.
This skill should be used when creating OmniFocus Automation plugins (.omnifocusjs), JXA scripts for OmniFocus, or OmniFocus automation artifacts. Triggers when user asks "create OmniFocus plugin", "generate OmniFocus plugin", "build .omnifocusjs", "build OmniFocus automation", "build JXA script for OmniFocus", "create OmniFocus action", or "make OmniFocus plugin". Do NOT trigger for: "create a plugin" without OmniFocus context (ask for clarification), "create a Claude plugin" (use plugin-dev skill), "install a plugin" (use omnifocus-core skill), "show tasks" or "analyze" (use omnifocus-core skill). WORKFLOW: 1) CLASSIFY query vs plugin 2) SELECT format (solitary/solitary-fm/bundle/solitary-library) 3) COMPOSE from libraries 4) GENERATE via `node scripts/generate_plugin.js` - NEVER Write/Edit tools 5) VALIDATE via `bash scripts/validate-plugin.sh` 6) TEST in OmniFocus.
This skill should be used when users need GTD methodology coaching on productivity, workflow, or task management systems. Triggers when user asks "create a next action", "check my GTD system", "analyze my projects", "improve my workflow", "weekly review", "inbox zero", "someday maybe", or "GTD coaching". For OmniFocus-specific automation, use the omnifocus-core skill instead.
This skill should be used when users ask to "create Obsidian templates", "create a template", "create a .base file", "design Bases queries", "set up vault structure", "configure Templater workflows", "set up daily weekly monthly rollup", "analyze vault organization", "configure Excalibrain", "build temporal rollup system", "update frontmatter schema", "fix vault organization", or "add metadata to templates". Architects new PKM structures and provides guidance for Templater, Bases, Chronos, and QuickAdd patterns. Particularly useful for creating automatic note organization systems, temporal rollup structures (daily to yearly), and maintaining job-agnostic organizational patterns. Do NOT use for maintaining or evolving existing vault content (metadata drift, duplicate notes, merges, link redirects, canvas generation — use vault-curator for those).