Individual skill
detool
Make durable artifacts portable by replacing incidental stack, vendor, model, CLI, path, quota, or harness nouns with the mechanism they mean, while keeping provenance, runbooks, and tool-subject claims concrete.
skills/depth/detool/SKILL.md
Source commit 0b1e2c65231b3ce9294844362efae9b3a726e3ed
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,377
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- anti-slop Repository topic
- clean-code Repository topic
- hygiene Repository topic
- markdown Repository topic
- plugin Repository topic
- skills Repository topic
- ssot Repository topic
- evals Repository topic
- fable Repository topic
- design-patterns Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,578 bytes
Read excerpt
Remove incidental tool coupling from artifacts that claim to outlive the stack that wrote them.
## Goal
A durable artifact should stay true and actionable when the agent, harness, operating system, vendor, model, or toolchain changes. `detool` finds stack-specific nouns in portable content and rewrites them to the underlying mechanism without deleting the action they enabled.
The point is portability, not vagueness. A reader should still know what to inspect, run, measure, compare, or verify after the rewrite.
## Workflow
1. Read the target artifact end to end.
2. **Role before edit**: classify the whole artifact, or each section if mixed, as durable/portable content, provenance/operational record, or a claim about a named tool.
3. Sweep durable content for incidental coupling: harness paths, vendor CLIs and flags, model or product brands used as mechanisms, tool-specific environment variables, quotas, UI steps, cache homes, session files, and version-pinned behavior stated as timeless truth.
4. **Mechanism not euphemism**: replace each durable-content hit with the neutral mechanism that preserves the action. If neutral wording would lose the action, keep the concrete detail as an example of the mechanism instead of pretending it generalizes.