How Does This Work Explainer
cursor/plugins
Answers how-does-this-work and where-should-this-live questions by exploring the codebase with read-only subagents and writing an onboarding-depth explanation.
Consults existing breadcrumb analysis docs before exploring the codebase.
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .claude/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .claude/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumbType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .agents/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .agents/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .cursor/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .cursor/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deepklarity/harness-kit.git --path .claude/skills/hk-follow-breadcrumb--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .gemini/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .gemini/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumbInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .github/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .github/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/hk-follow-breadcrumb .opencode/skills/hk-follow-breadcrumb && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hk-follow-breadcrumb" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-follow-breadcrumb into .opencode/skills/hk-follow-breadcrumb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-follow-breadcrumb", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
hk-follow-breadcrumbConsults existing breadcrumb analysis docs before exploring the codebase.
Hk Follow Breadcrumb is an agent skill from deepklarity/harness-kit. Consults existing breadcrumb analysis docs before exploring the codebase. Use this skill whenever the user asks about how a flow works, where something happens in the code, how to debug or test a specific area, what files are involved in a feature, or needs to understand the path data takes through the system. Also trigger when the user mentions 'where does X happen', 'how does Y work', 'trace this', 'what files handle Z', 'how to test this flow', 'debug this area', or when you're about to spawn multiple…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Codebase onboarding and Subagents. The repository describes itself as: A kit for building with AI agents and also the engineering patterns around it. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 87305cd. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobTaskBashFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Hk Follow Breadcrumb loads about 1.4k tokens when it runs. Until then it costs about 213 tokens; SKILL.md has 554 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Grep, Glob, Task, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from deepklarity/harness-kit at commit 87305cd, republished under its MIT licence (© deepklarity). 554 words, ~1,427 tokens.
.claude/skills/hk-follow-breadcrumb/SKILL.md (or your agent's skills folder).This skill is about reading before searching. The docs/breadcrumb_analysis/ directory contains end-to-end workflow traces that have already been carefully researched and documented. Loading a relevant breadcrumb takes seconds and costs a fraction of what spawning exploration subagents costs. The breadcrumb docs are maintained alongside code changes, so they're the most reliable "map" of how flows work.
<exploration_context> $ARGUMENTS </exploration_context>
If the context above is empty, look at what the user is asking about in the conversation and infer the exploration target.
Read docs/breadcrumb_analysis/_INDEX.md. This is the single source of truth for what's been documented.
The index has two sections that matter:
Compare what the user is asking against the index entries. There are three outcomes:
Load the relevant docs in order of increasing detail:
FLOW.md — Read this first. It's the high-level map (30-second read). Shows the path data takes, which files/functions are involved at each hop, and where branches occur. This alone often answers "where does X happen?" questions.
DETAILS.md — Read this if the user needs function-level specifics: what data goes in/out, what conditionals change behavior, what side effects exist. This answers "how does X work?" questions.
DEBUG.md — Read this if the user is debugging something broken, or wants to know how to test a flow. Contains log locations, grep patterns, quick commands, env vars, and common breakpoints. This answers "how do I debug/test X?" questions.
Don't load all three by default. Start with FLOW.md. Only go deeper if the user's question requires it. Present what you found and ask if they need more detail.
Load the relevant breadcrumb for the covered portion. Then clearly tell the user:
The breadcrumb for <X> covers <these parts> of what you're asking about.
For <the uncovered parts>, I'll need to explore the code directly.Then explore only the gaps — don't re-trace what the breadcrumb already documents.
Tell the user:
No existing breadcrumb covers this flow. I'll explore the code directly.
Consider running /hk-breadcrumb-creator afterward to document this flow for next time.Then proceed with normal exploration (grep, glob, file reads, subagents as needed).
After loading the relevant breadcrumb docs, synthesize an answer to the user's actual question. Don't just dump the breadcrumb content — extract the specific information they need.
Good response pattern:
Based on the breadcrumb for <flow-name>:
<direct answer to their question, citing specific files/functions from the breadcrumb>
The key files involved are:
- `path/to/file.py` :: `function()` — <what it does in this context>
- `path/to/other.py` :: `other_func()` — <what it does>
<if debugging> Quick commands from the debug guide:
<relevant commands from DEBUG.md>If the breadcrumb is stale (references files/functions that no longer exist), note which parts seem outdated and verify those specific points against the current code. Flag this to the user so the breadcrumb can be updated.
If the user's exploration uncovered a flow that isn't documented (outcome C), or revealed that an existing breadcrumb is incomplete (outcome B with significant gaps), suggest:
This flow isn't documented in breadcrumb analysis yet. Want me to create one?
Run /hk-breadcrumb-creator to trace and document it for future reference.This closes the loop — exploration that finds undocumented territory feeds back into the documentation system.
function_name in file.py do?" → Just read the file directly./hk-breadcrumb-creator instead. This skill reads; that one writes.© deepklarity, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/hk-follow-breadcrumb of deepklarity/harness-kit.
Open the folder on GitHubat commit 87305cd
Hk Follow Breadcrumb next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hk Follow Breadcrumb this skilldeepklarity/harness-kit | 100 | — | ~1.4k | Automated safety check: Notes | MIT | |
| How Does This Work Explainercursor/plugins | 11k | 6 repos | ~630 | Automated safety check: Pass | None | |
| Codebase Research QuestionsWirasm/prp | 2.3k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Codebase Onboardingspencerpauly/awesome-cursor-skills | 844 | — | ~653 | Automated safety check: Notes | CC0-1.0 | |
| Codebase Exploreryologdev/yoyo-evolve | 1.9k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Caveman Repository ExplorerJuliusBrussee/caveman | 111k | 1 repos | ~492 | Automated safety check: Pass | Apache-2.0 |
cursor/plugins
Answers how-does-this-work and where-should-this-live questions by exploring the codebase with read-only subagents and writing an onboarding-depth explanation.
Wirasm/prp
Answers where and how questions about a codebase with parallel research agents and a write-up where every claim cites a file and line, describing only what exists.
spencerpauly/awesome-cursor-skills
Launch multiple explore subagents in parallel to investigate architecture, data models, auth, APIs, and deployment.
yologdev/yoyo-evolve
Builds a structural map of a large or unfamiliar codebase by dispatching sub-agents to summarize regions, keeping the main context small.
JuliusBrussee/caveman
A read-only explorer for cold-start orientation or failed searches that replies with nothing but file path and line range citations, keeping its reads out of main context.
code-yeongyu/oh-my-openagent
Generates a tree of AGENTS.md files for a repository, one at the root and more in complex subdirectories, so agents learn its structure and conventions.
deepklarity/harness-kit
Create new skills, modify and improve existing skills, and measure skill performance.
deepklarity/harness-kit
Run comprehensive agent-native architecture review with scored principles.
deepklarity/harness-kit
Mock-first, layer-by-layer feature development. An agent skill from deepklarity/harness-kit.
deepklarity/harness-kit
Audit whether an AI agent can autonomously close the loop on problems in a given area — from discovering a symptom to verifying a fix — without human intervention.
deepklarity/harness-kit
Traces a workflow end-to-end through the harness-kit monorepo and creates a breadcrumb analysis doc in docs/breadcrumbanalysis/.
deepklarity/harness-kit
Generate changelog entries from git diffs, prepend to CHANGELOG.md, and optionally commit + PR.
Categories
Consults existing breadcrumb analysis docs before exploring the codebase. Hk Follow Breadcrumb is an agent skill from deepklarity/harness-kit. Consults existing breadcrumb analysis docs before exploring the codebase.
Hk Follow Breadcrumb fits situations like: the user asks about how a flow works; where something happens in the code; test a specific area; what files are involved in a feature.
Run `npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a claude-code`. Or copy the skill folder (.claude/skills/hk-follow-breadcrumb in deepklarity/harness-kit) into .claude/skills/hk-follow-breadcrumb in your project. Claude Code loads it when a task matches its description.
Run `npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a codex`. Or copy the skill folder (.claude/skills/hk-follow-breadcrumb in deepklarity/harness-kit) into .agents/skills/hk-follow-breadcrumb in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hk-follow-breadcrumb, .gemini/skills/hk-follow-breadcrumb, .github/skills/hk-follow-breadcrumb and .opencode/skills/hk-follow-breadcrumb in your project.
SKILL.md names no scripts, command-line tools or credentials: Hk Follow Breadcrumb is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Task, Bash.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Hk Follow Breadcrumb is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Hk Follow Breadcrumb: How Does This Work Explainer (cursor/plugins, 11k stars), Codebase Research Questions (Wirasm/prp, 2.3k stars), Codebase Onboarding (spencerpauly/awesome-cursor-skills, 844 stars) and Codebase Explorer (yologdev/yoyo-evolve, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
deepklarity (a GitHub organization) maintains it in deepklarity/harness-kit, which has 100 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on July 15, 2026.
Source: deepklarity/harness-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.