Skip to content
Agentmart
Submit a tool

check-resolvable

Audit ~/.claude/ for orphans — skills, commands, guides, and tools that exist on disk but have no path from CLAUDE.md / RESOLVER.md / other reachable files.

Skill by griffinhilly

IndexedMIT★ 67
Write a review

Chalk Labs

Need help deploying check-resolvable?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/griffinhilly-check-resolvable

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Audit ~/.claude/ for orphans — skills, commands, guides, and tools that exist on disk but have no path from CLAUDE.md / RESOLVER.md / other reachable files. Run weekly or before any CLAUDE.md cleanup.

Use cases: security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 1, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/check-resolvable

What's inside

Skill name
check-resolvable
Description
Audit ~/.claude/ for orphans — skills, commands, guides, and tools that exist on disk but have no path from CLAUDE.md / RESOLVER.md / other reachable files. Run weekly or before any CLAUDE.md cleanup.
License
MIT
Instructions
68 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# /check-resolvable — Reachability Audit

A thin wrapper around `~/.claude/tools/check-resolvable.py`. The script does the deterministic scan; this skill interprets the result and recommends action.

**Per CLAUDE.md latent-vs-deterministic rule, the audit itself is deterministic** (regex over a fixed text corpus, no LLM judgment). The optional second pass — "which of these orphans actually matter" — is latent and lives in this skill, not the script.

## When to invoke

- Weekly cron via `/loop` or `/schedule`
- Before any CLAUDE.md cleanup or skill refactor
- After adding ≥3 new skills/guides/tools (signal that the routing surface has grown)
- After any workflow-config sync that may have moved files

## Process

### Step 1: Run the deterministic scan

```
python3 ~/.claude/tools/check-resolvable.py --human
```

Add `--list-reachable` to also see what's known-good. Add `--out report.json` to persist the full JSON.

### Step 2: Interpret orphans

For each orphan reported:

- **Genuine orphan** (dead capability) — the file exists but nothing references it; safe to retire or document for removal
- **False positive** (script's pattern missed a reference) — the file IS reachable but the script's regex didn't catch it; flag for adding the reference pattern to `check-resolvable.py`
- **Pending wire-up** (newly added, not yet wired) — the file was just created and hasn't been added to RESOLVER.md or CLAUDE.md yet; add the reference now

### Step 3: Resolve

- Genuine orphans: propose removal (don't delete without user approval per your safety doctrine)
- False positives: edit `check-resolvable.py` to add the missing pattern; re-run
- Pending wire-up: add the routing entry to RESOLVER.md or the trigger to CLAUDE.md; re-run

### Step 4: Report

Summarize:
- Total capabilities counted
- Number reachable vs. orphan, by kind
- Action taken for each orphan (retired / wired / pattern-fixed / left as-is)
- Any pattern-detection gaps in the script that should be fixed

## Limitations of the deterministic scan

The audit catches *file-level* reachability — whether the artifact is referenced. It does NOT catch:

- **Stale references** (a guide is referenced but its content is outdated) — different problem, addressed by quarterly CLAUDE.md health check
- **Logical reachability** (a skill is referenced but the conditions for invocation never fire) — addressed by trigger evals (`~/.claude/tools/skill-trigger-evals.py`)
- **Cross-project references** (project CLAUDE.md files reference user-scope skills) — partial: this scan only walks `~/.claude/`, not per-project COMP files

## Extensions (mode of thinking)

Reachability audits are an instance of the broader principle: **"trust the determinism."** Any time the workflow accumulates capability beyond what a human can mentally enumerate, automated reachability becomes the only way to keep the system honest. Extensions:

1. **Cross-project reachability** — extend the corpus to include every project's CLAUDE.md / MEMORY.md / PLAN.md / ORIENT.md. Catches cases where a project references a skill that no longer exists.
2. **Reverse direction** — instead of "are all capabilities reached?", ask "are all references valid?" (catches typos: CLAUDE.md says `/check-resolveable` but the skill is `/check-resolvable`).
3. **Health over time** — run the audit weekly and log results; surface the *trend* in orphan count. If orphans grow week-over-week despite no removals, something is decaying.
4. **Trigger eval coupling** — pair this with `skill-trigger-evals.py`. Reachability says "this skill is wired in"; trigger evals say "this skill actually fires on the right inputs." Both are needed for a healthy routing layer.

## Sources

- Garry Tan, *Resolvers: The Routing Table for Intelligence* — "First run found 6 unreachable skills. Fifteen percent of the system's capabilities were dark."
- Workflow dialectic review — the binding constraint that this audit must be a script, not an LLM-driven skill.

From griffinhilly/claude-code-synthesis, MIT.

More from griffinhilly/claude-code-synthesis

Signals

Stars
67
Forks
6
Open issues
1
Last commit (this folder)
Jul 24, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from griffinhilly

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get check-resolvable running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying check-resolvable?

CallGet help
Cite this page

check-resolvable skill. Agent Mart. https://agentmart.dev/skills/griffinhilly-check-resolvable (last updated 2026-10-24)