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
Added on

NPX Install

npx skill4agent add xiaohui-zhangxh/c456-cli c456-cli

Tags

Translated version includes tags in frontmatter

SKILL.md Content (Chinese)

View Translation Comparison →

C456 CLI (c456-cli)

Call C456's HTTP API v1 via
c456
in the terminal, allowing Agents to write/query content in C456 without manually writing raw REST details in conversations.

Install the CLI

Use
npx c456-cli …
or
bunx c456-cli …
if not installed; use
c456
directly if installed globally.

Install This Skill (for Other Repositories)

Run the following in the root directory of the target project (add
-g
to install to the user directory, or
--agent cursor
to specify the client as needed):
bash
npx skills add xiaohui-zhangxh/c456-cli --skill c456-cli -y
If you have cloned the c456-cli repository, run the following in the root directory of that repository:
bash
npx skills add . --skill c456-cli -y
List available skills in the remote package without installing:
npx skills add xiaohui-zhangxh/c456-cli -l

Authentication and Site

MethodDescription
API Key
c456 config set-key <token>
or the environment variable
C456_API_KEY
Site Root URLDefaults to
https://c456.com
; for self-hosted instances, use
c456 config set-url <url>
,
C456_URL
, or the one-time command
c456 -B <url> …
Short Option Conflict: In subcommands,
-k
stands for intake type (kind)
. Do not use
-k
to pass the API Key. The Key can only be set via
config
/
C456_API_KEY
.
-B
vs
-u
: The root-level
-B
/
--base-url
refers to the C456 site root address; in subcommands like
intake
,
-u
usually means "target resource URL"
(e.g., links to tools/channels), do not confuse them.

Agent Execution Method

  1. When real read/write operations on C456 are required, run
    c456
    subcommands in the sandbox/terminal and parse their standard output (including the
    --- JSON ---
    section attached to some commands).
  2. Add
    -f
    /
    --force
    to commands like
    intake delete
    in non-interactive scenarios to avoid waiting for terminal confirmation (still confirm the user's intent before deletion).
  3. Do not echo the full API Key in logs or responses.
  4. Never fabricate parameters: Only use options explicitly documented in
    c456 <command> --help
    (or the source code/docs of this repository); run
    --help
    first if unsure.

Command Quick Reference

Configuration
  • c456 config set-key <token>
    /
    c456 config set-url <url>
    /
    c456 config show
    /
    c456 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
search
  • c456 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
    /
    delete
    (consistent with
    c456 playbook --help
    )
Fetch
fetch
  • c456 fetch profile -u <url> -p <profile_id>
    (
    profile_id
    is required; otherwise the API returns "unsupported profile type")
  • c456 fetch detect -u <url>
Notes on
fetch detect
:
  • It calls
    POST /api/v1/intakes
    to create an intake with
    kind=tool
    , and the server will attempt to automatically parse the data section.
  • It is not a substitute for automatically inferring the
    profile_id
    for
    fetch profile
    ; for social account homepages (e.g., YouTube), directly use:
    c456 fetch profile -p social_account -u "<url>"
    .
Meaning of
profile_id
types:
  • link_product
    : Product/official website and other ordinary link pages (parses name/icon/description)
  • package_registry
    : Software package pages (npm, RubyGems, etc.)
  • github_origin
    : Code repositories (GitHub/GitLab/Gitee)
  • social_account
    : Social account homepages/channels (YouTube/Douyin/Xiaohongshu, etc.)

More Complete Documentation

See the
--help
of each command and the
README.md
and
DEVELOPMENT.md
files in this repository.

Pagination Parameters (List Commands)

  • -p, --page
    : 1-10000
  • -n, --per-page
    : 1-100 (default 20; the server will truncate it to the maximum value)

Content Syntax (Rich Text)

The CLI
--help
uses
type: <type_name>
to mark field types; when generating/writing content, Agents must select the syntax and constraints according to the following table:
  • markdown_kramdown
    references/content-syntax-kramdown.md