dev-tools
Skill532 starsChanged 49 days agoMITView on GitHub
Route and configure the repository's optional developer tools, check generated host adapters and distinguish configuration from verified connections.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ztrange/claude-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ztrange/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- go-b2b-starter/AGENTS.mdAGENTS.md
- next_b2b_starter/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- go-b2b-starter/CLAUDE.mdCLAUDE.md
- next_b2b_starter/CLAUDE.mdCLAUDE.md
- orchestrationSkill
- pr-reviewSkill
- service-connectionsSkill
- dev-toolsSkill
- orchestrationSkill
- pr-reviewSkill
- service-connectionsSkill
The file
We split this skill 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
- Very specific: line 8
Read AGENTS.md, .agents/tools.json and docs/AI_TOOLS.md.
- Distinctive: line 14
Run these from the repository root, or invoke the scripts by absolute path:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Developer tool routing
Read AGENTS.md, .agents/tools.json and docs/AI_TOOLS.md. The catalog owns
exact pins and selections; each project's adapters expose its allowed subset.
Root coordinates tool configuration. Go gets documentation tools; Next.js also
gets local development tools. Provider administration stays in the authorized
main session and is never inherited by implementation or reviewer roles.
Run these from the repository root, or invoke the scripts by absolute path:
node scripts/harness.mjs tools
node scripts/harness.mjs sync
node scripts/harness.mjs check
node --test scripts/harness.test.mjs scripts/mcp-probe.test.mjsEdit the canonical catalog for requested selections; never edit generated adapters
or global settings. Prefer an existing working host integration. A local MCP may
fetch its pinned executable on first launch. node scripts/mcp-probe.mjs <id>
initializes and lists a selected local tool only; it does not verify app behavior.
Route Go work to go-b2b-starter/.agents/skills/go-backend/SKILL.md, frontend
runtime/component/browser work to
next_b2b_starter/.agents/skills/frontend-tools/SKILL.md, Better Auth guidance to
next_b2b_starter/.agents/skills/auth-integration/SKILL.md, and requested provider
connections to .agents/skills/service-connections/SKILL.md.
Reviewer adapters expose documentation tools only. Inspect unrelated inherited host/plugin capabilities before delegation. Keep private source, credentials, cookies and customer records out of documentation queries. Report configuration, initialization and actual local/provider verification as separate outcomes.
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.