hyper-interview SKILL.md skillA
hyper-interview from zeikar/hyperclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zeikar/hyperclaude/hyper-interview@git:20260929.d328514Pins git:20260929.d328514 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zeikar/hyperclaude
- Path
skills/hyper-interview/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260929.d328514, committed Sep 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 10,517 bytes
- Repository stars
- 5
- License
- MIT
Use when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you need", "clarify requirements first", "I'm not sure exactly what I want", "make sure you understand before building". Also when the user invokes /hyperclaude:hyper-interview. Runs a short one-question-at-a-time interview and writes a spec to .hyperclaude/specs/ — the front-end input to /hyperclaude:hyper-research and /hyperclaude:hyper-plan. Distinct from…
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
# hyper-interview Requirements-clarification gate. Turns a vague idea into a clear spec through a short Socratic interview — one targeted question at a time, aimed at whichever requirement dimension is least clear — then writes the spec to `.hyperclaude/specs/<YYYYMMDD-HHMM>-<slug>.md`. The spec is the front-end input to `hyper-research` / `hyper-plan`; the slug it mints is derived from the idea text the same way those skills derive theirs, so handing the same idea forward keeps the `research → plan → plan-review` trace linked. **Claude-only — no Codex.** Critique belongs downstream, where it has something concrete to critique (`hyper-plan-review` on the plan, `hyper-code-review` on the diff). This gate's job is *clarity*, not review: get the requirements right so the plan isn't built on guesses. Anything off in the spec is caught when the plan is reviewed. This is a **light** interview: a conversational flow that aims each question at the least-clear requirement dimension, judged qualitatively, with no state kept beyond the spec file. ## When to use - User typed `/hyperclaude:hyper-interview <idea>`. …
Read the whole file at its exact version.
How to install
mdr add zeikar/hyperclaude/hyper-interview@sha256:49768515c8a1631dThe line at the top of this page pins the label git:20260929.d328514, 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_b7pf4le3p7vhggxs)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 2, 2026 and Sep 29, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260929.d328514 latest | 2026-09-29 | d328514 | 10,517 B | A | view · diff |
| git:20260929.99a57bc | 2026-09-29 | 99a57bc | 10,436 B | A | view · diff |
| git:20260929.2ab108a | 2026-09-29 | 2ab108a | 10,204 B | A | view · diff |
| git:20260704.33dedc7 | 2026-07-04 | 33dedc7 | 10,337 B | A | view · diff |
| git:20260704.64cd556 | 2026-07-04 | 64cd556 | 10,281 B | A | view · diff |
| git:20260602.355e553 | 2026-06-02 | 355e553 | 10,118 B | A | view |
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 (10517 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
zeikar/hyperclaude · 5 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b7pf4le3p7vhggxs GET https://markdownregistry.com/api/v1/resolve?ref=zeikar/hyperclaude/hyper-interview GET https://markdownregistry.com/api/v1/blob/49768515c8a1631dd6d6b83b4b9031e44956815001c6d2370aac0891a13bc3e2
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.