support: a generalist agent that does what it is asked, delegating a range's reading to the analyst
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
36ca927998
commit
7aaabfdca0
6 files changed
+275
-2
No files matched your search
@@ -7,6 +7,7 @@ The generic AIMsight agents, one copy of each. An agent states only its trade he
|
||||
| `analyst` | read a range like the expert and label it, with an analysis that justifies each label | station, range, hints, output folder, `DETECTORS: yes \| no` (with `yes`, `Events: <command>`), `INSTRUCTIONS: <file>` | aimsight-app (`instructions/analyst.md`, `DETECTORS: no`) |
|
||||
| `upgrader` | improve a target (a git repository) on the evidence given, without overfitting, one commit per fix | `Target`, `Evidence`, `Checks` (or `none`), `Base`, `Files already modified`, output folder, `INSTRUCTIONS: <file>` | Optimizer (`optimize` skill): the detectors (`instructions/upgrader-detectors.md`), then the tools (`instructions/upgrader-tools.md`) |
|
||||
| `validator` | judge an upgrader's change on the checks and the code, without its diagnosis: keep, remove some fixes, cancel | `Target`, `Modification`, `Base`, `Checks` (before, after, after each fix), output, `INSTRUCTIONS: <file>` | Optimizer, the detectors (`instructions/validator-detectors.md`) |
|
||||
| `support` | do what it is asked, as a generalist: answer a client or the expert, look into a station; it delegates a range's reading to the analyst (`claude -p` from a root of links in its folder) | `INSTRUCTIONS: <file>`, `Output folder` (both optional; else `~/aimsight-labeling/auto/support/<YYYY-MM-DD>_<subject>/`) | the user, from anywhere (`claude --plugin-dir ~/aimsight-agents --agent agents:support`) |
|
||||
|
||||
## Launching them
|
||||
|
||||
@@ -16,6 +17,12 @@ The repository is a Claude Code plugin (`.claude-plugin/plugin.json`), loaded re
|
||||
claude -p "<request>" --plugin-dir ~/aimsight-agents --agent agents:analyst
|
||||
```
|
||||
|
||||
The support is launched by the user from anywhere, isolated like the other agents' runs and given the repositories it reads and writes; it builds its own root of links in its folder:
|
||||
|
||||
```bash
|
||||
claude --plugin-dir ~/aimsight-agents --agent agents:support --setting-sources project,local --strict-mcp-config --add-dir ~/aimsight-labeling --add-dir ~/aimsight-data/data --add-dir ~/aimsight-tools --add-dir ~/aimsight-detectors --add-dir ~/aimsight-libredesk
|
||||
```
|
||||
|
||||
In a workflow, through the Agent tool: `subagent_type: agents:upgrader`, with `--plugin-dir ~/aimsight-agents` when the session is launched.
|
||||
|
||||
The caller launches from its root, which carries the links `data/` (the stations, `~/aimsight-data/data`), `labeling/` (`~/aimsight-labeling`), `tools/` (`~/aimsight-tools`), and `detectors/` (`~/aimsight-detectors`) when the agent needs it; it gives `--add-dir` on their real targets so that the agent can read or write there. Claude does not write into a loaded plugin: what gets written (the tools, the detectors, the sessions) lives in the other repositories, never here.
|
||||
|
||||
Reference in new issue
Block a user