agent-manager-skill
Manage CLI Agents with Tmux
This skill enables Claude to manage multiple local CLI agents running in parallel tmux sessions, providing start/stop/monitor capabilities and cron-friendly scheduling for automated workflows.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「agent-manager-skill」を使用しています。 agent-manager-skill list
期待される結果:
- EMP_0001: running (uptime: 2h 34m)
- EMP_0002: running (uptime: 1h 12m)
- EMP_0003: stopped
「agent-manager-skill」を使用しています。 agent-manager-skill doctor
期待される結果:
- ✓ tmux installed (v3.3a)
- ✓ python3 installed (3.10.12)
- ✓ agents/ directory exists
- ✓ 5 agents configured
- All checks passed
セキュリティ監査
安全Security audit complete. All 9 static findings are false positives. The skill contains only documentation with markdown code examples - no actual shell execution, no suspicious network activity, and no cryptographic code. The backticks flagged are markdown formatting, and the URL is a legitimate GitHub repo reference.
品質スコア
作れるもの
DevOps Workflow Automation
Run multiple background maintenance scripts in parallel, monitor their output, and schedule recurring tasks using cron.
Parallel AI Task Execution
Launch multiple Claude or other CLI agents simultaneously for different subtasks, then aggregate results.
Background Job Management
Start long-running processes in tmux sessions that persist beyond terminal sessions, with easy monitoring.
これらのプロンプトを試す
Use the agent-manager-skill to list all currently running agents and their status.
Start agent EMP_0001 using the agent-manager-skill and show me the output.
Monitor the logs of agent EMP_0002 in real-time using the agent-manager-skill.
Assign the following task to agent EMP_0003 using the agent-manager-skill: Follow teams/fractalmind-ai-maintenance.md Workflow
ベストプラクティス
- Configure agents in the agents/ directory before attempting to start them
- Use the doctor command first to verify all prerequisites are installed
- Monitor agents during initial runs to ensure they behave as expected
- Use descriptive agent IDs (like EMP_0001) for easy identification
回避
- Starting agents without first running the doctor check
- Assigning tasks to agents that are not properly configured
- Not monitoring agent output during critical operations
- Running too many agents simultaneously without resource monitoring