How do I install the Cpipe skill?

Run npx skillmds@latest add stefanwebb/cpipe in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cpipe skill do?

Use cpipe to discover, inspect, and send commands to named-pipe tool servers. It is listed under Coding & Dev Tools on SkillMD.

Is Cpipe safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cpipe?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cpipe free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

stefanwebb (@stefanwebb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cpipe by stefanwebb — Agent Skill

Name: Cpipe
Author: stefanwebb

File contents

Use cpipe to interact with ToolServer instances (servers following the tool-* pipe naming convention). Always activate the named-pipes conda environment first.

conda activate named-pipes

Discover running servers

cpipe --list          # list tool pipes (tool-* convention) under /tmp (fast, no process scan)
cpipe --pid           # same, but also show which PIDs have each pipe open
cpipe --clear         # delete orphaned tool pipes (no live process) under /tmp

Pass an optional directory to search a different root (e.g. cpipe --list /var/tmp).

Send commands to a tool server

cpipe <tool> <cmd>

<tool> is either a bare tool name (e.g. chat) — which resolves to /tmp/tool-chat — or a full pipe path. <cmd> is the command to send.

Built-in commands every tool supports

cpipe chat ping                 # health check — responds with "pong"
cpipe chat status               # current state of the server (e.g. "running")
cpipe chat description          # one-line description of the tool
cpipe chat help                 # full help text (SKILL.md content)
cpipe chat stop                 # shut the server down gracefully

Sending data

cpipe chat greet -d Alice                        # -d / --data sets the "data" field
cpipe chat greet Alice                           # positional DATA works too
cpipe chat chat -j '{"messages":[{"role":"user","content":"Hello"}]}'  # merge extra JSON fields

Streaming responses

cpipe detects streaming automatically. Chunks are printed as they arrive; the command exits after the final {"done": true} sentinel.

cpipe chat chat -j '{"messages":[{"role":"user","content":"Tell me a joke"}]}'

Protocol flags

Flag	Effect
`--no-subscribe`	Skip the subscribe/unsubscribe handshake entirely
`-n` / `--no-wait`	Fire-and-forget; do not wait for a response
`-t SECS` / `--timeout SECS`	Response timeout in seconds (default: 5.0)
`-v` / `--verbose`	Print sent messages and status to stderr

Examples

cpipe --list                                         # what's running?
cpipe chat description                               # what does this tool do?
cpipe chat help                                      # full API reference
cpipe tts text -d "Hello, world"                     # send a text chunk to the TTS server
cpipe tts flush                                      # drain the TTS buffer
cpipe chat stop                                      # shut down the LLM server
cpipe --clear                                        # clean up stale pipes after a crash

---name: cpipedescription: Use cpipe to discover, inspect, and send commands to named-pipe tool servers.---Use `cpipe` to interact with `ToolServer` instances (servers following the `tool-*` pipe naming convention). Always activate the `named-pipes` conda environment first.```bashconda activate named-pipes```## Discover running servers```bashcpipe --list # list tool pipes (tool-* convention) under /tmp (fast, no process scan)cpipe --pid # same, but also show which PIDs have each pipe opencpipe --clear # delete orphaned tool pipes (no live process) under /tmp```Pass an optional directory to search a different root (e.g. `cpipe --list /var/tmp`).## Send commands to a tool server```bashcpipe <tool> <cmd>````<tool>` is either a bare tool name (e.g. `chat`) — which resolves to `/tmp/tool-chat` — or a full pipe path. `<cmd>` is the command to send.### Built-in commands every tool supports```bashcpipe chat ping # health check — responds with "pong"cpipe chat status # current state of the server (e.g. "running")cpipe chat description # one-line description of the toolcpipe chat help # full help text (SKILL.md content)cpipe chat stop # shut the server down gracefully```### Sending data```bashcpipe chat greet -d Alice # -d / --data sets the "data" fieldcpipe chat greet Alice # positional DATA works toocpipe chat chat -j '{"messages":[{"role":"user","content":"Hello"}]}' # merge extra JSON fields```### Streaming responses`cpipe` detects streaming automatically. Chunks are printed as they arrive; the command exits after the final `{"done": true}` sentinel.```bashcpipe chat chat -j '{"messages":[{"role":"user","content":"Tell me a joke"}]}'```## Protocol flags| Flag | Effect ||---|---|| `--no-subscribe` | Skip the subscribe/unsubscribe handshake entirely || `-n` / `--no-wait` | Fire-and-forget; do not wait for a response || `-t SECS` / `--timeout SECS` | Response timeout in seconds (default: 5.0) || `-v` / `--verbose` | Print sent messages and status to stderr |## Examples```bashcpipe --list # what's running?cpipe chat description # what does this tool do?cpipe chat help # full API referencecpipe tts text -d "Hello, world" # send a text chunk to the TTS servercpipe tts flush # drain the TTS buffercpipe chat stop # shut down the LLM servercpipe --clear # clean up stale pipes after a crash```

Frequently asked questions

Cpipe