Tools Filing
Tools, services, libraries, CLIs, MCPs, frameworks, platforms, and vendor ecosystems go in
tools/.
Resolver Status
This is a resolver companion page. The canonical filing rule lives in Filing Decision Tree. Use Wiki Brain Operating Model first to decide whether the knowledge should become a standalone page, section, ledger row, generated view, redirect, or no durable write. Then use this page as a compact retrieval handle for the local rule. Source: User request, 2026-07-01
File Here
- Independent capabilities that exist outside this wiki: tools, services, SDKs, CLIs, frameworks, MCPs, platforms, vendors, and ecosystems.
- Capability summaries, setup notes, tradeoffs, alternatives, version/currentness notes, and verification routes.
Do Not File Here
- Repeatable HOW-to procedures: create or update an executable skill.
- Product/company context Kevin is building around: use
projects/. - General reusable theory: use
concepts/.
Activation Rule
A promoted tool capture is not done until the relevant action surface is updated: Capability Routing Map, Skill Resolver, Active Stack (What to Actually Use), wiki/tools/README.md, Actionable Tools Index, trigger evals, or harness projection when applicable.
Closeout
If this rule changes, update Filing Decision Tree first, then this companion page, relevant directory READMEs, generated packs if routing changed, wiki/_index.md, qmd, and wiki/log.md. Source: Index Logging Protocol, 2026-07-01
Timeline
- 2026-07-01 | Updated this resolver companion to align with the current filing authority stack: Wiki Brain Operating Model for shape, Filing Decision Tree for directory placement, and Index Logging Protocol for closeout. Source: User request, 2026-07-01
- 2026-05-31 | Tools filing from RESOLVER. Source: public wiki expansion, 2026-05-31