Agent Skills
› ryantsai/KKTerm
› terminal-command-planner
terminal-command-planner
GitHub用于规划安全的终端命令,支持本地、SSH、WSL及PowerShell等环境。涵盖诊断、日志检查及服务审查,强调只读优先、避免破坏性操作,并明确各平台边界与语法差异。
Trigger Scenarios
用户请求终端命令
需要进行shell诊断
检查系统日志
服务状态审查
解释命令含义
Install
npx skills add ryantsai/KKTerm --skill terminal-command-planner -g -y
SKILL.md
Frontmatter
{
"name": "terminal-command-planner",
"description": "Plan safe terminal commands for local shells, SSH terminals, PowerShell, Command Prompt, WSL, diagnostics, log inspection, service checks, and approval-based command assistance in KKTerm."
}
Terminal Command Planner
Use this skill when the user asks for terminal commands, shell diagnostics, log checks, service inspection, or command explanations.
Workflow
- Determine whether the command targets a local terminal Session, an SSH Session, WSL, PowerShell, Command Prompt, or a generic shell.
- Prefer read-only inspection before mutation.
- Explain the intent and expected output before suggesting risky or unfamiliar commands.
- Keep commands scoped to the named host, path, service, process, or file.
- Avoid broad deletes, destructive disk operations, fork bombs, credential dumping, or irreversible system-wide changes.
- For mutating commands, offer a safer dry run, preview, backup, or targeted form when practical.
- Do not claim a command ran unless a tool result or session context proves it.
- If the current shell is unknown, make the shell assumption explicit.
- When translating between PowerShell, Command Prompt, WSL, and POSIX shells, call out syntax differences that matter.
KKTerm Boundaries
- Local Windows shells run through ConPTY; browser previews do not validate local terminal focus or input behavior.
- SSH uses NativeSsh and can differ from local shell behavior.
- Secrets must not be pasted into normal chat text.
- User-facing status belongs in the workspace status bar when changing app state.
Version History
- b4e2eb1 Current 2026-07-05 14:38


