Files

Eric Chan c771979178 Add Skills + CLI mode for external agents (#599 )

* Add Skills + CLI external agent workflow

* feat: add Skills + CLI transport for ACP agents

* chore: remove branch-local compatibility shims

2026-04-10 18:41:53 +08:00

name, description

name	description
netcatty-tool-cli	Use this skill when an external agent needs to operate on Netcatty sessions through Skills + CLI instead of the netcatty-remote-hosts MCP server.

Netcatty Tool CLI

Use this skill for external ACP agents when Netcatty is configured for Skills + CLI mode.

For routine tasks, the host prompt is usually enough. Read only the reference that matches the task type.

Router

Use the exact Netcatty CLI prefix provided by the host prompt.
Keep --chat-session <chat-session-id> on every Netcatty CLI call. Do not omit it.
Treat --chat-session <chat-session-id> as required for env, session, real exec, and every sftp operation. Treat --session <session-id> as required for session, exec, and every sftp operation.
Classify the task before choosing a command path:
- Remote command execution tasks go through the exec reference.
- Remote file or directory tasks go through the sftp reference.
- If the user explicitly says to avoid shell or exec, do not use exec.
- Treat exec as the short-command path only. If the command may exceed about 60 seconds, or streams output for an extended period, use the long-running job commands instead of plain exec.
If the host prompt already names a connected default target session, use that session directly for routine requests that do not mention another session or host, but still start with session --session <id> --json --chat-session <chat-session-id> instead of jumping straight to exec or sftp.
Only fall back to env lookup when the task is ambiguous, the user points to another session, or that direct session lookup fails.

Treat the host-provided CLI prefix as the only supported entrypoint for this session.
Run Netcatty CLI commands strictly serially.
Treat Netcatty CLI errors as authoritative.
Never ask the user for SSH credentials, key paths, proxy settings, or jump-host details when Netcatty session access already exists.
Do not pause to explain the plan, re-read this skill, or design scripts before trying that shortest path.
When presenting structured results, prefer a concise table if it fits clearly.