Use when running multiple independent tasks concurrently across agents, tools, or systems — ensures thread safety, proper result collection, and efficient resource usage. Default skill for Starlight Orchestrator.
Scanned 6/11/2026
Install via CLI
openskills install frankxai/Starlight-Intelligence-System---
name: orchestration/parallel-execution
description: Use when running multiple independent tasks concurrently across agents, tools, or systems — ensures thread safety, proper result collection, and efficient resource usage. Default skill for Starlight Orchestrator.
type: agent-orchestration
---
# Parallel Execution
> *"Why do one thing when you can do three?"*
## When This Skill Activates
- Running multiple independent tasks concurrently
- Keywords: "parallel", "concurrent", "simultaneously", "batch"
- Default for: Starlight Orchestrator
## What This Skill Does
Manages parallel execution of independent tasks across agents, tools, and systems. Ensures thread safety, proper result collection, and efficient resource usage.
## Procedures
### Procedure 1: Parallelization Analysis
1. List all tasks to be executed
2. Build dependency graph
3. Identify independent tasks (no dependencies on each other)
4. Group independent tasks for parallel execution
5. Sequence dependent tasks after their prerequisites
6. Calculate resource requirements for parallel batch
### Procedure 2: Parallel Dispatch
1. Confirm all parallel tasks are truly independent
2. Limit concurrent agents to 3 (token budget constraint)
3. Dispatch tasks to assigned agents simultaneously
4. Monitor all tasks for completion or failure
5. Collect results as each task completes
6. Handle failures without blocking other parallel tasks
### Procedure 3: Result Collection
1. Wait for all parallel tasks to complete
2. Collect all results
3. Check for conflicts in results
4. If conflicts: resolve using Synthesis Protocol
5. Merge into unified output
6. Report any failed tasks separately
## Integration Points
- **Vault:** Operational Vault (execution metrics)
- **Agents:** Orchestrator (primary), up to 3 concurrent agents
- **Engine:** Orchestration Engine (parallel pattern)
## Quality Criteria
- Were only truly independent tasks run in parallel?
- Were results properly collected and merged?
- Were failures handled gracefully?
- Was the concurrent agent limit respected?
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.