Agent skill

Hk Follow Breadcrumb

by deepklarity in deepklarity/harness-kit

Consults existing breadcrumb analysis docs before exploring the codebase.

MITAuto-check: notesDevelopment

Install Hk Follow Breadcrumb

skills CLI
$ npx skills add deepklarity/harness-kit --skill hk-follow-breadcrumb -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install deepklarity/harness-kit hk-follow-breadcrumb --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
hk-follow-breadcrumb
GitHub stars
100
Token cost
~1.4k tokens
SKILL.md length
554 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Consults existing breadcrumb analysis docs before exploring the codebase.

  • Works in 4 steps: Load the index → Match the question to breadcrumbs → Present findings → …
  • The user asks about how a flow works
  • SKILL.md covers Context, Step 1: Load the index, Step 2: Match the question to… and Step 3: Present findings, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • 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

Example prompts

  • “where does X happen”
  • “how does Y work”
  • “trace this”
  • “/hk-follow-breadcrumb”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Task, Bash

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Load the index
  2. Match the question to breadcrumbs
  3. Present findings
  4. Suggest breadcrumb creation for gaps

What it can do on your machine

Read from SKILL.md and the folder at commit 87305cd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Task
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~213
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Task, Bash

Automated 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.

SKILL.md

The full file from deepklarity/harness-kit at commit 87305cd, republished under its MIT licence (© deepklarity). 554 words, ~1,427 tokens.

Download SKILL.mdSave it as .claude/skills/hk-follow-breadcrumb/SKILL.md (or your agent's skills folder).
name
hk-follow-breadcrumb
description
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 exploration subagents to understand a cross-cutting flow. Even if the user doesn't explicitly ask — if the task requires understanding how multiple layers connect (frontend → backend → worker → CLI), check breadcrumbs first. This is cheaper and more accurate than re-discovering the same information through code search.
allowed-tools
Read, Grep, Glob, Task, Bash
argument-hint
<what you're trying to understand, e.g. 'how does task execution work' or 'where do traces get ingested'>

/hk-follow-breadcrumb — Breadcrumb-First Exploration

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.

Context

<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.

Step 1: Load the index

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:

  1. Flows table — lists every breadcrumb folder and what it traces. Scan this to find which breadcrumb(s) cover the user's question.
  2. Quick navigation — maps common symptoms (e.g., "task stuck in IN_PROGRESS", "screenshots not showing") directly to the right DEBUG.md. If the user describes a symptom, check here first.

Step 2: Match the question to breadcrumbs

Compare what the user is asking against the index entries. There are three outcomes:

A. Direct hit — a breadcrumb covers exactly this flow

Load the relevant docs in order of increasing detail:

  1. 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.

  2. 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.

  3. 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.

Show full SKILL.md (222 more words)Show less
B. Partial coverage — a breadcrumb covers part of the flow

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.

C. No coverage — nothing in the index matches

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).

Step 3: Present findings

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.

Step 4: Suggest breadcrumb creation for gaps

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.

When NOT to use this skill

  • Single-file questions — "What does function_name in file.py do?" → Just read the file directly.
  • Creating new breadcrumbs — Use /hk-breadcrumb-creator instead. This skill reads; that one writes.
  • General codebase search — "Find all TODO comments" → Just grep. Breadcrumbs trace flows, not search for patterns.

© deepklarity, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/hk-follow-breadcrumb of deepklarity/harness-kit.

Open the folder on GitHubat commit 87305cd

Compare with similar skills

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.

Hk Follow Breadcrumb compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hk Follow Breadcrumb this skilldeepklarity/harness-kit100—~1.4kAutomated safety check: NotesMIT
How Does This Work Explainercursor/plugins11k6 repos~630Automated safety check: PassNone
Codebase Research QuestionsWirasm/prp2.3k—~2.8kAutomated safety check: PassMIT
Codebase Onboardingspencerpauly/awesome-cursor-skills844—~653Automated safety check: NotesCC0-1.0
Codebase Exploreryologdev/yoyo-evolve1.9k—~2.8kAutomated safety check: PassMIT
Caveman Repository ExplorerJuliusBrussee/caveman111k1 repos~492Automated safety check: PassApache-2.0

Similar skills

  • Official

    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.

    11k GitHub starsUsed in 6 repos~630 tokens
    DevelopmentAuto-check passed
  • 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.

    2.3k GitHub stars~2.8k tokensUpdated 9 days ago
    DevelopmentAuto-check passed
  • Codebase Onboarding

    spencerpauly/awesome-cursor-skills

    Launch multiple explore subagents in parallel to investigate architecture, data models, auth, APIs, and deployment.

    844 GitHub stars~653 tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes
  • Codebase Explorer

    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.

    1.9k GitHub stars~2.8k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Caveman Repository Explorer

    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.

    111k GitHub starsUsed in 1 repo~492 tokens
    Agent WorkflowsAuto-check passed
  • Init Deep AGENTS.md Generator

    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.

    70k GitHub stars~3.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from deepklarity/harness-kit

All 18 skills in this repo
  • Hk Skill Creator

    deepklarity/harness-kit

    Create new skills, modify and improve existing skills, and measure skill performance.

    100 GitHub stars~3.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Hk Arch Audit

    deepklarity/harness-kit

    Run comprehensive agent-native architecture review with scored principles.

    100 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check: notes
  • Hk Mock First

    deepklarity/harness-kit

    Mock-first, layer-by-layer feature development. An agent skill from deepklarity/harness-kit.

    100 GitHub stars~3.9k tokensUpdated 2 mo ago
    Auto-check: notes
  • Hk Autonomy Audit

    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.

    100 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check: notes
  • Hk Breadcrumb Creator

    deepklarity/harness-kit

    Traces a workflow end-to-end through the harness-kit monorepo and creates a breadcrumb analysis doc in docs/breadcrumbanalysis/.

    100 GitHub stars~3k tokensUpdated 2 mo ago
    Auto-check: notes
  • Hk Changelog

    deepklarity/harness-kit

    Generate changelog entries from git diffs, prepend to CHANGELOG.md, and optionally commit + PR.

    100 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check: notes

Questions about Hk Follow Breadcrumb

What does Hk Follow Breadcrumb do?

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.

When should I use Hk Follow Breadcrumb?

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.

How do I install Hk Follow Breadcrumb in Claude Code?

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.

How do I install Hk Follow Breadcrumb in Codex?

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.

Can I use Hk Follow Breadcrumb in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Hk Follow Breadcrumb need to run?

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.

Does Hk Follow Breadcrumb access the network?

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.

Is Hk Follow Breadcrumb safe to install?

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.

What licence does Hk Follow Breadcrumb use?

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.

How many tokens does Hk Follow Breadcrumb use?

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.

What are the alternatives to Hk Follow Breadcrumb?

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.

Who maintains Hk Follow Breadcrumb?

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.