@devries-cameron20 / composio Mirror · read-only / commits / 2fb6eac35
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 09:45 UTC

docs(skill): refer Instant Tools questions to the guide (#4776)

## What changes Adds a short Instant Tools guide link to the Platform reference and asks the agent to check eligibility before requiring a connection. Actions needing authentication keep the existing Connect Link flow. ## Scope One reference file. No added policy framework, eval files, API schemas, prices, or SDK changes. The expanded skill changes were reverted at the author's request. Docs remain separate in #4770. ## Verification Restored the prior minimal revision. This is a documentation pointer change, not an end-to-end behavior verification.

palash-c committed Oct 12, 2026 at 16:35 UTC 2fb6eac358e34ddee4b893ef8818c155c4be5435
1 file changed +3 -1
skills/composio/references/platform.md
+3 -1
@@ -105,6 +105,8 @@ Pass the session tools to the repository's existing model or agent using its nat
105
106 ## Choose tools and authentication behavior
107
108 +For Instant Tools, read https://docs.composio.dev/docs/instant-tools.md before choosing authentication or usage settings. Use that guide for current eligibility, pricing, project access, Session controls, account routing, and charge reporting.
109 +
110 Sessions expose a small set of meta tools by default so the agent can discover integrations and authenticate at runtime:
111
112 - `COMPOSIO_SEARCH_TOOLS`
@@ -138,7 +140,7 @@ Do not force advanced requests through first-time setup. Route them to current d
140
141 For a first-time setup or integration request, success means a programmatic, safe, read-only tool call from the developer's real execution path returns an actual provider result and a non-empty Composio log ID.
142
141 -Ask which integration the developer wants to try unless the application already makes the choice clear. Discover the real toolkit and tool at runtime. If the current user is not connected, return the Connect Link, wait for authorization, and retry.
143 +Ask which integration the developer wants to try unless the application already makes the choice clear. Discover the real toolkit and tool at runtime. If the current user is not connected, check the Instant Tools guide before assuming a connection is required. When authentication is required, return the Connect Link, wait for authorization, and retry.
144
145 A mock, Playground run, tool search, schema fetch, session creation, or Connect Link alone does not prove the integration. If the repository has no runnable agent loop, add only the smallest entrypoint compatible with its existing provider; do not require another hosted model.
146