Agent skill

Orchestrating Test Execution

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Test coordinate parallel test execution across multiple environments and frameworks.

MITAuto-check passedTesting & QA

Install Orchestrating Test Execution

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill orchestrating-test-execution -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace orchestrating-test-execution --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/orchestrating-test-execution .claude/skills/orchestrating-test-execution && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
orchestrating-test-execution
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
507 words
Files
7 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Test coordinate parallel test execution across multiple environments and frameworks.

  • Works in 7 steps: Analyze the existing test suite using… → Classify tests into execution tiers → Configure parallel execution for each tier → …
  • Performing specialized testing
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
  • Calls pytest, npx and jest

What it does

Orchestrating Test Execution is an agent skill from jeremylongshore/tons-of-skills-marketplace. Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts, reference files and assets (for example `assets/README.md`, `assets/configuration_template.yaml` and `assets/example_test_graph.json`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA, covering Unit testing and CI/CD. It works with JUnit. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Performing specialized testing
  • With phrases like orchestrate tests
  • Run parallel tests
  • Coordinate test execution

Example prompts

  • “orchestrate tests”
  • “run parallel tests”
  • “coordinate test execution”
  • “/orchestrating-test-execution”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:orchestrate-*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Analyze the existing test suite using Grep and Glob to catalog all test files, their framework, approximate run time, and dependency…
  2. Classify tests into execution tiers
  3. Configure parallel execution for each tier
  4. Create a CI pipeline configuration that runs tiers in parallel
  5. Implement intelligent retry logic for flaky tests
  6. Aggregate results from all parallel workers into a single report
  7. Write the orchestration configuration to the project's CI config file and validate it with a dry run.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(test:orchestrate-*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • pytest
    • npx
    • jest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • jestjs.io
    • pytest-xdist.readthedocs.io
    • playwright.dev
    • docs.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Orchestrating Test Execution loads about 1.3k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 507 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 507 words, ~1,259 tokens.

Download SKILL.mdSave it as .claude/skills/orchestrating-test-execution/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
orchestrating-test-execution
description
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(test:orchestrate-*)
compatibility
Designed for Claude Code
version
1.25.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
testing, orchestrating-test

Test Orchestrator

Overview

Coordinate parallel test execution across multiple test suites, frameworks, and environments. Manages test splitting, worker allocation, result aggregation, and intelligent retry strategies.

Prerequisites

  • Test runner with parallel execution support (Jest, Vitest, pytest-xdist, Playwright, or JUnit 5)
  • CI/CD platform configured (GitHub Actions, GitLab CI, CircleCI, or Jenkins)
  • Test suite with consistent pass rates (flaky tests identified and tagged)
  • Sufficient CI runner resources for parallel worker count
  • Test result reporting tool (JUnit XML, Allure, or equivalent)

Instructions

  1. Analyze the existing test suite using Grep and Glob to catalog all test files, their framework, approximate run time, and dependency requirements.
  2. Classify tests into execution tiers:
    • Tier 1 (Fast): Unit tests with no I/O -- target under 30 seconds total.
    • Tier 2 (Medium): Integration tests requiring local services -- target under 3 minutes.
    • Tier 3 (Slow): E2E and browser tests -- target under 10 minutes.
  3. Configure parallel execution for each tier:
    • Split unit tests across N workers using jest --shard=i/N or pytest -n auto.
    • Shard E2E tests by test file using Playwright --shard=i/N or Cypress parallelization.
    • Assign heavier integration tests to dedicated workers with more resources.
  4. Create a CI pipeline configuration that runs tiers in parallel:
    • Tier 1 and Tier 2 run concurrently on separate jobs.
    • Tier 3 runs after a fast pre-check gate passes.
    • Each tier reports results to a unified collection step.
  5. Implement intelligent retry logic for flaky tests:
    • Tag known flaky tests with @flaky or equivalent marker.
    • Retry failed tests up to 2 times before marking as failed.
    • Track flaky test frequency in a log file for triage.
  6. Aggregate results from all parallel workers into a single report:
    • Merge JUnit XML files from each shard.
    • Calculate total pass/fail/skip counts and execution time.
    • Identify the slowest tests for optimization targets.
  7. Write the orchestration configuration to the project's CI config file and validate it with a dry run.
Show full SKILL.md (195 more words)Show less

Output

  • CI pipeline configuration file (.github/workflows/test.yml, .gitlab-ci.yml, or equivalent)
  • Test sharding configuration with worker count and split strategy
  • Merged test result report in JUnit XML or JSON format
  • Execution timeline showing parallel job durations and bottlenecks
  • Flaky test inventory with retry counts and failure patterns

Error Handling

ErrorCauseSolution
Shard produces zero testsUneven test distribution or incorrect shard indexVerify shard count matches actual test file count; use file-based splitting
Worker out of memoryToo many parallel processes on one runnerReduce --maxWorkers or -n count; increase runner memory; use --workerIdleMemoryLimit
Test ordering dependencyTests pass in isolation but fail in specific shard orderAdd --randomize flag; fix shared state leaks; enforce test independence
Result aggregation mismatchMissing shard results due to job timeoutSet job-level timeouts higher than test timeouts; add result upload as a separate step
CI cache miss slowing startupDependencies not cached between parallel jobsConfigure dependency caching per lockfile hash; use a shared setup job

Examples

GitHub Actions matrix strategy for Jest sharding:

yaml
jobs:
  test:
    strategy:
      matrix:
        shard: [1, 2, 3, 4]
    steps:
      - run: npx jest --shard=${{ matrix.shard }}/4 --ci --reporters=jest-junit
      - uses: actions/upload-artifact@v4
        with:
          name: results-${{ matrix.shard }}
          path: junit.xml
  merge:
    needs: test
    steps:
      - uses: actions/download-artifact@v4
      - run: npx junit-merge -d results-* -o merged-results.xml

pytest-xdist parallel execution:

bash
pytest -n auto --dist worksteal -q --junitxml=results.xml

Playwright sharded execution:

bash
npx playwright test --shard=1/3 --reporter=junit

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references, assets) in skills/.curated/orchestrating-test-execution of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • assets/configuration_template.yaml
  • assets/example_test_graph.json
  • assets/test_report_template.html
  • references/README.md
  • scripts/README.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Orchestrating Test Execution next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Orchestrating Test Execution compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Orchestrating Test Execution this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Debug Playwright Prowquay/quay2.8k—~2.2kAutomated safety check: PassApache-2.0
