dynamo-probe
Skill1 starsChanged 35 days agoNo licenceView on GitHub
Measure whether a Dynamo task actually stumps the reference model, by running pass@2 cycles through the cycle wrapper, classifying verdicts, recording solve traces and deciding whether to harden or hop to a different stump pattern. Use this when a design has passed the mutant gauntlet and the visible-oracle certificate and is ready to be probed, when reading the result of a probe, when deciding whether a design is done or needs another cycle, or when the user asks how hard the task is or what the pass rate was. After a valid failure it hands off to dynamo-submission for the deliverables. Do not use it to judge difficulty from a subagent's attempt: only the context-free channel measures anything.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-reconcileSkill
- change-scoperSkill
- codebase-cartographerSkill
- commit-conventionsSkill
- debuggerSkill
- dynamo-bootstrapSkill
- dynamo-bootstrapSkill
- dynamo-designSkill
- dynamo-designSkill
- dynamo-probeSkill
- dynamo-rebuildSkill
- dynamo-rebuildSkill
- dynamo-repairSkill
- dynamo-repairSkill
- dynamo-reworkSkill
- dynamo-submissionSkill
- dynamo-submissionSkill
- dynamo-verifySkill
- dynamo-verifySkill
- feature-grafterSkill
- feature-integratorSkill
- grillingSkill
- intake-triageSkill
- phase-executorSkill
- pr-descriptionSkill
- product-architectSkill
- product-guideSkill
- product-state-initSkill
- quality-gateSkill
- refactor-stewardSkill
- regression-guardSkill
- root-cause-investigatorSkill
- safety-net-builderSkill
- surgical-fixerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.