@devries-cameron20 / composio Mirror · read-only / commits / a09b619f3
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, 04:45 UTC

docs: tighten toolkit terminology wording

Jeevesh Jain committed Nov 16, 2026 at 16:05 UTC a09b619f3dfbf9ea6817af835fbe9df4a283e25e
2 files changed +1 -2
docs/lib/llm-guardrails/session.ts
+1 -1
@@ -28,7 +28,7 @@ export const SESSION_GUARDRAILS = `
28
29 ## 1. Recommended Integration: Sessions
30
31 -For agent tool delivery, Composio supports **direct tools through a provider package** (with a provider package) and **MCP** (no provider package needed).
31 +For agent tool delivery, Composio supports **direct tools** (through a provider package) and **MCP** (no provider package needed).
32
33 For application-owned tools or deterministic backend code, use [managed authentication with Proxy Execute](/docs/authentication/managed-auth-for-custom-tools). A session can provide a user-scoped runtime context without an LLM or MCP. Composio authenticates provider requests server-side; connected-account reads redact credentials and aren't a supported token-export workflow.
34
skills/composio/SKILL.md
-1
@@ -63,7 +63,6 @@ Do not turn an explanation, documentation lookup, or narrow bug fix into onboard
63 10. Prefer the smallest configuration that completes the current job. Keep toolkit filters, tag policies, approvals, Firewall hooks, Custom MCP toolkits, sandbox controls, custom auth, provider-specific hardening, and other advanced options out of the first path unless the request or existing code requires them. When the request does ask for one, such as "ask before sending" or "block prompt injection", use the documented feature instead of building a substitute in prompts or application code.
64 11. Do not invent repository facts. Never claim that a file, framework, environment loader, identity field, agent path, or dependency exists until it was provided or inspected. If codebase context is unavailable, state the unknown and ask for access or one necessary detail.
65 12. In SDK or API examples, use exact identifiers and call shapes from a current public page or schema. Copy the documented shape for the requested language instead of translating names between TypeScript and Python; if a required detail is not documented, explain the behavior without inventing code.
66 -
66 13. A product may ship both a Composio Built toolkit (`notion`) and a Provider MCP toolkit (`notion_mcp`) grouped as one App in the catalog. They are separate toolkits with separate connections. Use the slug the user or the code names; when the slug is unspecified, compare auth schemes, connected state, tool lists, and triggers, prefer the toolkit the user can authenticate, and state which one you chose. Never assume the `_mcp` toolkit is newer, larger, or shares a connection with its sibling.
67
68 ## Canonical information