Agent skill
Start Orchestrator
Starts the Orchestrator 3 Stream application (backend + frontend) in background mode. Use when the user asks to start orchestrator, launch orchestrator, run orchestrator, or open the orchestrator UI. Supports --session and --cwd flags for backend.
Install this agent skill to your Project
npx add-skill https://github.com/PytaichukBohdan/DanaCockFightBot/tree/main/.claude/skills/start-orchestrator
SKILL.md
Start Orchestrator
Launches the Orchestrator 3 Stream application with both backend (FastAPI) and frontend (Vue/Vite) servers.
Prerequisites
- The orchestrator application is located at
apps/orchestrator_3_stream/ - Backend requires Python with uv (Astral UV)
- Frontend requires Node.js with npm
- PostgreSQL database should be running
Configuration
Default ports (configurable via .env):
- Backend: Port 8002 (default fallback: 9403)
- Frontend: Port 5175
Backend Flags
The backend script (start_be.sh) accepts:
| Flag | Description | Priority |
|---|---|---|
--cwd <path> |
Working directory for the orchestrator | CLI > .env (ORCHESTRATOR_WORKING_DIR) > current dir |
--session <id> |
Session ID to resume | CLI > .env (ORCHESTRATOR_SESSION_ID) > new session |
Workflow
1. Start Backend (with optional flags)
Run in background by default:
# Basic start (new session, current directory)
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh &
# With session ID (resume existing session)
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --session <session-id> &
# With custom working directory
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --cwd /path/to/project &
# With both flags
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --cwd /path/to/project --session <session-id> &
2. Start Frontend
Run in background:
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh &
3. Open UI in Chrome
After both services are running, open the frontend URL:
open -a "Google Chrome" "http://127.0.0.1:5175"
Complete Example Commands
Start both in background (new session):
# Start backend
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh &
# Wait for backend to initialize
sleep 3
# Start frontend
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh &
# Wait for frontend to initialize
sleep 2
# Open in Chrome
open -a "Google Chrome" "http://127.0.0.1:5175"
Resume a session:
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --session abc123-def456 &
sleep 3
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh &
sleep 2
open -a "Google Chrome" "http://127.0.0.1:5175"
Foreground Mode
If user requests foreground mode, do NOT use & suffix and run each command sequentially, starting frontend first in background then backend in foreground:
# Frontend in background (so we can run backend in foreground)
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh &
# Backend in foreground (to see logs)
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --cwd /path/to/project
Stopping Services
To stop the services:
# Find and kill backend
lsof -ti:8002 | xargs kill -9
# Find and kill frontend
lsof -ti:5175 | xargs kill -9
Troubleshooting
- Port in use: The scripts automatically kill processes using their ports before starting
- Database not running: Ensure PostgreSQL is running before starting backend
- Missing dependencies: Run
uv syncin backend directory,npm installin frontend directory
Examples
Example 1: Basic Start
User request:
Start the orchestrator
You would:
- Start backend in background:
bash
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh & - Wait 3 seconds for backend to initialize
- Start frontend in background:
bash
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh & - Wait 2 seconds for frontend to initialize
- Open Chrome:
bash
open -a "Google Chrome" "http://127.0.0.1:5175"
Example 2: Resume Session with Custom CWD
User request:
Start orchestrator with session abc123 and working directory /Users/me/myproject
You would:
- Start backend with flags:
bash
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh --cwd /Users/me/myproject --session abc123 & - Wait, then start frontend and open Chrome as above
Example 3: Foreground Mode
User request:
Start orchestrator in foreground so I can see logs
You would:
- Start frontend in background first:
bash
cd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_fe.sh & - Wait 2 seconds
- Start backend in foreground (no
&):bashcd /path/to/agent-experts/apps/orchestrator_3_stream && ./start_be.sh - Note: Chrome opening should happen after frontend is ready but before backend foreground command
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
creating-new-skills
Creates new Agent Skills for AI Agents following best practices and documentation. Use when the user wants prompts 'create a new skill ...' or 'use your meta skill to ...'.
telegram
This skill should be used when fetching, searching, downloading, or sending messages on Telegram. Use for queries like "show my Telegram messages", "search Telegram for...", "get unread messages", "send a message to...", or "add Telegram messages to my notes".
handoff
Compact the current conversation into a handoff document for another agent to pick up.
scaffold-exercises
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
edit-article
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Didn't find tool you were looking for?