菜单
Access, search, analyze, and submit CoC conversation process records via REST API to a running CoC server (chat, run-workflow, run-script, follow-up, stream, search, list, stats). Use when the user asks to find, read, search, summarize, analyze, submit, or send tasks to CoC.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | coc-chat |
| description | Access, search, analyze, and submit CoC conversation process records via REST API to a running CoC server (chat, run-workflow, run-script, follow-up, stream, search, list, stats). Use when the user asks to find, read, search, summarize, analyze, submit, or send tasks to CoC. |
| metadata | {"version":"0.0.1"} |
Unified CLI for querying and submitting CoC conversation process records. All commands communicate with a running coc serve instance via REST API.
python <skill-dir>/scripts/coc_chat.py <command> [args...]
Read references/reference.md for the full command reference, REST API schemas, SSE streaming protocol, and examples.
| Goal | Command |
|---|---|
| List workspaces | workspaces |
| List recent chats | list <wsId> --limit 10 |
| Read a conversation | show <wsId> <pid> or conversation <wsId> <pid> |
| Search titles | search <keyword> |
| Full-text content search | search-content <keyword> [--workspace <id>] [--status …] [--type …] |
| Aggregate stats | stats [wsId] |
| Token usage report | token-usage --days 7 |
| Task history | history --workspace <wsId> |
| Submit a chat | chat <prompt> --workspace <wsId> |
| Stream output | stream <processId> |
| Send follow-up | follow-up <processId> <message> |
| Run a workflow | run-workflow <path> --workdir <dir> |
| Check status | status <processId> |
| Flag | Description |
|---|---|
--base-url <url> | Server URL (default: http://localhost:4000, or COC_SERVER_URL env) |
--workspace <id> | Workspace ID (e.g. ws-1a2b3c) |
--json | Output raw JSON response |
--limit <n> | Max results (default 20) |
<skill-dir> is the directory containing this SKILL.md file.
Comprehensive reference for CoC (Copilot of Copilot) architecture — server, memory system, LLM tools, SDK wrapper, process store, workflow engine, deep-wiki, and dashboard SPA. Use whenever the user asks anything related to CoC (Copilot of Copilot), forge, deep-wiki, coc-client, the CoC server, dashboard, workflow engine, memory system, LLM tools, process store, or any of their subsystems. Also use whenever you need background knowledge to answer a question, plan a change, or ground your reasoning in this codebase — read the relevant reference file(s) under `references/` before responding. Use when building, modifying, debugging, or explaining CoC features, or when understanding how subsystems interact.
Submit a single commit or a range of commits as a new GitHub pull request. Cherry-picks the commits onto a fresh branch off the latest origin/main, pushes, opens the PR via `gh`, and enables auto-merge by default. On any cherry-pick/rebase conflict the script aborts the entire submit; the AI must NOT attempt to resolve conflicts. Use when the user asks to "open a PR for this commit", "send commits X..Y as a PR", "PR-ify these commits", or similar.
Schedule recurring follow-up messages into the current conversation. Supports fixed-interval monitoring and one-shot wakeups for dynamic self-pacing.
MUST BE LOADED for any code change in this repository. Implements the requested code change and adds comprehensive test coverage, ensuring tests pass across Linux, macOS, and Windows. Use whenever you are about to modify, add, refactor, fix, or delete source code in this repo — including bug fixes, feature work, refactors, and small tweaks. Use when you need to execute implementation work (not just planning) and must include tests. Commit the changes to the repository after the implementation is complete.
Delegate a job from the current chat to a new conversation. Use when the user asks to delegate or hand off work.
Draft a user experience specification for a requested CoC feature. Use when planning new features, designing user flows, or creating UX specs for the CoC dashboard, CLI, server, or Node packages.