← Back to Skills Marketplace
145
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install copaw-api-chat
Description
Communicate with a CoPaw instance through its HTTP API. Use when: (1) you need to inspect available CoPaw agents or chats, (2) create a chat or session and s...
README (SKILL.md)
CoPaw API Chat
Use this skill to work with CoPaw over HTTP API, not through the web UI.
When to use
- You need to talk to a local CoPaw instance programmatically.
- You need the correct sequence: create chat/session → send message → read SSE.
- You need to understand agent scoping, auth layers, or related API groups before building automation.
Workflow
- Read
references/overview-auth-scoping.mdfirst. - If the task is about chatting with CoPaw, then read
references/chats-console-sse.md. - If the task touches agent/model/skill/tool management, read
references/agents-models-skills-tools.md. - If the task touches workspace, MCP, or cron, read
references/workspace-mcp-cron.md. - If you need ready-to-run examples, read
references/practical-recipes.md.
Minimal practical path
- Confirm agent id (
defaultunless proven otherwise). - Create a chat with
POST /api/chats. - Reuse the returned
session_id/user_id/channelcontext. - Send the message with
POST /api/agents/{agentId}/console/chat. - Read the response as SSE.
Important rules
- Do not assume stateless request/response. CoPaw is chat/session-centric.
- Distinguish confirmed API behavior from interpretation.
- Prefer agent-scoped routes (
/api/agents/{agentId}/...) or setX-Agent-Idexplicitly. - In the current deployment, auth may be provided by nginx Basic Auth even if internal CoPaw auth is off.
- Treat
/api/workspaceand some/api/agents/*/files/*surfaces as dangerous/admin-level APIs.
References
references/overview-auth-scoping.md— API surface, auth, scoping, prioritiesreferences/chats-console-sse.md— chat lifecycle, session context, SSE mechanicsreferences/agents-models-skills-tools.md— management surfaces around agents/models/skills/toolsreferences/workspace-mcp-cron.md— workspace, MCP, cron boundaries and risksreferences/practical-recipes.md— short request examples and file structure examples
Output expectations
When using this skill, answer with:
- the minimal correct endpoint sequence,
- the required payload shape,
- auth/scoping caveats,
- and only the API groups relevant to the task.
Usage Guidance
This is an instruction-only skill for talking to a CoPaw HTTP API and appears coherent. Before using it: ensure you point requests at a trusted/local CoPaw instance (avoid exposing internal endpoints to the public internet); only provide Basic Auth or Bearer tokens when you trust the target server; avoid automating admin endpoints (/api/workspace, /api/mcp, /api/cron) unless you need admin tasks; and review any credentials you supply to other tools or scripts that call these endpoints. Because the skill is just documentation and examples, it won't install code, but the HTTP requests it recommends could be used to read or modify data on the target server — proceed with the usual caution when granting API access.
Capability Analysis
Type: OpenClaw Skill
Name: copaw-api-chat
Version: 0.1.0
The skill bundle provides documentation and instructions for an AI agent to interact with the CoPaw HTTP API. It includes structured workflows for session management, chat interactions via SSE, and administrative tasks, with explicit warnings in SKILL.md and workspace-mcp-cron.md regarding high-risk endpoints. No evidence of malicious intent, data exfiltration, or unauthorized execution was found.
Capability Assessment
Purpose & Capability
Name/description match the actual content: the SKILL.md and references describe API endpoints, chat/session flow, and admin surfaces. No unrelated binaries, credentials, or installs are requested.
Instruction Scope
Instructions stay on-topic (create chat → send message → read SSE). The references document admin-level endpoints and explicitly warn they are high-risk; that is appropriate caution rather than scope creep. The skill does not instruct reading local files or unrelated environment variables.
Install Mechanism
No install spec and no code files—instruction-only—so nothing is written to disk or downloaded during install.
Credentials
The skill declares no required env vars or credentials. It mentions possible Basic Auth or Bearer tokens in context (real API concerns) but does not request unrelated secrets or excessive environment access.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or modify other skills or system settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install copaw-api-chat - After installation, invoke the skill by name or use
/copaw-api-chat - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial public release: generalized CoPaw HTTP API chat integration skill, removed environment-specific examples, validated packaging.
Metadata
Frequently Asked Questions
What is CoPaw API Chat?
Communicate with a CoPaw instance through its HTTP API. Use when: (1) you need to inspect available CoPaw agents or chats, (2) create a chat or session and s... It is an AI Agent Skill for Claude Code / OpenClaw, with 145 downloads so far.
How do I install CoPaw API Chat?
Run "/install copaw-api-chat" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is CoPaw API Chat free?
Yes, CoPaw API Chat is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does CoPaw API Chat support?
CoPaw API Chat is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created CoPaw API Chat?
It is built and maintained by erview (@erview); the current version is v0.1.0.
More Skills