by NeoLabHQ
The why skill applies Five Whys analysis to turn a symptom into a root-cause chain and a fix you can act on. Use this why guide for UX Audit, product issues, bugs, or process breakdowns when you need disciplined reasoning instead of shallow guesses.
by NeoLabHQ
The cause-and-effect skill uses Fishbone analysis to map likely root causes across People, Process, Technology, Environment, Methods, and Materials. It helps you turn a vague problem into a structured cause tree, prioritize likely drivers, and decide next steps. Useful for cause-and-effect for UX Audit, incident reviews, retrospectives, and troubleshooting.
by NeoLabHQ
analyse-problem is an A3 problem analysis skill for turning a messy issue into a one-page brief with background, current condition, root cause analysis, countermeasures, implementation plan, and follow-up. It is useful for Strategic Planning, ops, product, and engineering when you need a decision-ready problem statement.
by NeoLabHQ
Analyse is a Kaizen analysis skill that auto-selects Gemba Walk, Value Stream Mapping, or Muda for code, workflows, and inefficiencies. Use the analyse skill for Skill Authoring, repo audits, and structured investigation when you want the right method chosen first.
by NeoLabHQ
tree-of-thoughts is a reasoning workflow skill that helps agents explore multiple approaches, prune weak branches, and synthesize a better answer. It is useful for hard debugging, planning, architecture tradeoffs, and tree-of-thoughts for Agent Orchestration.
by NeoLabHQ
launch-sub-agent helps you dispatch a focused sub-agent for bounded tasks in multi-agent systems. It analyzes task complexity, selects an appropriate model tier, supports specialized agent matching, and adds self-critique verification for more reliable results.
by NeoLabHQ
multi-agent-patterns is a practical guide for designing Multi-Agent Systems in Claude Code when one agent is not enough. Use it to split work, coordinate sub-agents, and compare orchestration patterns without adding unnecessary overhead.
by NeoLabHQ
Judge is a two-phase evaluation skill that launches a meta-judge first, then a judge sub-agent to score work with isolated context, evidence, and clear criteria. Use it for report-only reviews of code, writing, analysis, or Skill Authoring when you need a defensible judge guide instead of a casual opinion.
by NeoLabHQ
judge-with-debate evaluates solutions through structured multi-agent debate, using a shared specification, evidence-based counterarguments, and up to 3 rounds to reach consensus. It is well suited for code review, rubric-based assessment, and judge-with-debate for Multi-Agent Systems workflows.
by NeoLabHQ
do-in-steps helps an agent tackle complex tasks by splitting work into ordered subtasks, orchestrating sub-agents, and verifying each step before moving on. It is a strong fit for repository changes, multi-step refactors, migrations, and do-in-steps for Agent Orchestration when you need controlled handoff and fewer silent failures.
by NeoLabHQ
do-competitively helps you solve important tasks with parallel candidate generation, rubric-based judging, and evidence-based synthesis. It is best for Workflow Automation and other high-stakes requests where quality, robustness, and tradeoff handling matter more than speed.
by alinaqi
icpg adds a WHY layer to code understanding with ReasonNodes, formal contracts, and drift detection. Use it for code review, refactoring, and pre-task analysis when you need intent, ownership, and risk context before changing code.
by NeoLabHQ
reflect is a Skill Validation tool for reviewing a prior response or output. It uses complexity triage and verification to catch missed flaws, weak reasoning, and overconfident approval before work ships.
by NeoLabHQ
critique is a report-only review skill that uses multiple specialized judges, debate, and consensus to assess completed work. It helps with critique for Code Review, correctness, quality, and missed issues before merging. Install critique in the NeoLabHQ context-engineering-kit and use it with file paths, commits, or context.
by massimodeluisa
recursive-decomposition is a workflow automation skill for large, multi-file, or multi-hop tasks. It splits work into smaller parts, processes them independently, and merges results for more reliable codebase reviews, document aggregation, and structured extraction when a single prompt would be too shallow or fragile.
