Loading...
Loading...
Found 5,906 Skills
What's blocking close — maintain the closing checklist with status, critical path, and days to close. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the checklist", or on a scheduled status pull.
Persist learnings to memory or maintain existing memories. Triggers on "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Start here for first-time CARTO use — install the CLI, authenticate, switch profiles, understand JSON output and async job patterns. Also orients on the two parallel access paths into the CARTO platform (CLI for authoring/scripting, MCP server for inline interactions in chat hosts) and which skills cover each.
Install all AntiGravity lazy package skills at once. Load when saying "Install all" or "Install all AntiGravity lazy packages".
Turn Hermes into an autonomous project executor using Kanban boards inside Obsidian vault with visual rendering and REST API control
Use when Hermes reviews Claude-authored writeups, public docs, skill changes, README/agent/issue-template changes, or upstream speed-match documentation before syncing or publishing.
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
Use when running the CTO flow-optimization loop — WIP scan, epic focus, triage unlabeled issues, and dispatch.
Collaborative design exploration that authors the Design & Rationale section of the one unified docs/specs/ spec. Triggers: 'brainstorm', 'ideate', 'explore options', or /ideate. Default is a one-pass design preamble; the deep rung gates the 2-3 approach divergent loop and the discover bridge. Do NOT use for task decomposition (that is /plan, which adds Decomposition to the same doc) or code review.
Decompose the unified docs/specs/ artifact into parallelizable tasks — the ## Decomposition section of the same document whose ## Design & Rationale section holds the DR-N source. Triggers: 'plan implementation', 'create tasks from spec', or /plan. Applies the verification ladder: verification depth matches each task's blast radius — static analysis for low-risk tasks, scoped tests plus a kill-probe for medium, the integration suite on top for high-risk surfaces (judged test-after, not test-first ordering). Auto-chained from /ideate, or run directly to author the whole unified spec at thin/standard depth. Do NOT use for brainstorming, debugging, or code review.
Use this skill when the user wants to analyze an existing pipe for improvement opportunities — automation gaps, manual bottlenecks, missing AI agents, field conditions, or adjacent processes. Acts as a process analyst: investigates, diagnoses, and improves the pipe in progressive rounds — each round delivers visible results.