Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ccplugins/environment-memory
Use before retrying any command, tool, or approach that failed once, and immediately after discovering any OS/shell/tool-specific quirk — checks and updates a stable cross-project quirks file so failed approaches are never silently repeated.
Passed 11 of 18 test cases with the skill, and 6 of 18 without it.
and 5 more in the full report
7 fixed8 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to log a quirk where python3 -m venv fails on Ubuntu unless python3-venv is installed. Generate the exact entry string to add to ~/.claude/craftsman-memory/environment-quirks.md.
| Checked | Without skill | With skill |
|---|---|---|
| Writes the record as a single line without line breaks. | Missed | Passed |
The instructions your model reads when the skill loads.
Trial-and-error against the same broken assumption — "maybe bash works this time" — wastes turns and tokens without new information. Any OS, shell, or tool quirk discovered once should be usable forever after, in every project, not just the one where it was found.
Core principle: a quirk discovered once should never be rediscovered by trial and error.
~/.claude/craftsman-memory/environment-quirks.md — deliberately outside this plugin's own
install directory, so a plugin update never wipes it. Deliberately outside any single project's
memory folder too, since quirks like "hooks run via CMD.exe not bash on this machine" apply
everywhere, not just to the project where they were found.
Format: flat, append-only, one line per entry —
<symptom> → <fix> (discovered: <date>, context: <where>)
No YAML frontmatter, no index, no categorization — this file is meant to be read in full whenever it's relevant, so keep it short and skimmable rather than structured for querying (token-cheap by design).
~/.claude/craftsman-memory/environment-quirks.md for a matching symptom before trying
the same thing a second way, or a different way that might hit the same underlying constraint
(e.g. "PowerShell syntax works where bash syntax silently no-ops" applies to any bash-syntax
attempt, not just the exact command that first failed).KNOWN_ISSUES.md for the project instead).test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.