manager-getting-started
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: manager-getting-started
description: Getting started with Manager — the 48-tool multi-AI orchestrator. Use when: delegating code task…
category: other
runtime: no special runtime
---
# manager-getting-started output preview
## PART A: Task fit
- Use case: Getting started with Manager — the 48-tool multi-AI orchestrator. Use when: delegating code tasks to Claude Code/Codex/Gemini, running parallel AI executions, creating workflow templates, or routing tasks across AI backends. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “What Manager Is / Key Tools / Common Patterns” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Getting started with Manager — the 48-tool multi-AI orchestrator. Use when: delegating code tasks to Claude Code/Codex/Gemini, running parallel AI executions, creating workflow templates, or routing tasks across AI backends. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “What Manager Is / Key Tools / Common Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “What Manager Is / Key Tools / Common Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: manager-getting-started
description: Getting started with Manager — the 48-tool multi-AI orchestrator. Use when: delegating code task…
category: other
source: tomevault-io/skills-registry
---
# manager-getting-started
## When to use
- Getting started with Manager — the 48-tool multi-AI orchestrator. Use when: delegating code tasks to Claude Code/Codex…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “What Manager Is / Key Tools / Common Patterns” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "manager-getting-started" {
input -> user goal + target files + boundaries + acceptance criteria
context -> What Manager Is / Key Tools / Common Patterns
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} What Manager Is
A single MCP server (manager.exe) with 48 tools for multi-AI orchestration. It routes tasks to Claude Code, Codex, Gemini CLI, and GPT, with parallel execution, workflow chaining, and learned routing patterns.
| Category | Key Tools | What It Does |
|---|---|---|
| Task lifecycle | task_submit, task_status, task_output, task_poll, task_list | Submit, monitor, and retrieve AI task results |
| Routing | task_route, task_decompose, task_explain | Smart backend selection and task breakdown |
| Parallel | task_run_parallel | Concurrent multi-backend execution with dependencies |
| Workflows | workflow_run | Multi-step chains with retry and escalation |
| Templates | template_save, template_list, template_run | Reusable workflow patterns |
| Sessions | session_start, session_send, session_list | Interactive AI sessions |
| Direct access | codex_exec, codex_review, gemini_direct | Call specific backends directly |
| Analytics | get_analytics, run_analyzer | Execution stats and pattern analysis |
| Loaves | create_loaf, loaf_update, loaf_status, loaf_close | Multi-step tracked jobs |
| Notifications | notify | Desktop notifications for task events |
Key Tools
| I want to... | Use |
|---|---|
| Delegate a coding task | task_submit(backend="claude_code", prompt="...") |
| Let Manager pick the best AI | task_submit(auto_route=true, prompt="...") |
| Run tasks in parallel | task_run_parallel(steps=[...]) |
| Chain steps with retry | workflow_run(steps=[...]) |
| Save a reusable pattern | template_save(name="...", steps=[...]) |
| Check what backend to use | task_route(prompt="...") |
| Start interactive session | session_start(backend="claude_code") |
| Get execution stats | get_analytics |
Common Patterns
Quick delegation: manager:task_submit(backend="claude_code", prompt="Add error handling to src/main.rs", working_dir="C:/project")
Poll for completion: manager:task_poll(task_id="abc-123", timeout=60)
Parallel review: manager:task_run_parallel(steps=[ {id: "frontend", backend: "claude_code", prompt: "Review src/ui/", parallel_group: "review"}, {id: "backend", backend: "codex", prompt: "Review src/api/", parallel_group: "review"} ])
Anti-Patterns
- Don't poll in a tight loop — use task_poll with a timeout instead of repeated task_status
- Don't hardcode backends — use auto_route or task_route to let Manager learn which backend works best
Source: AIWander/manager — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review