c456-cli
Original:🇨🇳 Chinese
Translated
Operate C456 via the c456 Node CLI (HTTP API v1): intakes, playbooks, search, fetch, and config. Use this when the user mentions C456, c456-cli, intake, playbook, c456.com, or syncing content with a self-hosted C456.
4installs
Sourcexiaohui-zhangxh/c456-cli
Added on
NPX Install
npx skill4agent add xiaohui-zhangxh/c456-cli c456-cliTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →C456 CLI (c456-cli)
Call C456's HTTP API v1 via in the terminal, allowing Agents to write/query content in C456 without manually writing raw REST details in conversations.
c456Install the CLI
Use or if not installed; use directly if installed globally.
npx c456-cli …bunx c456-cli …c456Install This Skill (for Other Repositories)
Run the following in the root directory of the target project (add to install to the user directory, or to specify the client as needed):
-g--agent cursorbash
npx skills add xiaohui-zhangxh/c456-cli --skill c456-cli -yIf you have cloned the c456-cli repository, run the following in the root directory of that repository:
bash
npx skills add . --skill c456-cli -yList available skills in the remote package without installing:
npx skills add xiaohui-zhangxh/c456-cli -lAuthentication and Site
| Method | Description |
|---|---|
| API Key | |
| Site Root URL | Defaults to |
Short Option Conflict: In subcommands, stands for intake type (kind). Do not use to pass the API Key. The Key can only be set via / .
-k-kconfigC456_API_KEY-B-u-B--base-urlintake-uAgent Execution Method
- When real read/write operations on C456 are required, run subcommands in the sandbox/terminal and parse their standard output (including the
c456section attached to some commands).--- JSON --- - Add /
-fto commands like--forcein non-interactive scenarios to avoid waiting for terminal confirmation (still confirm the user's intent before deletion).intake delete - Do not echo the full API Key in logs or responses.
- Never fabricate parameters: Only use options explicitly documented in (or the source code/docs of this repository); run
c456 <command> --helpfirst if unsure.--help
Command Quick Reference
Configuration
- /
c456 config set-key <token>/c456 config set-url <url>/c456 config showc456 config reset
Intake
intake- Create:
c456 intake new [-k signal|tool|channel] [-u <url>] [-t title] [-b content] - View / Update / Delete / List: ·
c456 intake show <id>·c456 intake update <id> …·c456 intake delete <id> [-f]c456 intake list [-k] [-q] [-p page] [-n per-page]
Search
searchc456 search signals -q "…" [-k kind] [-l n]c456 search playbooks -q "…" [-l n]
Playbook
playbook- Create:
c456 playbook new -t "title" [-b 'Markdown'] [--ref-intake id …] [--ref-playbook id …] - Additional commands: /
show/list/update(consistent withdelete)c456 playbook --help
Fetch
fetch- (
c456 fetch profile -u <url> -p <profile_id>is required; otherwise the API returns "unsupported profile type")profile_id c456 fetch detect -u <url>
Notes on :
fetch detect- It calls to create an intake with
POST /api/v1/intakes, and the server will attempt to automatically parse the data section.kind=tool - It is not a substitute for automatically inferring the for
profile_id; for social account homepages (e.g., YouTube), directly use:fetch profile.c456 fetch profile -p social_account -u "<url>"
Meaning of types:
profile_id- : Product/official website and other ordinary link pages (parses name/icon/description)
link_product - : Software package pages (npm, RubyGems, etc.)
package_registry - : Code repositories (GitHub/GitLab/Gitee)
github_origin - : Social account homepages/channels (YouTube/Douyin/Xiaohongshu, etc.)
social_account
More Complete Documentation
See the of each command and the and files in this repository.
--helpREADME.mdDEVELOPMENT.mdPagination Parameters (List Commands)
- : 1-10000
-p, --page - : 1-100 (default 20; the server will truncate it to the maximum value)
-n, --per-page
Content Syntax (Rich Text)
The CLI uses to mark field types; when generating/writing content, Agents must select the syntax and constraints according to the following table:
--helptype: <type_name>- →
markdown_kramdownreferences/content-syntax-kramdown.md