analyse
by NeoLabHQAnalyse 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.
This skill scores 74/100, which means it is listable for directory users as a useful but moderately constrained analysis helper. It gives a clear trigger, a sensible method-selection workflow, and enough operational structure that an agent can choose between Gemba Walk, Value Stream Mapping, and Muda with less guesswork than a generic prompt, though it would benefit from more supporting assets and tighter execution guidance.
- Clear auto-selection trigger and optional `/analyse [target_description]` usage make it easy for agents to invoke.
- Strong operational mapping: the skill explains when to use Gemba Walk, Value Stream Mapping, or Muda, reducing method-selection ambiguity.
- Substantial body content with multiple headings, examples, and stepwise flow suggests real workflow value rather than a placeholder.
- No scripts, references, resources, or supporting files are included, so adoption relies entirely on the SKILL.md instructions.
- The visible excerpt shows a truncated step list and no install command, which may leave some execution details under-specified for first-time users.
Overview of analyse skill
What analyse does
The analyse skill is an auto-selector for Kaizen-style analysis. It helps you choose the right lens for a target: Gemba Walk for code reality, Value Stream Mapping for workflows, or Muda for waste and inefficiency. If you want the analyse skill because you need a faster way to inspect a system without guessing the method first, this is the right fit.
Best fit for this skill
Use analyse when you have a codebase area, process, or inefficiency description and want structured investigation instead of a vague “look into this” prompt. It is especially useful for Skill Authoring, repo audits, architecture review, and workflow bottleneck analysis.
Why install it
The main value of analyse is method selection. Rather than forcing one analysis style onto every problem, it maps your target to a more suitable technique, which reduces false starts and improves the quality of the first pass.
How to Use analyse skill
Install and entry point
Install the skill with npx skills add NeoLabHQ/context-engineering-kit --skill analyse. The primary entry point is /analyse [target_description], where the target can be a feature, workflow, subsystem, or problem area.
How to frame input for analyse
Give the skill a concrete target plus the kind of concern you have. Better: /analyse deployment workflow for slow approvals and failed rollbacks. Weaker: /analyse my project. The skill works best when it can infer whether you need code exploration, process mapping, or waste analysis.
Read these files first
Start with SKILL.md, then inspect any repo-level guidance that may shape behavior in this ecosystem, especially README.md, AGENTS.md, and metadata.json if present. In this repo, the main practical source is SKILL.md; there are no helper scripts or support folders to deepen the workflow.
Practical usage tips
If you already know the method, you can override auto-selection with METHOD values like gemba, vsm, or muda. Use this when the target is ambiguous but your goal is clear. For best results, describe the object, the outcome you want, and the constraint you care about most.
analyse skill FAQ
Is analyse for code only?
No. analyse handles code implementation, workflows, and waste analysis. The deciding factor is the target type and what you want to learn, not whether the input is a repository or a process.
When should I not use analyse?
Do not use it when you already have a narrow, obvious task that needs no method choice, or when the prompt is so vague that the skill cannot distinguish code reality from process issues. In those cases, add context first or pick a more specific skill.
How is analyse different from a normal prompt?
A normal prompt usually assumes one analysis style. The analyse skill first chooses the best Kaizen method, which is useful when you want a structured start and fewer dead-end assumptions.
Is analyse suitable for beginners?
Yes, if the user can describe the target in plain language. Beginners get the most value when they provide a specific area and a concrete question, such as where a workflow slows down or where code behavior differs from docs.
How to Improve analyse skill
Give a stronger target
The biggest quality boost comes from naming the exact thing under analysis and the failure mode you care about. For example, “analyze the auth flow for mismatch between docs and implementation” produces better guidance than “analyze auth.”
Specify the outcome you want
Tell analyse whether you need a code walkthrough, a process map, or waste identification. Even though the skill auto-selects, a clear outcome helps it choose and explain the method with less ambiguity.
Use constraints and examples
Include one or two real signals: a slow step, a confusing function, a repeated handoff, or a known inefficiency. Those details help the analyse skill focus on evidence rather than broad exploration.
Iterate after the first pass
If the first analysis is too broad, narrow the target and rerun with a more specific method hint. For analyse skill, iterative prompts usually outperform one oversized request because they preserve the method selection while tightening scope.