Repository navigation
feat: release pi.bianqian 0.1.6 and pi.ssh-manager 0.1.6 with when-to-use tool descriptions - #67
Merged
vastsa merged 1 commit intoOct 6, 2026
Conversation
…-use tool descriptions Batch 2 of the tool-description trigger audit: lead every agent-tool description with explicit when-to-use trigger conditions and example phrasings (Chinese and English) so the agent picks the right tool from the user's goal instead of guessing. pi.bianqian gains a negative scope on create_note (todos and goals belong to pi.todo / pi.goal-x) and a hard rule that purge_note never serves an ordinary delete request; pi.ssh-manager states the override boundary that AI cannot authorize a blocked command — only the panel's one-time approval can.
|
@muzimu217 is attempting to deploy a commit to the vastsa's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
Why
Follow-up to #66 (session-orchestrator 0.6.1): an audit of all 31 agent-tool descriptions in this repository found that none stated when the tool should be used — official plugin/skill descriptions consistently pair a capability summary with "Use when…" trigger conditions, example phrasings and negative scope. Without them the agent has to guess which tool matches the user's goal. This is batch 2: pi.bianqian (8 tools) and pi.ssh-manager (4 tools).
What changed
pi.bianqian 0.1.6 — every tool description now leads with a trigger:
create_notegains a negative scope: structured todos belong to pi.todo, goals to pi.goal-x — a sticky note is for jotting things down.purge_notegains a hard rule: never serve an ordinary delete request (that isdelete_note); only explicit "permanently destroy" phrasing.delete_notepoints to the softer soft-delete path;get_notepoints tosearch_noteswhen the id is unknown.pi.ssh-manager 0.1.6 — same treatment, plus the security boundary stated in the description itself:
ssh_connect: only configured host profiles are addressable — never fabricate aprofile_id.ssh_execute: one bounded command per call; mutating/dangerous commands are statically blocked and AI cannot authorize an override — the agent must direct the user to the panel's one-time approval instead. Not for interactive shell sessions.Both are description-level releases (0.1.5 → 0.1.6); no behavior or permission changes. Changelogs and test version assertions updated.
Verification
Remaining plugins with un-triggered descriptions (next batches): pi.goal-x, pi.workspace-file-guard, demo.*.