Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jordancoin/config-setup
Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo.
Passed 6 of 16 test cases with the skill, and 10 of 16 without it.
3 fixed9 passed either way5 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to write a `.codemap/config.json` for a repository, but we haven't checked its structure yet. What command should be executed first before writing configuration rules?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends executing codemap . prior to writing configuration rules. | Missed | Passed |
The instructions your model reads when the skill loads.
Write or improve .codemap/config.json so future Codemap calls stay focused on the code that matters for this repo.
.codemap/config.json is missingInspect the repo quickly before writing config
codemap .codemap --deps .Cargo.toml, Package.swift, *.xcodeproj, go.mod, package.json, pyproject.toml, etc.)Decide whether config is missing, boilerplate, or tuned
.codemap/config.jsononly values, no real shaping, no excludes despite obvious noiseWrite a conservative code-first config
only values when they helpexclude entries for obvious non-code noisedepth when the repo is broadPrefer stack-aware defaults
src, tests, benches, examples; de-prioritize corpora, sample PDFs, training data, large generated artifacts.xcassets, screenshots, snapshots, vendor/build outputssrc, apps, packages, tests; de-prioritize dist, coverage, Storybook assets, large fixture payloadsPreserve user intent
test cases passed, vs 10 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.