task-orchestrator
Autonomous multi-agent task orchestration with dependency analysis, parallel tmux/Codex execution, and self-healing heartbeat monitoring. Use for large projects with multiple issues/tasks that need coordinated parallel execution.
Install with Tessl CLI
npx tessl i github:jdrhyne/agent-skills --skill task-orchestrator83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates specific technical capabilities and includes an explicit 'Use for' clause. The main weakness is the heavy use of technical jargon in trigger terms that users may not naturally use when requesting this functionality. The description would benefit from including more user-friendly synonyms alongside the technical terms.
Suggestions
Add natural language trigger terms users might say, such as 'run tasks in parallel', 'batch process issues', 'work on multiple things at once', or 'coordinate multiple agents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dependency analysis', 'parallel tmux/Codex execution', 'self-healing heartbeat monitoring', and 'multi-agent task orchestration'. These are concrete technical capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Autonomous multi-agent task orchestration with dependency analysis, parallel tmux/Codex execution, and self-healing heartbeat monitoring') and when ('Use for large projects with multiple issues/tasks that need coordinated parallel execution'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'large projects', 'multiple issues/tasks', 'parallel execution', but uses technical jargon ('tmux', 'Codex', 'heartbeat monitoring') that users may not naturally say. Missing common variations like 'batch processing', 'concurrent tasks', 'run in parallel'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technical niche: multi-agent orchestration, tmux/Codex execution, heartbeat monitoring. Unlikely to conflict with simpler task management or single-agent skills due to explicit parallel/multi-agent focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and concrete executable examples. The self-healing monitoring pattern with explicit remediation steps is particularly well done. Main weaknesses are moderate verbosity and the monolithic structure that could benefit from splitting detailed examples into referenced files.
Suggestions
Move the 'Example: Security Framework Orchestration' section to a separate EXAMPLES.md file and reference it
Move 'Lessons Learned' to a separate TROUBLESHOOTING.md or append to a referenced file, keeping only a brief summary inline
Consolidate the repeated parallel/sequential execution explanations into a single concise section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., repeated explanations of parallel vs sequential execution, multiple similar code blocks). The JSON examples and bash scripts are necessary but could be tightened in places. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete JSON schemas, and copy-paste ready code blocks throughout. The tmux commands, git worktree setup, and monitoring scripts are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear phases (Analyze → Create Manifest → Launch → Monitor → Create PRs → Cleanup). Includes explicit validation checkpoints in the self-healing section and feedback loops for stuck/error states with specific remediation actions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~350 lines) that could benefit from splitting detailed examples (like the Security Framework example) and the Lessons Learned into separate files. References to other skills are mentioned but inline content is heavy. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.