DEPRECATED — superseded by tree-sitting. This skill generated persistent _MAP.md files; tree-sitting does the same AST extraction at runtime (~700ms for 250 files) with no artifact to write, commit, or keep in sync. Use tree-sitting for "map this codebase", "explore repo", "understand structure", or any code navigation task. The final working version is archived at release mapping-codebases-v0.8.0.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use tree-sitting instead.
This skill wrote _MAP.md files to disk — a persisted symbol inventory per
directory, generated once and read many times. That tradeoff made sense when
scanning was expensive. It isn't: tree-sitting parses a 250-file repo in about
700ms and answers queries against the in-memory AST in under a millisecond.
A persisted map costs what a runtime scan does not — it goes stale, it needs regenerating, it gets committed, and it must be excluded from every other tool that walks the tree. Nothing was gained for that.
TREESIT=/mnt/skills/user/tree-sitting/scripts/treesit.py
# Was: codemap.py /path/to/repo → root orientation
python3 $TREESIT /path/to/repo
# Was: reading every _MAP.md in the tree → full inventory
python3 $TREESIT /path/to/repo --depth=-1 --detail=sparse
# Was: grepping _MAP.md for a symbol → direct lookup
python3 $TREESIT /path/to/repo --no-tree 'find:parse_input'
The last working release is
mapping-codebases-v0.8.0
(2026-03-31). It carries scripts/codemap.py and the eleven bundled
parsers/*.so grammars. The release is the snapshot; nothing in this directory
reproduces it.
Note that v0.8.0 ships a latent bug: codemap.py:1216 calls an unimported
get_parser() inside a try swallowed by a bare except Exception, so HTML
inline-JavaScript symbol extraction silently returned nothing. It will not be
fixed.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
The English summary is being prepared. Showing the original description.
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe (evaluator-as-selector, stop on regression). Routes on measured cost-per-completed-task rather than per-token price, because a tier's token count varies more by task shape than price varies across tiers. Covers per-model effort semantics, the concision lever, cascade preconditions, context handoff, and watching a subagent fan-out live. Use when choosing a subagent's model or effort, when choosing how to escalate a failed attempt, or when asked which model or effort a task should get. Grounded in a 2026-07 calibration, a 2026-08 coding-cost study, a 2026-09 seeded-bug repair battery, a 2026-10 Haiku 5.5 ladder priced per spawn, and a 2026-10 retry-versus-escalation ladder on 295 SWE-bench Verified tasks; Managed Agents API specifics are operational, not calibrated.
The English summary is being prepared. Showing the original description.
Securely manages API credentials for multiple providers (Anthropic Claude, Google Gemini, GitHub). Use when skills need to access stored API keys for external service invocations.
The English summary is being prepared. Showing the original description.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
The English summary is being prepared. Showing the original description.
Pre-change blast-radius report for a symbol or file. Walks tree-sitting references, augments with a plain-text scan over non-parsed files (configs, plain docs), and clusters affected sites by feature (`_FEATURES.md`) or top-level package. Use when about to refactor, rename, or delete something in a repo you don't own — "what breaks if I change `validateUser`", "who calls this", "is this safe to remove", "where is this used", "blast radius", "impact analysis". This is the CONVERGENT pre-change risk skill — for "what is this repo?" use exploring-codebases; for "where is X?" use searching-codebases.
The English summary is being prepared. Showing the original description.
Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.
The English summary is being prepared. Showing the original description.