Loading...
Loading...
Found 17 Skills
Set up, audit, and maintain repository documentation and instructions for AI agents. Use for repository harness structure, execution-plan support, or diagnosing why an agent missed a repo rule.
DAG-based multi-skill orchestration: Discover, Plan, Validate, Execute. Builds execution graphs for tasks requiring multiple skills in sequence or parallel with dependency resolution and context passing. Use when a task requires 2+ skills chained together, parallel skill execution, or conditional branching between skills. Use for "compose skills", "chain workflow", "multi-skill", or "orchestrate skills". Do NOT use when a single skill can handle the request, or for simple sequential invocation that needs no dependency management.
Optimize SQL queries for performance with indexing strategies, query rewriting, and execution plan analysis. Use when queries are slow, optimizing database performance, or analyzing query execution.
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.
Visualize planned changes before implementation. Use when reviewing plans, comparing before/after architecture, assessing risk, or analyzing execution order and impact.
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
Decide whether/how to pivot a startup or product and produce a Pivot Decision & Execution Pack (diagnosis, exhaustion check, pivot options map, pivot thesis + metrics, validation plan, execution plan, decision memo). Use for “should we pivot?”, “stuck pre-PMF”, “growth stalled”, “change ICP”, “reposition”, “major strategy reset”.
Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.
Diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators (AllNodesScan, CartesianProduct, Eager, NodeByLabelScan), and prescribing fixes (indexes, hints, query rewrites, runtime selection). Use when a query is slow, when EXPLAIN or PROFILE output needs interpretation, when dbHits or pageCacheHitRatio are poor, when cardinality estimation diverges from actuals, or when deciding between slotted/pipelined/parallel runtimes. Covers USING INDEX / USING SCAN / USING JOIN hints, db.stats.retrieve, SHOW QUERIES, SHOW TRANSACTIONS, TERMINATE TRANSACTION. Does NOT write new Cypher from scratch — use neo4j-cypher-skill. Does NOT cover GDS algorithm tuning — use neo4j-gds-skill. Does NOT cover index/constraint creation syntax details — use neo4j-cypher-skill references/indexes.md.
Improve database query performance through indexing, query optimization, and execution plan analysis. Reduce response times and database load.
Turn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.