Blue Teamgaasher/Agent-Loop-Skills174—~3.6kAutomated safety check: PassMIT
Quay Prow Triagequay/quay2.8k—~2.9kAutomated safety check: PassApache-2.0
Bats Shell Testing Patternswshobson/agents40k12 repos~1.3kAutomated safety check: PassMIT
Simple Modern Uvjlevy/simple-modern-uv301—~1.9kAutomated safety check: PassMIT

Similar skills

  • Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…

    2.8k GitHub stars~2.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Blue Team

    gaasher/Agent-Loop-Skills

    A skill your agent uses when the user has concrete failing cases in code or a guardrail/classifier/filter/prompt/API they own — a red-team failure catalogue OR a CI/CD test-failure report (failing…

    174 GitHub stars~3.6k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Diagnose any Quay Prow job failure end to end: prowjob.json - top-level build log - JUnit - resolved failing step - Playwright results.json when the failing step is Playwright, continuing through…

    2.8k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 12 repos~1.3k tokens
    Testing & QAAuto-check passed
  • Simple Modern Uv

    jlevy/simple-modern-uv

    Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.

    301 GitHub stars~1.9k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Writing gotest Tests

    mvrahden/go-test

    Guides writing, fixing and migrating tests in Go repositories that use the gotest suite framework, including version differences and CI setup.

    128 GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Orchestrating Test Execution

What does Orchestrating Test Execution do?

Test coordinate parallel test execution across multiple environments and frameworks. Orchestrating Test Execution is an agent skill from jeremylongshore/tons-of-skills-marketplace. Test coordinate parallel test execution across multiple environments and frameworks.

When should I use Orchestrating Test Execution?

Orchestrating Test Execution fits situations like: performing specialized testing; with phrases like orchestrate tests; run parallel tests; coordinate test execution.

How do I install Orchestrating Test Execution in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill orchestrating-test-execution -a claude-code`. Or copy the skill folder (skills/.curated/orchestrating-test-execution in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/orchestrating-test-execution in your project. Claude Code loads it when a task matches its description.

How do I install Orchestrating Test Execution in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill orchestrating-test-execution -a codex`. Or copy the skill folder (skills/.curated/orchestrating-test-execution in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/orchestrating-test-execution in your project. Codex loads it when a task matches its description.

Can I use Orchestrating Test Execution in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill orchestrating-test-execution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrating-test-execution, .gemini/skills/orchestrating-test-execution, .github/skills/orchestrating-test-execution and .opencode/skills/orchestrating-test-execution in your project.

What does Orchestrating Test Execution need to run?

Going by SKILL.md and its folder, Orchestrating Test Execution needs the command-line tools its instructions call (pytest, npx and jest). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(test:orchestrate-*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Orchestrating Test Execution access the network?

SKILL.md names 4 domains. As links in the text: jestjs.io, pytest-xdist.readthedocs.io, playwright.dev and docs.github.com. This is read from the text; nothing was executed.

Is Orchestrating Test Execution safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Orchestrating Test Execution use?

Orchestrating Test Execution is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Orchestrating Test Execution use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15 tokens, read only when the agent opens those files.

What are the alternatives to Orchestrating Test Execution?

Skills that share tags, products or a category with Orchestrating Test Execution: Debug Playwright Prow (quay/quay, 2.8k stars), Blue Team (gaasher/Agent-Loop-Skills, 174 stars), Quay Prow Triage (quay/quay, 2.8k stars) and Bats Shell Testing Patterns (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Orchestrating Test Execution?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.