kiro-debug SKILL.md skillA
kiro-debug from huruikagi/specbind is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add huruikagi/specbind/kiro-debug@git:20260408.a8ee894Pins git:20260408.a8ee894 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- huruikagi/specbind
- Path
tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-debug/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260408.a8ee894, committed Apr 8, 2026
- Size
- 5,305 bytes
- Repository stars
- 2
- License
- MIT
Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
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
# kiro-debug ## Overview This skill is for fresh-context root cause investigation. It combines local evidence, runtime/config inspection, and external documentation or issue research when available. It is not a patch generator for guess-first debugging. ## When to Use - Implementer reports `BLOCKED` - Reviewer rejection repeats after remediation - Validation fails unexpectedly - A task appears to conflict with runtime or platform reality - The same failure survives more than one attempted fix Do not use this skill to speculate about fixes before gathering evidence. ## Inputs Provide: - Exact failure symptom or blocker statement - Error messages, stack trace, and failing command output - Current `git diff` or summary of uncommitted failed changes - Task brief: what was being built - Reviewer feedback, if the failure came from review rejection - Relevant spec file paths (`requirements.md`, `design.md`) - Relevant requirement/design section numbers - Relevant `## Implementation Notes` - Runtime or environment constraints already known ## Outputs Return: - `ROOT_CAUSE` - `CATEGORY` - `FIX_PLAN` - `VERIFICATION` - `NEXT_ACTION: RETRY_TASK | BLOCK_TASK | STOP_FOR_HUMAN` …
Read the whole file at its exact version.
How to install
mdr add huruikagi/specbind/kiro-debug@sha256:6a88e4ec7102c0ebThe line at the top of this page pins the label git:20260408.a8ee894, 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_uvytovm4e47cb524)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 8, 2026.
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 (5305 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
huruikagi/specbind · 2 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uvytovm4e47cb524 GET https://markdownregistry.com/api/v1/resolve?ref=huruikagi/specbind/kiro-debug GET https://markdownregistry.com/api/v1/blob/6a88e4ec7102c0ebcba2c7dfad37eeb0439a53b376fdada54a0b0d8b5ee46378
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.
More from huruikagi/specbind
Every file in huruikagi/specbind