kaizen-explore SKILL.md skillA
kaizen-explore from hfadhlullah/kaizen is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hfadhlullah/kaizen/kaizen-explore@git:20261109.0858cc9Pins git:20261109.0858cc9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hfadhlullah/kaizen
- Path
skills/kaizen-explore/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261109.0858cc9, committed Nov 9, 2026
- First version recorded
- Nov 8, 2026
- Size
- 7,993 bytes
- Repository stars
- 6
- License
- MIT
Question an idea and research its uncertainties before Kaizen planning. Use for a new product, unclear improvement, or an explicit request to explore or stress-test a direction. Routine fixes and already agreed work go directly to Plan.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Kaizen Explore Explore establishes the problem worth solving and the evidence for a direction. It produces `00-explore.md` in a Kaizen run; it does not implement the product. Use the existing run when invoked inside Kaizen. Otherwise read the `kaizen` skill and perform its intake with an explicit Explore override. Do not enable Explore globally just because it was requested for one run. ## Start and resume Read `state.json`, `00-request.md`, any existing `00-explore.md`, and the project's notes index and relevant sources. Keep the original request intact. A resumed run keeps its recorded Explore choice even if settings changed. A run already past Explore does not return to it unless the user explicitly requests that. For an active exploration record `explore_status=active`, `stage=explore`, and `awaiting=null` with `kaizen state <id>`. Report the phase with `kaizen report`. Create `00-explore.md` immediately and save progress after meaningful exchanges or research findings, so another session can resume without repeating questions. ## Look around before you talk After reading the local material and before the first question, check what is …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uw3tnuvzmre5polp/244d81f0ca9b1060c6c287f4f6715e0a15099a9c1aebedc1a996172a642d9140.json
Then /plugin install kaizen-explore@markdownregistry-uw3tnuvzmre5polp in Claude Code. It installs git:20261109.0858cc9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add hfadhlullah/kaizen/kaizen-explore@sha256:244d81f0ca9b1060The line at the top of this page pins the label git:20261109.0858cc9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uw3tnuvzmre5polp)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in hfadhlullah/kaizen/kaizen-explore since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of kaizen-explore from somewhere else? Ask it: where did my kaizen-explore come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Nov 8, 2026 and Nov 9, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261109.0858cc9 latest | 2026-11-09 | 0858cc9 | 7,993 B | A | view · diff |
| git:20261109.31ad92c | 2026-11-09 | 31ad92c | 7,992 B | A | view · diff |
| git:20261109.0c80828 | 2026-11-09 | 0c80828 | 7,443 B | A | view · diff |
| git:20261108.4d4ae03 | 2026-11-08 | 4d4ae03 | 6,252 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/kaizen-explore/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7993 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hfadhlullah/kaizen · 6 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uw3tnuvzmre5polp GET https://markdownregistry.com/api/v1/resolve?ref=hfadhlullah/kaizen/kaizen-explore GET https://markdownregistry.com/api/v1/blob/244d81f0ca9b1060c6c287f4f6715e0a15099a9c1aebedc1a996172a642d9140
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.