Dépôts renommés avec le préfixe aimsight- : chemins et noms mis à jour

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 14:56:41 +01:00
1 parent fff7c7df70
commit 36ca927998
2 files changed
+6 -6

No files matched your search

+1 -1
View File
@@ -5,7 +5,7 @@ agents: the generic AIMsight agents, as a Claude Code plugin (`README.md`). An a
- Nothing specific to a caller in an agent: output paths, report format, the caller's git rules go through the request or through the instruction file it names (for the analyst, `INSTRUCTIONS`).
- A new parameter of an agent enters the README table in the same change; a caller that changes its request says so in its own docs.
- The agents run everything from the caller's root (links `data/`, `labeling/`, `tools/`, `detectors/`); they never write here.
- **Check a change**: load the agent on a short question, `claude -p "<question>" --plugin-dir ~/agents --agent agents:<name> --model haiku`, then a real launch by the caller.
- **Check a change**: load the agent on a short question, `claude -p "<question>" --plugin-dir ~/aimsight-agents --agent agents:<name> --model haiku`, then a real launch by the caller.
Rules:
- Every time is UTC; no rule specific to a station, a target or a date; never read `.env` nor copy the metric identifiers (`SIM_CCID`, `ip*`).
+5 -5
View File
@@ -4,7 +4,7 @@ The generic AIMsight agents, one copy of each. An agent states only its trade he
| Agent | Its trade | Request parameters | Called by |
|---|---|---|---|
| `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>` | Diagnostic-App (`instructions/analyst.md`, `DETECTORS: no`) |
| `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`) |
@@ -13,11 +13,11 @@ The generic AIMsight agents, one copy of each. An agent states only its trade he
The repository is a Claude Code plugin (`.claude-plugin/plugin.json`), loaded read-only:
```bash
claude -p "<request>" --plugin-dir ~/agents --agent agents:analyst
claude -p "<request>" --plugin-dir ~/aimsight-agents --agent agents:analyst
```
In a workflow, through the Agent tool: `subagent_type: agents:upgrader`, with `--plugin-dir ~/agents` when the session is launched.
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/` (`~/labeling`), `tools/` (`~/tools`), and `detectors/` (`~/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.
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.
Taken on 2026-11-16 from Diagnostic-App (`analyst`, `tool-builder`, commit dd6f1bf) and from detectors (`upgrader`, `validator`, commit 5438b0b); the same day, the upgrader and the validator were made generic on a target and the tool-builder folded into the upgrader (`docs/superpowers/specs/2026-11-16-generic-agents-design.md`). The architecture of the repositories: `~/Diagnostic-App/docs/architecture.drawio`.
Taken on 2026-11-16 from aimsight-app (`analyst`, `tool-builder`, commit dd6f1bf) and from detectors (`upgrader`, `validator`, commit 5438b0b); the same day, the upgrader and the validator were made generic on a target and the tool-builder folded into the upgrader (`docs/superpowers/specs/2026-11-16-generic-agents-design.md`). The architecture of the repositories: `~/aimsight-app/docs/architecture.drawio`.