Agent capabilities

Directory: sdk/agent-capability

Source docs/en/site/sdk-agent-capability.md

Directory: sdk/agent-capability Who this is for: letting a workspace agent call your business capability from Messages (face recognition, drawing, query a business API, and similar) — do not register platform_plugins, no apps-desktop iframe entry.

Voice: the user triggers the capability in a workspace conversation; you deliver an HTTP/MCP capability service + a workspace skill; Cadau runs it with an internet capability pack and built-in http_request.
Vs plugin apps: [../platform-plugin/README.md](/docs/sdk-platform-plugin) (full web on the apps desktop + launch_token).
Vs host embed: [../host-embed/README.md](/docs/sdk-host-embed) (embed assistant on a host business page).
Vs appsdk: [../appsdk/README.md](/docs/sdk-appsdk) (lightweight app pack inside a workspace, not a third-party HTTP capability service).

Doc version: 0.1 (mechanism source of truth; dedicated code package and scaffolding come later)

1. When to use this

| | Agent capabilities (this directory) | Plugin apps | |--|------------------------|--------------| | Where the user enters | Talks to a work assistant in Messages | Apps desktop tile → iframe | | Cadau side | Internet capability pack + skills + http_request | platform_plugins[], launch_token, knowledge sync | | What you deliver | Capability HTTP service (isolated by workspace_id) + SKILL.md | Web UI + API + platform-plugin/go | | Register platform_plugins | No | Yes |

Do not fill platform_plugins for a conversation-only API capability (that would add a useless iframe / launch_token / app entry).

2. Connection steps (current implementation)

Deploy a capability API (PostgreSQL/MySQL and similar; business tables isolated by workspace_id).
A workspace admin turns on the internet request capability pack (http_integration).
Write a workspace skill (SKILL.md): when to use it, how http_request calls your API, auth and params.
Install the skill into the workspace skill center (agents in the workspace can recall by default; do not rewrite each agent’s “available skills” narrow list by default).

Cadau does not auto-register a built-in tool name for every business API. The model calls your service through skill notes + http_request.

3. Combined with plugin apps

A plugin app can have all of these at once:

Capability	Path
UI and human operations	`platform-plugin`
Agents understand plugin background	Plugin knowledge sync → workspace `plugin-{module_id}/`
Step-by-step plugin-domain work from Messages	Plugin repo `skills/{slug}/` → skill center (`platform-plugin` §7.5)
Call an HTTP API outside the plugin from Messages	This directory §2 (skills + internet capability pack)

4. Decision tree

Need a full web UI on the apps desktop?
  ├─ No → agent capabilities: capability service + skills + internet capability pack (this directory)
  └─ Yes → plugin apps: platform-plugin
        ├─ Also need background notes in conversation? → knowledge/ sync
        ├─ Also need a procedural how-to? → skills/ shipped → skill center
        └─ Also need to call an external HTTP API from Messages? → add this directory §2

5. Further reading (mechanism source of truth)

Document	Notes
Workspace capability packs	Internet capability pack, `http_request`
Skill composition spec	`SKILL.md` contract, trigger notes
platform-plugin §7.5	Skills shipped with the plugin → skill center
sdk/README.md	Four-way SDK overview

6. Planned (not delivered)

The following are not yet a standalone code package or scaffolding. When you implement, still follow §2 and the mechanism docs:

[ ] Minimal capability-service template (HTTP + workspace_id auth example)
[ ] Skill-pack starter (SKILL.md + references/)
[ ] MCP adapter (if the product enables an MCP path)

Sibling SDKs: host-embed · platform-plugin · appsdk · this directory.