Document connections.list result shape in skills.ts - #1808
Open
baggiiiie wants to merge 1 commit into
Open
Conversation
baggiiiie
force-pushed
the
connections-list-result-shape
branch
from
August 28, 2026 13:01
49eb2c0 to
62ffeba
Compare
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.
issue
when agents call
tools.executor.coreTools.connections.list({})the actual output iswhile
executeskill doesn't explicitly say where the connection array is inside the{ok , data}envelope.i have observed that agents almost always tend to write code like:
which gives an error, as
conn.integrationis invalid.fix
i've added instructions in skills to document how to deal with results from
tools.executor.coreTools.connections.list({}). been running this local build for a week now, have seen significant improvements on this, no mistake at all across 50+ calls! hence im opening this PR