shikhu-inquiry SKILL.md skillA
shikhu-inquiry from arjunpatel7/shikhu is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arjunpatel7/shikhu/shikhu-inquiry@git:20261106.63de1d1Pins git:20261106.63de1d1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arjunpatel7/shikhu
- Path
src/shikhu/_skill/shikhu-inquiry/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261106.63de1d1, committed Nov 6, 2026
- First version recorded
- Oct 3, 2026
- Size
- 7,962 bytes
- Repository stars
- 22
- License
- MIT
Answer a question about how or why something in THIS repository works, by showing which tracked files answer it and why, then recording the exchange so it can seed a quiz later. Use it whenever the user asks a genuine question whose subject belongs to this repository — its source, CLI behavior, config, CI, hooks or build setup — and answering it well means reading files here. These arrive casually and mid-task, often elliptical or typo-laden: "how are we storing quizzes rn?…
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
# shikhu-inquiry — answer from the codebase, then bank the question ## Why this exists Shikhu tracks how well the user understands *their own* code. Historically that meant generating quizzes and asking them to sit through them, which people don't do. But people *do* ask their agent to explain their code, constantly. This skill turns that existing habit into the same signal: the question they already asked becomes the seed of a quiz question, and the files you cite become the record of what it was about. Two things follow from that, and they are the whole point: - **Show your work.** Don't just answer — say which files answer it and why those files. The user should end the turn knowing where the answer lives, not just what it is. - **Ask once, cheaply.** One short confirm closes the loop. Silence earns nothing. ## 0. Invoked explicitly? If the user ran `/shikhu-inquiry` directly, skip any judgment about whether this is a conceptual question — they've already made that call. Use their message as the question, or ask them for one if they gave none, then continue from step 1. ## 1. Get the packet ```bash shikhu inquiry-packet "<the user's question>" ``` …
Read the whole file at its exact version.
How to install
mdr add arjunpatel7/shikhu/shikhu-inquiry@sha256:33da742b19fc3c3bThe line at the top of this page pins the label git:20261106.63de1d1, 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_3lwkmevnemkxmyef)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 3, 2026 and Nov 6, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.63de1d1 latest | 2026-11-06 | 63de1d1 | 7,962 B | A | view · diff |
| git:20261105.9ee8def | 2026-11-05 | 9ee8def | 7,789 B | A | view · diff |
| git:20261012.bd0bc64 | 2026-10-12 | bd0bc64 | 6,778 B | A | view · diff |
| git:20261003.84bc60f | 2026-10-03 | 84bc60f | 6,747 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 (7962 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
arjunpatel7/shikhu · 22 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3lwkmevnemkxmyef GET https://markdownregistry.com/api/v1/resolve?ref=arjunpatel7/shikhu/shikhu-inquiry GET https://markdownregistry.com/api/v1/blob/33da742b19fc3c3bd631871dbb2d83f4bd75201eff16e6447cc200e3962cb1e3
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.