clawdi 0.13.2 → 0.13.3

package/dist/skills/clawdi/SKILL.md

@@ -79,12 +79,38 @@ When the user's request is **conceptual** ("how do I usually do X"), prefer `mem
 
 ## Connectors
 
-Connected service tools (Gmail, GitHub, Notion, etc.) are dynamically registered from the user's Clawdi Cloud dashboard. They appear as individual tools like `gmail_fetch_emails`, `github_list_issues`, etc.
-
-- These tools are already authenticated — no OAuth needed at runtime
-- If a tool call fails with "No connected account", tell the user to connect the service in the Clawdi Cloud dashboard
-- File downloads from connectors return signed URLs — download them with `curl` or `fetch` before processing
-- Confirm with the user before side-effecting operations (sending email, creating issues, etc.)
+Use the Composio Tool Router meta-tools returned by `tools/list` on the `clawdi` MCP server.
+Treat their live names and schemas as authoritative; never assume a fixed meta-tool set.
+
+1. Start each external-app workflow with `COMPOSIO_SEARCH_TOOLS`. Follow its exposed
+   `queries` and `session` schema, reuse the returned session ID throughout that workflow,
+   and use only the exact toolkit and tool slugs it returns. If a required schema is absent
+   or incomplete, call `COMPOSIO_GET_TOOL_SCHEMAS`; never invent fields or inputs.
+2. Before a side effect, require a complete target identity and all schema-required inputs.
+   Explicit intent authorizes the exact requested action and target, but never authorizes
+   guessing a missing recipient, account, resource, or other target. Ask only for what is
+   missing, and do not request redundant confirmation once the exact action is authorized.
+3. When search reports no active connection, call `COMPOSIO_MANAGE_CONNECTIONS` with its
+   exposed schema and interpret only the fields it returns. Continue on `active`. On
+   `initiated`, present its non-empty `redirect_url` as a clickable authentication link with
+   a concise explanation that authorization is pending; the link URL must be exactly that
+   value. If `initiated` has no non-empty `redirect_url`, report that authorization cannot
+   continue and stop. On `failed`, report the returned error and stop. Never construct a
+   substitute link, ask for OAuth credentials, API keys, or tokens, or suggest an
+   out-of-band fallback.
+4. Use a wait or status operation only when `tools/list` exposes one. Follow its actual schema
+   and status values without inventing polling arguments. Continue only when it reports an
+   active connection; keep waiting only for a non-terminal status its schema defines, and
+   report any terminal failure. If none is exposed, stop until the user reports completing
+   authorization, then re-run search to verify the active connection before continuing.
+5. Execute exact returned slugs through `COMPOSIO_MULTI_EXECUTE_TOOL` with schema-compliant
+   arguments. Batch only independent calls. Keep ordinary results inline. Set
+   `sync_response_to_workbench` only when a result may be large or needs later remote
+   processing; use `COMPOSIO_REMOTE_WORKBENCH` / `COMPOSIO_REMOTE_BASH_TOOL` only for large
+   responses saved remotely or remote artifacts.
+6. Preserve dependencies and returned semantics. Follow signed-file metadata, pagination
+   fields, and termination signals exactly as exposed. Select an account only when the schema
+   supports it, and use additional or future meta-tools only according to their live schemas.
 
 ## Vault CLI
 

package/dist/skills/hosted/clawdi/SKILL.md

@@ -18,12 +18,35 @@ session. Do not use a generic web fetcher for Clawdi share URLs.
 
 ## Connectors
 
-Connected-service tools are registered dynamically from the user's Clawdi Cloud account.
-They can include Gmail, GitHub, Notion, Drive, Calendar, and other services.
-
-- Treat the tools as already authenticated for this runtime.
-- If a call reports that no account is connected, ask the user to connect that service in
-  the Clawdi Cloud dashboard.
-- Download files returned as signed URLs before processing them.
-- Confirm with the user before side-effecting actions such as sending mail or creating an
-  issue.
+Use the Composio Tool Router meta-tools returned by `tools/list` on the `clawdi` MCP server.
+Treat their live names and schemas as authoritative; never assume a fixed meta-tool set.
+
+1. Start each external-app workflow with `COMPOSIO_SEARCH_TOOLS`. Follow its exposed
+   `queries` and `session` schema, reuse the returned session ID throughout that workflow,
+   and use only the exact toolkit and tool slugs it returns. If a required schema is absent
+   or incomplete, call `COMPOSIO_GET_TOOL_SCHEMAS`; never invent fields or inputs.
+2. Before a side effect, require a complete target identity and all schema-required inputs.
+   Explicit intent authorizes the exact requested action and target, but never authorizes
+   guessing a missing recipient, account, resource, or other target. Ask only for what is
+   missing, and do not request redundant confirmation once the exact action is authorized.
+3. When search reports no active connection, call `COMPOSIO_MANAGE_CONNECTIONS` with its
+   exposed schema and interpret only the fields it returns. Continue on `active`. On
+   `initiated`, present its non-empty `redirect_url` as a clickable authentication link with
+   a concise explanation that authorization is pending; the link URL must be exactly that
+   value. If `initiated` has no non-empty `redirect_url`, report that authorization cannot
+   continue and stop. On `failed`, report the returned error and stop. Never construct a
+   substitute link, ask for OAuth credentials, API keys, or tokens, or suggest an
+   out-of-band fallback.
+4. Use a wait or status operation only when `tools/list` exposes one. Follow its actual schema
+   and status values without inventing polling arguments. Continue only when it reports an
+   active connection; keep waiting only for a non-terminal status its schema defines, and
+   report any terminal failure. If none is exposed, stop until the user reports completing
+   authorization, then re-run search to verify the active connection before continuing.
+5. Execute exact returned slugs through `COMPOSIO_MULTI_EXECUTE_TOOL` with schema-compliant
+   arguments. Batch only independent calls. Keep ordinary results inline. Set
+   `sync_response_to_workbench` only when a result may be large or needs later remote
+   processing; use `COMPOSIO_REMOTE_WORKBENCH` / `COMPOSIO_REMOTE_BASH_TOOL` only for large
+   responses saved remotely or remote artifacts.
+6. Preserve dependencies and returned semantics. Follow signed-file metadata, pagination
+   fields, and termination signals exactly as exposed. Select an account only when the schema
+   supports it, and use additional or future meta-tools only according to their live schemas.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "clawdi",
-	"version": "0.13.2",
+	"version": "0.13.3",
 	"description": "iCloud for AI Agents — cross-agent sessions, skills, memory, and vault.",
 	"license": "MIT",
 	"type": "module",
@@ -23,7 +23,7 @@
 	},
 	"scripts": {
 		"dev": "bun run src/index.ts",
-		"build": "rm -rf dist && bun build src/index.ts --outdir dist --target node --minify --define 'process.env.CLAWDI_DEFAULT_API_URL=\"https://cloud-api.clawdi.ai\"' && cp -r skills dist/skills",
+		"build": "rm -rf dist && bun build src/index.ts --outdir dist --target node --minify --define 'process.env.CLAWDI_DEFAULT_API_URL=\"https://cloud-api.clawdi.ai\"' --define 'process.env.CLAWDI_DEFAULT_DEPLOY_API_URL=\"https://api.clawdi.ai\"' && cp -r skills dist/skills",
 		"build:binary": "bun run scripts/build-binary.mjs",
 		"package:binary-release": "bun run scripts/package-binary-release.mjs",
 		"build:dev": "rm -rf dist && bun build src/index.ts --outdir dist --target node && cp -r skills dist/skills",