test-orchestrator
Coordinate Testing Across Your Project
Test planning can drift when teams manage test types separately. This skill organizes coverage goals, quality gates, execution flow, and reporting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "test-orchestrator" from https://skillstore.io/skills/brownbull-test-orchestrator.md and its manifest at https://skillstore.io/api/skills/brownbull-test-orchestrator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "test-orchestrator". Plan tests for an authentication change.
Expected outcome:
A test plan covering public method unit tests, database integration checks, login and password reset E2E flows, performance targets, and security validation.
Using "test-orchestrator". Assess whether a feature is ready for CI gating.
Expected outcome:
A readiness summary with required coverage, failing test review, flaky test handling, retry policy, and release-blocking conditions.
Using "test-orchestrator". Coordinate testing after a user-service update.
Expected outcome:
A task breakdown for specialized test skills, expected status events, result reporting needs, and quality metrics to track.
Security Audit
SafeAll static findings are false positives caused by markdown code fences, inline skill names, and illustrative pseudocode in SKILL.md. No prompt injection, data exfiltration intent, or executable command guidance was found in the reviewed skill content.
Risk Factors
⚙️ External commands (20)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/brownbull-test-orchestrator/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/brownbull-test-orchestrator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/brownbull-test-orchestrator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brownbull-test-orchestrator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/brownbull-test-orchestrator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Brownbull. (2026). test-orchestrator security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brownbull-test-orchestrator/audits/8BibTeX citation
@techreport{brownbull-brownbull-test-orchestrator-2026,
author = {Brownbull},
title = {test-orchestrator security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/brownbull-test-orchestrator/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-orchestrator security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Brownbull"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/brownbull-test-orchestrator/audits/8"
identifiers:
- type: other
value: "skillstore:brownbull-test-orchestrator:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan Release Testing
Create a test plan that maps changed components to required test types, coverage goals, and quality gates.
Improve Coverage
Identify gaps in unit, integration, and E2E coverage before a feature reaches review.
Standardize CI Checks
Define pass criteria, failure handling, and reporting expectations for automated test pipelines.
Try These Prompts
Create a test plan for [component]. Include unit, integration, and E2E coverage goals.
Review the current tests for [feature]. Identify missing scenarios, weak assertions, and coverage risks.
Define quality gates for [release]. Include coverage thresholds, failure policies, performance checks, and security testing.
Build a testing coordination plan for [project change]. Assign work across unit, integration, E2E, performance, and security testing.
Best Practices
- Provide the changed component, affected workflows, and current test coverage before asking for a plan.
- Use the skill to define pass criteria before implementation work begins.
- Review flaky tests and slow suites as release risks, not only maintenance issues.
Avoid
- Using one test type as a substitute for complete quality coverage.
- Setting coverage thresholds without reviewing important user workflows.
- Ignoring test failures because retry logic eventually passes.