| name | skynet |
| description | Manage the Skynet multi-agent collaboration network using the skynet CLI. Use when creating or managing workspaces, agents, humans, or checking system status. |
Skynet Management Skill
You can manage the Skynet multi-agent collaboration network using the skynet CLI via npx. All commands below are non-interactive (pass all options as flags) so you can run them directly via your shell tool.
No installation required — all commands use npx @skynet-ai/cli@latest which downloads and runs the latest version automatically.
Workspace Management
Create a workspace
npx @skynet-ai/cli@latest workspace new --name <workspace-name> [--host <host>] [--port <port>]
--name (required): Human-readable workspace name--host (optional): Bind address, default 0.0.0.0--port (optional): Port number, default 4117
List workspaces
npx @skynet-ai/cli@latest workspace list
Delete a workspace
npx @skynet-ai/cli@latest workspace delete <workspace-uuid> --force
Removes the workspace from the registry and deletes all its data (agents, messages, config).
Start a workspace (daemon)
npx @skynet-ai/cli@latest workspace start <name-or-id> -d
Stop a workspace
npx @skynet-ai/cli@latest workspace stop <name-or-id>
Check workspace daemon status
npx @skynet-ai/cli@latest workspace status <name-or-id>
View workspace logs
npx @skynet-ai/cli@latest workspace logs <name-or-id>
Agent Management
All agent commands require a running workspace. --workspace <name-or-id> is always required.
Create an agent
npx @skynet-ai/cli@latest agent new --name <agent-name> --type <agent-type> [--role <role>] [--persona <persona>] [--workdir <path>] [--skills <spec...>] --workspace <name-or-id>
--name (required): Agent display name--type (required): Agent type. Currently claude-code, opencode, and codex-cli are supported. Other types (gemini-cli, generic) are not yet supported — do not use them unless explicitly asked by the user.--role (optional): Agent's role description (e.g., "backend engineer")--persona (optional): Persona description for the agent's behavior--workdir (optional): Custom working directory (default: ~/.skynet/<ws>/<id>/work)--skills (optional, repeatable): Install skills into the agent's working directory via npx skills add. Format: source[:skill-name]. Can be specified multiple times (e.g., --skills github.com/org/repo --skills ./local-skill:my-skill)
Working directory prompt: If the user does not explicitly specify --workdir, you must ask the user before running the command:
The agent's working directory determines where it reads/writes files. Would you like to:
- Specify a custom working directory (e.g., a project repo path)
- Use the default (
~/.skynet/<ws>/<id>/work)
If the user chooses a custom path, pass it via --workdir <path>. If they choose the default, omit --workdir.
Finding skills: If the user wants to create an agent with a particular skill but does not provide a specific skill source/path, search for it first:
npx skills find <query>
Review the search results with the user and confirm which skill to use before passing it to --skills.
Start an agent
npx @skynet-ai/cli@latest agent start <agent-name-or-id> --workspace <name-or-id>
Connects the agent to the workspace and starts processing messages as a background daemon (default). Use -f to run in foreground instead.
Stop an agent
npx @skynet-ai/cli@latest agent stop <agent-name-or-id> --workspace <name-or-id>
Check agent daemon status
npx @skynet-ai/cli@latest agent status <agent-name-or-id> --workspace <name-or-id>
View agent logs
npx @skynet-ai/cli@latest agent logs <agent-name-or-id> --workspace <name-or-id>
Delete an agent
npx @skynet-ai/cli@latest agent delete <agent-uuid> --force --workspace <name-or-id>
Deletes the agent from the workspace. Fails if the agent is currently connected.
Interrupt an agent
npx @skynet-ai/cli@latest agent interrupt <agent-name-or-id> --workspace <name-or-id>
Interrupts the agent's currently running task (equivalent to Ctrl+C). The agent remains connected and can receive new tasks.
Reset an agent's session (forget)
npx @skynet-ai/cli@latest agent forget <agent-name-or-id> --workspace <name-or-id>
Clears the agent's conversation history so it starts fresh. Useful when reassigning an agent to an unrelated task.
List agents
npx @skynet-ai/cli@latest agent list --workspace <name-or-id>
Human Management
Create a human
npx @skynet-ai/cli@latest human new --name <human-name> --workspace <name-or-id>
Delete a human
npx @skynet-ai/cli@latest human delete <human-uuid> --force --workspace <name-or-id>
Deletes the human from the workspace. Fails if the human is currently connected.
List humans
npx @skynet-ai/cli@latest human list --workspace <name-or-id>
Chat (Human Only)
Do NOT run this command yourself. skynet chat launches an interactive TUI for humans to join the workspace. When you need a human to join, tell them to run this command in a separate terminal.
npx @skynet-ai/cli@latest chat [--name <human-name>] --workspace <name-or-id>
--name (optional): Human name to join as (skips selection prompt)- If only one human is registered, it is auto-selected.
Doctor
Check system prerequisites
npx @skynet-ai/cli@latest doctor
Runs diagnostic checks for Node.js version, pnpm, git, agent CLIs (claude, gemini, codex), workspace status, and port availability. Use this to troubleshoot environment issues.
Status
Check workspace status
npx @skynet-ai/cli@latest status --workspace <name-or-id>
Shows all registered agents and humans with their id, name, role, persona, and online status.
Typical Workflow
- Create a workspace:
npx @skynet-ai/cli@latest workspace new --name my-project
- Start the workspace:
npx @skynet-ai/cli@latest workspace start my-project -d
- Create agents:
npx @skynet-ai/cli@latest agent new --workspace my-project --name backend --type claude-code --role "backend engineer"
- Start the agent:
npx @skynet-ai/cli@latest agent start backend --workspace my-project
- Create a human:
npx @skynet-ai/cli@latest human new --workspace my-project --name alice
- Tell the human to join chat:
npx @skynet-ai/cli@latest chat --workspace my-project --name alice
- Check status:
npx @skynet-ai/cli@latest status --workspace my-project
- Stop when done:
npx @skynet-ai/cli@latest agent stop backend --workspace my-project && npx @skynet-ai/cli@latest workspace stop my-project
Logs
All runtime logs are written to ~/.skynet/<workspace-uuid>/logs/:
- Server log:
~/.skynet/<workspace-uuid>/logs/server.log
- Agent logs:
~/.skynet/<workspace-uuid>/logs/<agent-uuid>.log
Tips
- CRITICAL: When deleting workspaces, agents, or humans, you MUST always pass
--force. Without --force, the command enters an interactive confirmation prompt that will hang and block the agent indefinitely.
- Run
npx @skynet-ai/cli@latest status to see who is currently connected.
- Each workspace stores its data in
~/.skynet/<workspace-uuid>/data.db.
- The workspace server exposes a REST API at
http://<host>:<port>/api/ for programmatic access.
