Two SKILL.md sentences reworded: close once the work is done and published; install only when the command fails for a missing node_modules - #1776
Merged
Conversation
…ished, not merged; install only when running the command fails for a missing node_modules Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UMVVNvrAaovKrXTG2wKcqy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two sentences in the skills' SKILL.md files sent agents the wrong way in the Q2 experiment (#1774).
"Once the work is merged" → "once the work is done and published." A plain agent run has no merge step. Opus read "merged" literally and stalled before committing, with its claims held. Two places in the tickets SKILL.md.
"With no
node_modules, install first" → "run asnpx …; when that fails for a missingnode_modules, install and run it again." Sonnet read the old sentence as an order and rannpm installbefore reading anything, in three runs. Now the install is a fallback on a failed run. Same sentence in the tickets, queue and logs SKILL.md; all three changed the same way.No code change. The framework's generated prompts pick the new text up at build.
Checked on the experiment's rig with the same prompt. Sonnet went straight to the commands, no
npm installattempt. Opus stopped before the close step in its run, so that run says nothing about the first change; under the rules prompt it closed correctly with the old wording too. The first change is a correction of the words, not a measured fix.🤖 automated · Fable 5.1