Skip to content

Say where the extra skills actually came from - #17

Open
johnl-amd wants to merge 1 commit into
mainfrom
fix-extras-warning-source
Open

johnl-amd wants to merge 1 commit into
mainfrom
fix-extras-warning-source

Conversation

@johnl-amd

Copy link
Copy Markdown
Collaborator

The routing report told every reader that skills beyond the room came from the
runner's own config, and to set ANTHROPIC_API_KEY so the run could use an
isolated config dir.

On a run that already had the key set and recorded isolated_config_dir: true,
sixteen extras were still reported, and none of them were present in the runner's
~/.claude/skills. They were the agent CLI's own built-ins (code-review,
dataviz, loop, run, simplify, update-config, workflow-authoring, and
so on), which no config dir excludes.

So the warning named a cause it had not checked and prescribed a fix that was
already in place.

  • Isolation is already in the report metadata, so branch on it
  • Isolated run: say the extras ship with the agent CLI, that nothing removes
    them, and to read the scores with them in the room
  • Non-isolated run: original guidance, unchanged

Worth knowing either way, since the extras change every routing score and there
is currently no way to exclude the built-in ones.

The routing report told every reader that skills beyond the room came
from the runner's own config and to set ANTHROPIC_API_KEY so the run
could use an isolated config dir. On a run that already had the key set
and recorded isolated_config_dir true, sixteen extras were still
reported, none of them present in the runner's ~/.claude/skills: they
ship with the agent CLI, which no config dir excludes.

So the warning named a cause it had not checked and prescribed a fix
that was already in place.

Isolation is already recorded in the report metadata, so branch on it.
When the run was isolated the runner's own skills are out of the session
by construction and what remains ships with the CLI, which is worth
saying plainly along with the fact that nothing removes it. When it was
not, the original guidance still holds and is unchanged.

Signed-off-by: John Lybeck <john.lybeck@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant