aiskillstore/subagent-orchestration
skills/diegopherlt/subagent-orchestration/SKILL.md
This skill should be used when coordinating multiple subagents, implementing orchestrator patterns, or managing parallel agent workflows. Trigger phrases: "orchestrate agents", "coordinate subagents", "parallel agents", "multi-agent workflow", "delegate to agents", "run agents in parallel", "launch multiple agents".
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace subagent-orchestrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 10:35 AM55.3s3 files scanned
SKILL.md
- name:
- subagent-orchestration
- description:
- |
- Trigger phrases:
- orchestrate agents", "coordinate subagents", "parallel agents",
Orchestrating Subagents
Core Principles
- Always suggest subagent invocation when task matches their expertise
- User has final decision on invocation
- Prefer multiple parallel invocations for independent tasks with strict scopes
- ALWAYS define: files to modify, files NOT to touch, specific task boundaries
When to Use Parallel Invocation
Invoke multiple subagents in a single message when:
- Tasks are completely independent
- Each task has strict, non-overlapping scope
- No task depends on another's results
Examples:
- ✓ "Explore authentication flow" + "Review recent auth changes" (parallel)
- ✗ "Explore auth flow then refactor based on findings" (sequential - second depends on first)
Scope Definition Template
When proposing subagent invocation, use this structure:
Task: [Clear, single-sentence description]
Files to modify: [Explicit list with paths]
Files NOT to touch: [Explicit exclusions - be specific]
Constraints:
- [Business rules to follow]
- [Patterns to maintain]
- [Technical requirements]
Reference docs: [@AGENTS.md, @docs/architecture.md, etc.]
Decision Framework
Before suggesting subagents, verify:
- Is the scope clearly bounded? Can you define exact files and boundaries?
- Is it independent? Does it require results from another task first?
- Is it delegable? Would a subagent have enough context?
If any answer is "no", handle the task directly or break it down further.
Anti-patterns to Avoid
- Vague file specifications ("update related files")
- Missing exclusions (failing to specify what NOT to touch)
- Sequential tasks disguised as parallel (one depends on the other)
- Unbounded scopes ("refactor the codebase")
- Missing context references (no @file references for subagent to read)
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026