Awesome-omni-skills parallel-agents

Native Parallel Agents workflow skill. Use this skill when the user needs Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/parallel-agents" ~/.claude/skills/diegosouzapw-awesome-omni-skills-parallel-agents && rm -rf "$T"

manifest: skills/parallel-agents/SKILL.md

Native Parallel Agents

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/parallel-agents

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Native Parallel Agents > Orchestration through Claude Code's built-in Agent Tool

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Native Agent Invocation, Orchestration Patterns, Available Agents, Claude Code Built-in Agents, Synthesis Protocol, Orchestration Synthesis.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Complex tasks requiring multiple expertise domains
Code analysis from security, performance, and quality perspectives
Comprehensive reviews (architecture + security + testing)
Feature implementation needing backend + frontend + database work
Simple, single-domain tasks
Quick fixes or small changes

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

This skill enables coordinating multiple specialized agents through Claude Code's native agent system. Unlike external scripts, this approach keeps all orchestration within Claude's control.

Imported: Native Agent Invocation

Single Agent

Use the security-auditor agent to review authentication

Sequential Chain

First, use the explorer-agent to discover project structure.
Then, use the backend-specialist to review API endpoints.
Finally, use the test-engineer to identify test gaps.

With Context Passing

Use the frontend-specialist to analyze React components.
Based on those findings, have the test-engineer generate component tests.

Resume Previous Work

Resume agent [agentId] and continue with additional requirements.

Examples

Example 1: Ask for the upstream workflow directly

Use @parallel-agents to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @parallel-agents against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @parallel-agents for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @parallel-agents using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Available agents - 17 specialized agents can be orchestrated
Logical order - Discovery → Analysis → Implementation → Testing
Share context - Pass relevant findings to subsequent agents
Single synthesis - One unified report, not separate outputs
Verify changes - Always include test-engineer for code modifications
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.

Imported Operating Notes

Imported: Best Practices

Available agents - 17 specialized agents can be orchestrated
Logical order - Discovery → Analysis → Implementation → Testing
Share context - Pass relevant findings to subsequent agents
Single synthesis - One unified report, not separate outputs
Verify changes - Always include test-engineer for code modifications

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/parallel-agents

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@00-andruia-consultant-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@10-andruia-skill-smith-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@20-andruia-niche-intelligence-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@2d-games
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Orchestration Patterns

Pattern 1: Comprehensive Analysis

Agents: explorer-agent → [domain-agents] → synthesis

1. explorer-agent: Map codebase structure
2. security-auditor: Security posture
3. backend-specialist: API quality
4. frontend-specialist: UI/UX patterns
5. test-engineer: Test coverage
6. Synthesize all findings

Pattern 2: Feature Review

Agents: affected-domain-agents → test-engineer

1. Identify affected domains (backend? frontend? both?)
2. Invoke relevant domain agents
3. test-engineer verifies changes
4. Synthesize recommendations

Pattern 3: Security Audit

Agents: security-auditor → penetration-tester → synthesis

1. security-auditor: Configuration and code review
2. penetration-tester: Active vulnerability testing
3. Synthesize with prioritized remediation

Imported: Available Agents

Agent	Expertise	Trigger Phrases
`orchestrator`	Coordination	"comprehensive", "multi-perspective"
`security-auditor`	Security	"security", "auth", "vulnerabilities"
`penetration-tester`	Security Testing	"pentest", "red team", "exploit"
`backend-specialist`	Backend	"API", "server", "Node.js", "Express"
`frontend-specialist`	Frontend	"React", "UI", "components", "Next.js"
`test-engineer`	Testing	"tests", "coverage", "TDD"
`devops-engineer`	DevOps	"deploy", "CI/CD", "infrastructure"
`database-architect`	Database	"schema", "Prisma", "migrations"
`mobile-developer`	Mobile	"React Native", "Flutter", "mobile"
`api-designer`	API Design	"REST", "GraphQL", "OpenAPI"
`debugger`	Debugging	"bug", "error", "not working"
`explorer-agent`	Discovery	"explore", "map", "structure"
`documentation-writer`	Documentation	"write docs", "create README", "generate API docs"
`performance-optimizer`	Performance	"slow", "optimize", "profiling"
`project-planner`	Planning	"plan", "roadmap", "milestones"
`seo-specialist`	SEO	"SEO", "meta tags", "search ranking"
`game-developer`	Game Development	"game", "Unity", "Godot", "Phaser"

Imported: Claude Code Built-in Agents

These work alongside custom agents:

Agent	Model	Purpose
Explore	Haiku	Fast read-only codebase search
Plan	Sonnet	Research during plan mode
General-purpose	Sonnet	Complex multi-step modifications

Use Explore for quick searches, custom agents for domain expertise.

Imported: Synthesis Protocol

After all agents complete, synthesize:


#### Imported: Orchestration Synthesis

### Task Summary
[What was accomplished]

### Agent Contributions
| Agent | Finding |
|-------|---------|
| security-auditor | Found X |
| backend-specialist | Identified Y |

### Consolidated Recommendations
1. **Critical**: [Issue from Agent A]
2. **Important**: [Issue from Agent B]
3. **Nice-to-have**: [Enhancement from Agent C]

### Action Items
- [ ] Fix critical security issue
- [ ] Refactor API endpoint
- [ ] Add missing tests

Imported: Key Benefits

✅ Single session - All agents share context
✅ AI-controlled - Claude orchestrates autonomously
✅ Native integration - Works with built-in Explore, Plan agents
✅ Resume support - Can continue previous agent work
✅ Context passing - Findings flow between agents

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.