Loading...
Loading...
Found 251 Skills
Create handoff documentation from One Horizon task data including completed/planned tasks, initiatives, and blockers. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.
Report a bug or feature request in One Horizon. Use when asked "I found a bug", "track this issue", "log this defect", "log this feature request", "capture this product ask", or "track this enhancement". Requires One Horizon MCP.
Monitor background processes from Claude Code using sentinel files, heartbeat liveness, and subagent polling. Best practices and anti-patterns for autonomous loops that need to kick off work, detect completion/failure/hang/timeout, and resume the main context without wasting tokens. TRIGGERS - monitor background process, sentinel file, heartbeat monitoring, process supervision, agentic loop monitor, background task health, detect hung process, poll for completion, watchdog pattern, process liveness, monitor long-running task, agent poll loop, circuit breaker pattern.
Generate README documentation writing plans and tasks. Use when the user wants to create README files for packages, plan documentation writing, or generate doc tasks for manual or LLM authoring.
Capture idea or task as todo from current conversation context
Remove a future phase from roadmap and renumber subsequent phases
Todoist integration. Manage Projects, Users, Labels, Filters, Sections, Comments. Use when the user wants to interact with Todoist data.
Plan how to slice a non-trivial coding task across parallel subagents. Returns a dispatch plan (file assignments, dependencies, output-format contracts) — the main Agent then executes it with the Agent tool + `isolation: "worktree"`. Invoke only when work justifies multi-agent overhead: (a) greenfield 0→1 across multiple independent modules, (b) change touches ≥3 modules, or (c) ≥5 files each with >50 lines of diff. Small changes write inline.
Auto-activates when working with implementation plans. Triggers on "continue the plan", "next task", "what's the plan status", "run task 2.1", or when user references plans/*.plan.md files. Not for creating plans - use /superplan command for that.
Use this skill to turn a raw user request into a structured, model-agnostic task brief before execution, and — when the brief survives confirmation — to be the sole entry point that creates a task directory at `.agents/tasks/<task-id>/`. Invoke whenever the request is complex, multi-step, cross-domain, ambiguous, or will be handed off to another model or agent. Also trigger when the user says things like 'help me figure out what I need', 'I'm not sure how to ask this', 'I want to do X but I don't know where to start', 'take this and make it clearer', or when the task mixes multiple goals or domains. Do NOT trigger for simple one-line requests with clear intent (e.g., 'fix the typo on line 42', 'rename this variable').
Append-only task record convention for Loom. Use when reading or writing per-task records under `.agents/tasks/<task-id>/`, when another skill needs to log a lifecycle milestone (saved, decision, readiness, blocker, done), when the user asks about an existing task's status or progress, or when checking task records for drift via the linter. Do NOT trigger for creating new tasks (that is `task-brief`'s job), for general docs/planning unrelated to a task directory, or for historical questions about the retired `task-state-management` system.
Guide for setting up and using the Sync with Todoist Plugin for Obsidian (v2.6.0). Use this skill whenever the user asks about integrating Todoist with Obsidian, installing the Todoist plugin, creating query blocks to display tasks in Obsidian notes, adding tasks from Obsidian to Todoist, configuring API tokens, or any question related to the obsidian-todoist-plugin. Trigger even if the user just says "todoist obsidian", "show my tasks in obsidian", "obsidian task sync", or asks how to display/add/manage Todoist tasks inside Obsidian.