qoder-cloud-agents
Installation
SKILL.md
Qoder Cloud Agents
Choose MCP or HTTP
- Prefer the configured QCA MCP tools for the requested region/environment. Discover their actual names and argument schemas; see MCP calling guide.
- If MCP is absent or unconfigured, or the user requests HTTP, follow HTTP setup and workflows. Connected MCP errors and uncertain writes do not trigger automatic HTTP retries.
- Use this edition's regional endpoints. Keep the selected account, environment and resource region consistent.
- For MCP credential setup, read MCP authentication. HTTP uses separately configured local PAT/SAT credentials; a plugin PAT form does not automatically supply them. Never ask for tokens in chat.
Choose the workflow
| Task | Workflow |
|---|---|
| Custom Agent or one-off cloud task | Managed: Agent + Environment → Session |
| Agent running on demand or on a schedule | Managed Deployment |
| Business assistant conversation | Forward: Template + Identity → Session |
| Recurring Template task for an Identity | Forward Schedule |
Keep resources in their original business layer. Forward needs an actual identity_id from user/application context or existing resources.