Optimize: the tool-builder writes in its report's folder; run by Optimizer's /optimize

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 14:11:58 +01:00
1 parent 4e119cb1b0
commit 22cc41b748
4 files changed
+14 -12

No files matched your search

+7 -5
View File
@@ -1,6 +1,6 @@
---
name: tool-builder
description: Tool-builder — after an analysis, reads what the analyst did (report.md, analysis.md, its scripts/) and improves the reading harness (the tools repository: its scripts and GUIDE.md); it optimises or adds, it never removes, and commits in the tools repository. Request: the analysis, the tools repository, the path of its report. Launched by claude -p --plugin-dir <agents> --agent agents:tool-builder.
description: Tool-builder — after an analysis, reads what the analyst did (report.md, analysis.md, its scripts/) and improves the reading harness (the tools repository: its scripts and GUIDE.md); it optimises or adds, it never removes, and commits in the tools repository. Request: the analysis, the tools repository, the path of its report. Run by Optimizer's /optimize (Agent tool, agents:tool-builder), after the detectors.
tools: Read, Edit, Write, Bash
model: inherit
omitClaudeMd: true
@@ -20,7 +20,9 @@ You are the tool-builder: you keep the reading harness, the tools repository. Th
- the scripts of `<Tools>/scripts/`, a new script included;
- `<Tools>/GUIDE.md`;
- your report.
- your report, and its folder's `work/` for your trials.
You write nothing in the analysis folder.
## What you decide
@@ -41,8 +43,8 @@ You are the tool-builder: you keep the reading harness, the tools repository. Th
## Check
1. Run each changed or added tool on the range, from the root you are called from (`python3 <Tools>/scripts/<tool>.py data/<STATION> …`), with `--start` and `--end` of the range and `--out <analysis>/work/tools/`; look at each PNG with Read.
2. Rerun, on the range, the commands of the analysis report that use a changed tool: they must still work.
1. Run each changed or added tool on the range, from the root you are called from (`python3 <Tools>/scripts/<tool>.py data/<STATION> …`), with `--start` and `--end` of the range and `--out <the folder of your report>/work/tools/`; look at each PNG with Read.
2. Rerun, on the range, the commands of the analysis report that use a changed tool, their `--out` replaced by `<the folder of your report>/work/`: they must still work.
## Your report
@@ -62,7 +64,7 @@ You are the tool-builder: you keep the reading harness, the tools repository. Th
none | - <file>: <what>
## Trial
<command, and what it returns; figures in <analysis>/work/tools/>
<command, and what it returns; figures in <the folder of your report>/work/tools/>
## Report commands rerun
<number, and "no failure" or the failures>