skillscope
CLAUDE.md1 starsChanged 6 months agoMITView on GitHub
Notes for AI coding agents working in this repo. Read before exploring. A TUI written in Go that scans SKILL.md files across every supported agentic-CLI harness on a machine (Claude Code, Codex, Cursor, OpenCode, Antigravity) and shows them in three views (matrix / tree / diff) broken out by scope. The full design rationale lives in DESIGN.md and the original spec is in GOAL.md — read both before making non-trivial changes. Adding a harness or a view is intentionally one…
- Commits and pushes
In this repository6 other files it gives its agents.
- bubbleteaSkill
- coding-standardsSkill
- golang-patternsSkill
- golang-proSkill
- security-reviewSkill
- skillscopeSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
No central switch statement, no factory map.
- Very specific: line 54
All scope paths flow through filepath.Join(ctx.HomeDir, …) — HomeDir comes from os.UserHomeDir() which returns %USERPROFILE% on Windows.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
Notes for AI coding agents working in this repo. Read before exploring.
What this is
A TUI written in Go that scans SKILL.md files across every supported
agentic-CLI harness on a machine (Claude Code, Codex, Cursor, OpenCode,
Antigravity) and shows them in three views (matrix / tree / diff) broken
out by scope. The full design rationale lives in DESIGN.md and the
original spec is in GOAL.md — read both before making non-trivial
changes.
Layout
cmd/skillscope/ main, flag parsing, harness/view registration
internal/app/ event loop, model, keymaps, render glue
internal/harness/ the Harness interface + one subpkg per harness
internal/view/ matrix, tree, diff — each in its own subpkg
internal/scan/ walker that resolves Scopes → SkillRecords
internal/ops/ copy / move / delete on disk
internal/ui/ shared lipgloss styles + preview cache
testdata/ fixtures used by `make demo` and testsThe two plugin surfaces
Adding a harness or a view is intentionally one file in one place:
- Harness: drop
internal/harness/<id>/harness.goimplementing theharness.Harnessinterface and callingharness.Register(h{})ininit(). Add a blank import incmd/skillscope/main.go. - View: drop
internal/view/<id>/view.goimplementingapp.Viewand callingapp.RegisterView(v{})ininit(). Same blank-import step.
No central switch statement, no factory map. If you find yourself editing the core to "register" something, you're doing it wrong.
Tooling
- Go 1.24.5+ (matches
go.mod). CI's matrix pins"1.24"which picks the latest patch. make build/make test/make demo.make demoruns the TUI pointed attestdata/— useful when verifying UI changes.- Single static binary, no CGO. Cross-compiles cleanly to linux/macos/windows × amd64/arm64.
- Lint job runs
gofmt -l .,go vet ./..., andstaticcheck(pinned to 2025.1.1). Keepgofmtclean — CI rejects unformatted files.
Windows / cross-platform
All scope paths flow through filepath.Join(ctx.HomeDir, …) — HomeDir
comes from os.UserHomeDir() which returns %USERPROFILE% on Windows.
Hardcoding / separators or string-concatenating paths will break the
Windows build. Cross-platform contract is locked by
scanner_pathsep_test.go (every platform) and the build-tagged
scanner_windows_test.go (Windows-only on CI).
House rules
- Never follow symlinks out of scope.
scan.walkScopeusesos.Lstatand refuses symlinkedSKILL.md.ops.copyFiledoes the same on the source side. Don't loosen these — there are tests guarding both. - Ops respect
Scope.ReadOnly. Plugin scopes are read-only;CopyandMovemust reject them. Same: tests guard this. - Preview rendering is async.
ui.Renderis the heavyweight glamour pass — only call it from atea.Cmdgoroutine and store the result viam.Preview.Set. Never blockUpdateorViewon it. - PR policy: PRs created by agents must be draft and stay
draft. Use
gh pr create --draft …. Don'tgh pr ready.
Where to look first when…
- adding a new SKILL.md location for an existing harness →
internal/harness/<id>/harness.go, edit the returnedScopes. - changing matrix/tree/diff layout →
internal/view/<id>/view.go. - adding a keybinding →
internal/app/update.go(handleKey). - changing what shows in the preview pane →
internal/ui/preview.goandinternal/app/render.go::renderModalPreview. - adding a CLI flag →
cmd/skillscope/main.go.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

