القائمة
Portable SSH profile manager for agents. Run remote commands on saved hosts by friendly name instead of typing user@host -i key every time. Type less crap around your SSH commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run and manage background jobs from the terminal. Use this skill when the user wants to execute long-running commands in the background, track job status, read job output, or manage multiple concurrent processes. Provides friendly-name tracking, status monitoring, and output capture for background tasks.
Build self-contained, single-file HTML artifacts and serve them with the artify CLI. Use for visualizations, interactive tools, presentations, living documents, forms and quizzes that return structured data via artify snapshot, and any browser-native replacement for static files. Prefer adapting starters when there is a close fit; otherwise build from scratch.
Use this skill when you need to manage project tasks — create, update, complete, prioritize, filter, review, track dependencies, or find unblocked work. Trigger on: 'add a task', 'create task', 'show tasks', 'what's next', 'mark done', 'update task', 'task status', 'task history', 'next task', 'task inbox', 'list tasks', 'init tasks', 'task deps', 'ready tasks', 'blocked tasks', 'search tasks', 'tag-any', 'dependency graph'. Also use proactively when starting a new work session — check `tasks status` and `tasks ready` to orient yourself. This skill covers the project's static, file-based task system (persistent, in-repo history) with typed dependency tracking, ready queue, and priority management — NOT ephemeral runtime task tools.
Generate complete, production-ready TTS (Text-to-Speech) scripts and CLI tools using edge-tts — Microsoft's neural voice engine with 400+ natural-sounding voices. Use this skill whenever the user wants to speak text aloud from the terminal/PowerShell, list or search voices, select voices by name/language/gender, control rate/volume/pitch, save speech to MP3/audio files, or pipe text into a speak command. Trigger for ANY request involving TTS, speech synthesis, say command, speak function, voice output, edge-tts, or audio from scripts — even small snippets. Always check installation first and prefer uv tool install for setup.
Autonomous execution mode triggered by the word "engage". Use when the user has finished planning and wants the agent to execute autonomously without further questions until the workflow is fully complete. The agent must build, test, verify, and deliver proof of work — never exiting with an incomplete or unverified result. Trigger on: "engage", "go autonomous", "execute the plan", "run it", "make it happen", or any explicit signal to switch from planning mode into fully autonomous build-and-verify mode.
Control tmux/psmux sessions for interactive CLIs, SSH connections, and parallel agent orchestration. Works cross-platform: tmux on Linux/macOS, psmux on Windows. Provides sync commands that send keys and automatically capture output. Triggers: "run in tmux", "create tmux session", "tmux", "SSH session", "parallel terminals", "run multiple agents".
| name | essh |
| description | Portable SSH profile manager for agents. Run remote commands on saved hosts by friendly name instead of typing user@host -i key every time. Type less crap around your SSH commands. |
Abstracts SSH so you type less crap around your commands.
The human sets up profiles (essh add ...). You just use them.
essh --help
If not installed:
uv tool install "git+https://github.com/lirrensi/agent-sommelier"
essh list --json
essh <name> <command>
That's it. No -i key.pem, no user@host:22. Just the name.
essh list --json
# → [{"name": "coral-fox", "user": "deploy", "host": "192.168.1.50", "port": 22, "key_path": ""}]
essh coral-fox "uname -a"
essh coral-fox "systemctl status nginx"
essh prod-web "tail -n 100 /var/log/app.log"
## Command Filters
The human may set up command filter rules to control what you can run on
each host. Filters use wildcard matching with three actions:
- **allow** — The command runs without any prompting.
- **ask** — The command is blocked until the human authorizes it (same
authorization flow as the connection itself).
- **deny** — The command is rejected immediately with an error message.
There is no way to bypass this.
### Checking if filters are defined
```bash
# Global filters (apply to all hosts)
essh filter list global
# Per-host filters (apply to a specific host)
essh filter list <name>
When you run essh <name> "<command>", essh checks all filter rules (global first, then per-host) from top to bottom. The last matching rule wins.
If a deny rule matches: the command is rejected. You will see something like:
❌ BLOCKED: This command is blocked by a filter rule.
Command: rm -rf /etc
If an ask rule matches: in non-TTY mode, essh creates an authorization request showing the exact command. The human sees:
Pending request for 'prod-web':
Command: rm -rf /var/log
They must run essh authorize <name> for the command to proceed.
If an allow rule matches, or no rule matches: the command runs normally through the existing authorization gate.
The same wildcard rules as opencode (anomalyco) permission system:
| Pattern | Matches | Doesn't match |
|---|---|---|
rm * | rm, rm -rf / | rmdir |
shutdown * | shutdown, shutdown -h now | shutdown with no args? yes, actually |
git * | git, git status | (anything starting with git) |
rm -rf * | rm -rf /, rm -rf . | rm -r |
Key rule: * in patterns like rm * makes the trailing space and arguments optional — so rm * matches both bare rm and rm -rf /.
If you get blocked and think it's a mistake, tell the human:
The command "..." was blocked by a filter rule.
You may need to add an ``--action allow`` rule or adjust the pattern.