$ ~/registry/skill/affaan-m-parallel-execution-optimizer

SKILL

parallel-execution-optimizer

Name: parallel-execution-optimizer
Author: affaan-m

Speed up complex tasks with parallel execution while preserving correctness.

Stars

★ 229,796

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 210.5k

Summary

This is a prompt-only skill that describes a methodology for parallel execution; it requires no secrets, declares no remote endpoints, and does not itself provide a mechanism for code execution or data exfiltration. Given its open-source nature and very high community adoption, the overall risk is low, with the main remaining check being repository maintenance and license clarity.

CredentialsLow risk

The materials explicitly state that no keys or environment variables are required, and the README does not request login, API tokens, or credential injection; no direct credential collection, storage, or misuse risk is evident.

Network egressLow risk

The materials explicitly state that there are no remote endpoints. The README mentions API checks, deploy readbacks, and browser checks only as usage scenarios, and does not state that the skill itself connects to any service or sends user data out.

Code executionLow risk

This is a prompt-only skill. The README mainly provides operational guidance on parallelization, isolated write surfaces, and verification workflows; it does not provide executable scripts, install commands, or local process-control interfaces, so the material itself does not constitute direct code execution capability.

Data accessLow risk

The documentation does not declare any permission requests for the filesystem, databases, browsers, or other system resources. While it discusses scenarios such as repo inspection, file reads, and worktrees, these are methodological suggestions rather than built-in data read/write capabilities.

Supply chainLow risk

The source is an open-source GitHub repository with extremely high community adoption (about 210.5k stars), both of which are strong risk-reducing signals. The only visible gaps are an undeclared license and unknown maintenance status, which merit follow-up checks but are not sufficient on their own to raise this to high risk.

Recommendations

Use it as a prompt/methodology document; do not treat the README's scenario descriptions as built-in execution or networking capabilities.
Before adoption, verify recent commits, issue/PR activity, and release history to confirm the project is not unmaintained.
Check the license status to ensure compatibility with your organization's compliance requirements.
If you later pair it with executable tools for parallel operations, assess those tools separately for local execution, network access, and data permissions.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "parallel-execution-optimizer" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/parallel-execution-optimizer/SKILL.md
2. Save it as ~/.claude/skills/parallel-execution-optimizer/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Refactor Multiple Modules in Parallel

Prompt

Please refactor the user, payment, and notification modules in parallel: assign an independent workflow to each module, inspect code smells, propose changes, generate patches, then consolidate conflicts and final test results.

Expected

Module-by-module refactoring recommendations, patch results, conflict notes, and a unified testing and validation summary.

Batch-Verify Data Findings

Prompt

Split this data analysis task into parallel verification lanes: one checks raw data quality, one recomputes key metrics, one validates chart conclusions, and one reviews outlier handling; then merge everything into a consistency report.

Expected

A report containing findings from each verification lane, discrepancy comparisons, risk flags, and a final consistency conclusion.

Run Large-Scale Retrieval Concurrently

Prompt

Please accelerate this competitor research: concurrently gather the websites, pricing, features, and recent updates of 10 competitors, organize each into a structured card, then produce a comparison table and key insights.

Expected

A structured summary for each competitor, a unified comparison table, and presentation-ready insights.

// docs

Parallel Execution Optimizer

Use this skill when speed comes from doing independent work at the same time: repo inspection, file reads, API checks, browser checks, build/test lanes, deploy readbacks, or multi-worktree implementation passes.

Core Pattern

Turn urgency into a dependency graph before acting.

Define the objective and done signal.
Split work into lanes.
Mark each lane as parallel, sequential, or gated.
Run independent reads/checks together.
Keep writes isolated by file, worktree, branch, service, or dataset.
Merge only after evidence shows the lanes are compatible.
End with a verification table, not a vague speed claim.

Lane Matrix

Before a large push, write a compact matrix:

Lane | Can run in parallel? | Write surface | Risk | Verification
Repo scan | yes | none | low | rg/git status outputs
Backend patch | maybe | src/api | medium | unit tests
Frontend patch | maybe | app/components | medium | browser screenshot
Deploy readback | after build | remote service | high | live URL + logs

