Repository navigation
feat: invoke a trusted skill for one console task - #335
Merged
Merged
Conversation
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
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.
Summary
/skill <qualified-id> <task>to the idle raw console. Parse only the command and identifier; submit the complete remaining task as literal text through the existing resolver and RunSession. The selected skill is scoped to that turn, including when ordinary tasks were already queued.--no-skills, and server-executed cloud chat invocations before an unrestricted model call. Show the resolved ID, digest, context size, and host tool limits;/context next /skill ...previews a fresh selection without admitting it.Evidence
npm run buildpassed.npm run docs:checkpassed; 6 generated outputs match.git diff --cached --checkpassed before commit./and!task text reaches the local model with the skill, while a normal queued turn has no inherited skill. Other fixtures prove local model failure and disabled-skill refusal do not make selection sticky, and cloud/--no-skillsrefusals make zero model requests.Closes #327
Refs #192