Only run lanes in parallel when their write surfaces do not collide.

Execution Rules

Batch file reads, searches, status checks, and metadata queries.
Use isolated worktrees for large unrelated implementation lanes.
Start long-running tests, builds, backfills, and deploys in separate sessions, then poll them deliberately.
If a lane discovers a blocker that changes the plan, pause dependent lanes and update the matrix.
Never let a background process outlive the turn unless the user explicitly asked for a continuing service.
Do not parallelize destructive commands, migrations, writes to the same table, or live customer-impacting deploys without an explicit gate.

Output Shape

Use this when reporting:

Parallel execution result:
- Lanes run: 5
- Lanes completed: 4
- Blocked lane: deploy readback, waiting on DNS propagation
- Fast path found: batched repo scan + focused tests
- Verification: lint pass, unit pass, live smoke pass

Failure Modes

More concurrency that creates conflicting edits.
Benchmarking the tool instead of the task.
Treating "fast" as done before correctness is proven.
Forgetting to poll running sessions.
Hiding skipped checks behind a success summary.

Run parallel automated workflows across tools with Rube MCP for faster execution

ComposioGet→

$ loading_

Please install the "parallel-execution-optimizer" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/parallel-execution-optimizer/SKILL.md 2. Save it as ~/.claude/skills/parallel-execution-optimizer/SKILL.md 3. Reload skills and tell me it's ready

// examples

Refactor Multiple Modules in Parallel

Prompt

Please refactor the user, payment, and notification modules in parallel: assign an independent workflow to each module, inspect code smells, propose changes, generate patches, then consolidate conflicts and final test results.

Expected

Module-by-module refactoring recommendations, patch results, conflict notes, and a unified testing and validation summary.

Batch-Verify Data Findings

Prompt

Split this data analysis task into parallel verification lanes: one checks raw data quality, one recomputes key metrics, one validates chart conclusions, and one reviews outlier handling; then merge everything into a consistency report.

Expected

A report containing findings from each verification lane, discrepancy comparisons, risk flags, and a final consistency conclusion.

Run Large-Scale Retrieval Concurrently

Prompt

Please accelerate this competitor research: concurrently gather the websites, pricing, features, and recent updates of 10 competitors, organize each into a structured card, then produce a comparison table and key insights.

Expected

A structured summary for each competitor, a unified comparison table, and presentation-ready insights.

// docs

Parallel Execution Optimizer

Core Pattern

Turn urgency into a dependency graph before acting.

Define the objective and done signal.
Split work into lanes.
Mark each lane as parallel, sequential, or gated.
Run independent reads/checks together.
Keep writes isolated by file, worktree, branch, service, or dataset.
Merge only after evidence shows the lanes are compatible.
End with a verification table, not a vague speed claim.

Lane Matrix

Before a large push, write a compact matrix:

Lane | Can run in parallel? | Write surface | Risk | Verification
Repo scan | yes | none | low | rg/git status outputs
Backend patch | maybe | src/api | medium | unit tests
Frontend patch | maybe | app/components | medium | browser screenshot
Deploy readback | after build | remote service | high | live URL + logs

Only run lanes in parallel when their write surfaces do not collide.

Execution Rules

Batch file reads, searches, status checks, and metadata queries.
Use isolated worktrees for large unrelated implementation lanes.
Start long-running tests, builds, backfills, and deploys in separate sessions, then poll them deliberately.
If a lane discovers a blocker that changes the plan, pause dependent lanes and update the matrix.
Never let a background process outlive the turn unless the user explicitly asked for a continuing service.
Do not parallelize destructive commands, migrations, writes to the same table, or live customer-impacting deploys without an explicit gate.

Output Shape

Use this when reporting:

Parallel execution result:
- Lanes run: 5
- Lanes completed: 4
- Blocked lane: deploy readback, waiting on DNS propagation
- Fast path found: batched repo scan + focused tests
- Verification: lint pass, unit pass, live smoke pass

Failure Modes

More concurrency that creates conflicting edits.
Benchmarking the tool instead of the task.
Treating "fast" as done before correctness is proven.
Forgetting to poll running sessions.
Hiding skipped checks behind a success summary.