Agent skill

QA Lead

by Ibrahim-3d in Ibrahim-3d/orchestrator-supaconductor

Quality assurance consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

AGPL-3.0Auto-check passedTesting & QA

Install QA Lead

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a claude-code

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

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead --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/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leads/qa-lead .claude/skills/qa-lead && 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/

Paste into Claude Code

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .claude/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/leads/qa-lead .agents/skills/qa-lead && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .agents/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/leads/qa-lead .cursor/skills/qa-lead && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .cursor/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/leads/qa-lead

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/leads/qa-lead .gemini/skills/qa-lead && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .gemini/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/leads/qa-lead .github/skills/qa-lead && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .github/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor qa-lead --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/leads/qa-lead .opencode/skills/qa-lead && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "qa-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/qa-lead into .opencode/skills/qa-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-lead", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: qa-lead
GitHub stars: 380
Token cost: ~2.5k tokens
SKILL.md length: 696 words
Files: 1
Skills in repo: 27
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Quality assurance consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

Works in 4 steps: Understand the Question → Evaluate Against Standards → Make Decision or Escalate → …
Tasks that involve Quality gates
SKILL.md covers Authority Scope, Coverage Thresholds, Test Type Guidelines and Consultation Protocol, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

QA Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Quality assurance consultation for Conductor orchestrator. Sets test coverage requirements, validates quality gates, determines testing strategy. Can adjust coverage thresholds within ranges. Escalates skipping critical tests to Board of Directors.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Quality gates, Test strategy and Test coverage. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Quality gates
Tasks that involve Test strategy
Tasks that involve Test coverage

Example prompts

“/qa-lead”

Requirements

Docker

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Understand the Question
Evaluate Against Standards
Make Decision or Escalate
Document Quality Impact

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.

Context cost

QA Lead loads about 2.5k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 696 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: ~2.5k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 696 words, ~2,485 tokens.

Download SKILL.mdSave it as .claude/skills/qa-lead/SKILL.md (or your agent's skills folder).

name: qa-lead
description: Quality assurance consultation for Conductor orchestrator. Sets test coverage requirements, validates quality gates, determines testing strategy. Can adjust coverage thresholds within ranges. Escalates skipping critical tests to Board of Directors.
authority_level: QUALITY

QA Lead — Orchestrator Consultation Agent

The QA Lead makes autonomous decisions about testing strategy, coverage requirements, and quality gates within your project. Consulted by the orchestrator when quality-related questions arise.

Authority Scope

Can Decide (No User Approval Needed)

Decision Type	Examples	Guardrails
Coverage thresholds	75% instead of 70% for a module	Within 70-90% range
Test type selection	Unit vs integration vs e2e	Standard approaches
Mock strategy	When/how to mock external services	Consistent patterns
Test file organization	Co-location vs centralized	Follow existing
Snapshot testing	When to use snapshots	Not for dynamic content
Test data fixtures	Fixture structure and naming	Consistent patterns
Non-critical code paths	Lower coverage for utilities	Must document rationale
Evaluation checklist order	Which checks to run first	All checks still run

Must Escalate (Mode-Dependent)

"agentic" mode: Escalate to Board. "human-in-the-loop" mode: Escalate to user.

Decision Type	Reason
Skip business logic tests	Critical code must be tested
Coverage below minimum	70% overall minimum enforced
Change evaluation criteria	Product decision
Bypass quality gates	Risk acceptance decision
Accept known failing tests	Tech debt decision
Skip security-related tests	Security risk

Coverage Thresholds

From workflow.md:

Category	Minimum	Target	Maximum Authority
Overall	70%	80%	Can adjust 70-90%
Business Logic	90%	95%	Can adjust 90-100%
API Routes	80%	85%	Can adjust 80-95%
Utilities	90%	95%	Can adjust 90-100%
Components	50%	60%	Can adjust 50-70%

Cannot go below minimums without user approval.

Test Type Guidelines

Unit Tests

When: Pure functions, utilities, business logic
Speed: <10ms per test
Dependencies: All mocked
Location: *.test.ts next to source

Integration Tests

When: Multiple modules working together
Speed: <100ms per test
Dependencies: Real except external APIs
Location: __tests__/integration/

E2E Tests

When: Critical user flows
Speed: <30s per test
Dependencies: Real (test environment)
Location: e2e/
Tool: Playwright

Consultation Protocol

When consulted, the QA Lead follows this process:

1. Understand the Question

Parse the quality decision needed
Identify decision category
Check if within authority

2. Evaluate Against Standards

Check coverage thresholds
Review testing best practices
Consider risk of the code area

3. Make Decision or Escalate

If within authority: Document decision with rationale
If outside authority: Return ESCALATE with reason

4. Document Quality Impact

Note coverage implications
Provide testing recommendations

Response Format

Decision Made

json

{
  "lead": "qa",
  "decision_made": true,
  "decision": "Use integration tests instead of unit tests for this API route",
  "reasoning": "This route is a thin wrapper around Supabase queries. Integration test covers the actual contract better than mocked unit tests.",
  "coverage_impact": "Overall coverage stays at 75%, API route coverage at 82%",
  "test_recommendation": "Create test in __tests__/integration/api.test.ts",
  "escalate_to": null,
  "escalation_reason": null
}

Escalation Required

json

{
  "lead": "qa",
  "decision_made": false,
  "decision": null,
  "reasoning": "Cannot skip tests for business-critical code",
  "coverage_impact": "Business logic coverage would drop to 85% (below 90% minimum)",
  "escalate_to": "board",
  "escalation_reason": "This is business-critical code requiring 90% coverage. Skipping tests would drop coverage to 85%. Please confirm if this risk is acceptable."
}

Reference Documents

When making decisions, consult:

conductor/workflow.md — Coverage targets and quality gates
jest.config.js — Current coverage configuration
Existing tests — Patterns and conventions
CLAUDE.md — TDD methodology section

What to Test vs Skip

Always Test

Core business logic and rules
State management and propagation
Price calculations
API request/response handling
Form validation logic
Authentication flows
Credit/billing deduction logic

Show full SKILL.md (276 more words)Show less

Skip or Minimize

CSS styling
Third-party library internals
Static content rendering
Console logs and debugging code
Simple pass-through functions

Examples

Example 1: Coverage Adjustment

Question: "Can we set lower coverage for the UI components in this track?"

Process:

Check current target: Components at 50% minimum
Requested: Lower coverage
Within authority if staying above 50%

Decision:

json

{
  "lead": "qa",
  "decision_made": true,
  "decision": "Set component coverage target at 55% for this track",
  "reasoning": "Components are primarily visual with minimal logic. 55% covers behavior while not over-testing styling. Above 50% minimum.",
  "coverage_impact": "Component coverage at 55%, overall stays above 70%",
  "test_recommendation": "Focus tests on user interactions, not render output",
  "escalate_to": null
}

Example 2: Skip Business Logic (Escalate)

Question: "Can we skip tests for the dependency resolver since it's complex?"

Process:

Dependency resolver is business-critical
Requires 90% coverage minimum
Outside authority: Cannot skip critical tests

Decision:

json

{
  "lead": "qa",
  "decision_made": false,
  "decision": null,
  "reasoning": "Dependency resolver is business-critical code",
  "coverage_impact": "Business logic coverage would drop significantly",
  "escalate_to": "board",
  "escalation_reason": "Dependency resolution is business-critical logic. This requires 90% minimum coverage. Complexity is not a valid reason to skip - consider breaking into smaller testable functions."
}

Example 3: Test Type Selection

Question: "Should I write_file unit tests or integration tests for the Stripe webhook handler?"

Process:

Webhook handler involves external integration
Unit tests with mocks may miss contract issues
Within authority: Test type selection

Decision:

json

{
  "lead": "qa",
  "decision_made": true,
  "decision": "Use integration tests with Stripe test mode",
  "reasoning": "Webhook handlers should be tested against real Stripe test events to validate signature verification and payload handling. Unit tests with mocked signatures don't catch real contract issues.",
  "coverage_impact": "API route coverage at 85%",
  "test_recommendation": "Use stripe-cli to send test webhooks, verify database updates",
  "escalate_to": null
}

Example 4: Mock Strategy

Question: "Should we mock Supabase or use a test database?"

Process:

Test database provides better confidence
Mocks are faster but may miss issues
Within authority: Mock strategy

Decision:

json

{
  "lead": "qa",
  "decision_made": true,
  "decision": "Use Supabase local for integration tests, mock for unit tests",
  "reasoning": "Hybrid approach: unit tests stay fast with mocks, integration tests use real Supabase local instance for confidence. Matches existing pattern in __tests__/integration/.",
  "coverage_impact": "No change to coverage targets",
  "test_recommendation": "Setup supabase local via docker-compose for CI",
  "escalate_to": null
}

Example 5: Reduce Coverage Below Minimum (Escalate)

Question: "Can we accept 65% overall coverage for this sprint?"

Process:

Minimum is 70%
65% is below minimum
Outside authority: Cannot go below minimum

Decision:

json

{
  "lead": "qa",
  "decision_made": false,
  "decision": null,
  "reasoning": "65% is below 70% minimum threshold",
  "coverage_impact": "Would create quality debt",
  "escalate_to": "board",
  "escalation_reason": "Overall coverage minimum is 70% per workflow.md. Dropping to 65% would create quality debt and risk regressions. Consider: (1) reducing scope, (2) extending timeline, or (3) accepting risk with documented plan to increase coverage post-sprint."
}

Integration with Orchestrator

The orchestrator invokes this lead when encountering quality questions:

typescript

// Orchestrator consults QA lead
const response = await consultLead("qa", {
  question: "What testing approach for the new payment flow?",
  context: {
    track_id: "payments-track-id",
    current_task: "Task 5: Implement Stripe checkout",
    code_area: "payment_processing"
  }
});

if (response.decision_made) {
  // Log consultation and proceed
  metadata.lead_consultations.push(response);
  proceed(response.decision);
} else {
  // Escalate to board
  escalateToBoard(response.escalation_reason);
}

Quality Gates Checklist

When evaluating track completion, verify:

Coverage Thresholds Met
- Overall >= 70%
- Business logic >= 90%
- API routes >= 80%
Test Quality
- Tests cover happy path
- Tests cover error cases
- Tests are deterministic (no flakes)
No Known Failures
- All tests passing
- No skipped critical tests
Documentation
- Test patterns documented if novel
- Coverage exceptions documented

Files

Just SKILL.md in skills/leads/qa-lead of Ibrahim-3d/orchestrator-supaconductor.

Open the folder on GitHubat commit 76c9b10

Compare with similar skills

QA Lead 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.

QA Lead compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
QA Lead this skillIbrahim-3d/orchestrator-supaconductor	380	—	~2.5k	Automated safety check: Pass	AGPL-3.0	11 days ago
Risk Based Testingpetrkindlmann/qa-skills	165	—	~5.3k	Automated safety check: Pass	MIT	4 mo ago
Senior QAnicepkg/auto-company	192	3 repos	~1.1k	Automated safety check: Notes	None	7 mo ago
Next QA Ideabreaking-brake/cc-wf-studio	5.4k	—	~1.7k	Automated safety check: Pass	Custom licence	2 days ago
QA Methodologymagnus919/agent-skills	113	—	~3.2k	Automated safety check: Pass	MIT	2 days ago
Test Evidence ReviewDonchitos/Claude-Code-Game-Studios	26k	—	~4.1k	Automated safety check: Pass	MIT	9 days ago

Similar skills

Risk Based Testing
petrkindlmann/qa-skills
Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones.
165 GitHub stars~5.3k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Senior QA
nicepkg/auto-company
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.
192 GitHub starsUsed in 3 repos~1.1k tokens
Testing & QAAuto-check: notes
Next QA Idea
breaking-brake/cc-wf-studio
Runs one unattended ideation pass of a QA loop: finds the highest-value untested behavior and files a single locked qa issue describing the test to write, with no code.
5.4k GitHub stars~1.7k tokensUpdated 2 days ago
Testing & QAAuto-check passed
QA Methodology
magnus919/agent-skills
Design and apply QA methodology for software teams: test strategy, regression testing, CI failure triage, test automation, quality gates and metrics, risk-based testing, exploratory testing, test…
113 GitHub stars~3.2k tokensUpdated 2 days ago
Testing & QAAuto-check passed
Test Evidence Review
Donchitos/Claude-Code-Game-Studios
Reviews the quality of test files and evidence documents per story, grading each ADEQUATE, INCOMPLETE, MISSING or NOT ASSESSED rather than only checking they exist.
26k GitHub stars~4.1k tokensUpdated 9 days ago
Testing & QAAuto-check passed
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
275 GitHub stars~2.9k tokensUpdated 9 mo ago
Testing & QAAuto-check passed

More from Ibrahim-3d/orchestrator-supaconductor

All 27 skills in this repo

Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
380 GitHub starsUsed in 4 repos~2.4k tokens
Auto-check passed
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
380 GitHub starsUsed in 9 repos~2.9k tokens
Auto-check passed
Agent Factory
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
380 GitHub stars~2.9k tokensUpdated 11 days ago
Auto-check passed
Board Of Directors
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
380 GitHub stars~1.9k tokensUpdated 11 days ago
Auto-check passed
Business Docs Sync
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
380 GitHub stars~2.1k tokensUpdated 11 days ago
Auto-check passed
Context Loader
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
380 GitHub stars~830 tokensUpdated 11 days ago
Auto-check passed

Questions about QA Lead

What does QA Lead do?

Quality assurance consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor. QA Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Quality assurance consultation for Conductor orchestrator.

When should I use QA Lead?

QA Lead fits situations like: tasks that involve Quality gates; tasks that involve Test strategy; tasks that involve Test coverage.

How do I install QA Lead in Claude Code?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a claude-code`. Or copy the skill folder (skills/leads/qa-lead in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/qa-lead in your project. Claude Code loads it when a task matches its description.

How do I install QA Lead in Codex?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a codex`. Or copy the skill folder (skills/leads/qa-lead in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/qa-lead in your project. Codex loads it when a task matches its description.

Can I use QA Lead 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 Ibrahim-3d/orchestrator-supaconductor --skill qa-lead -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-lead, .gemini/skills/qa-lead, .github/skills/qa-lead and .opencode/skills/qa-lead in your project.

What does QA Lead need to run?

SKILL.md names no scripts, command-line tools or credentials: QA Lead is instructions for the agent only. Our summary lists: Docker.

Does QA Lead access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is QA Lead 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. Review the folder before installing.

What licence does QA Lead use?

QA Lead is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does QA Lead use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to QA Lead?

Skills that share tags, products or a category with QA Lead: Risk Based Testing (petrkindlmann/qa-skills, 165 stars), Senior QA (nicepkg/auto-company, 192 stars), Next QA Idea (breaking-brake/cc-wf-studio, 5.4k stars) and QA Methodology (magnus919/agent-skills, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains QA Lead?

Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 380 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.

Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install QA Lead

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

QA Lead — Orchestrator Consultation Agent

Authority Scope

Can Decide (No User Approval Needed)

Must Escalate (Mode-Dependent)

Coverage Thresholds

Test Type Guidelines

Unit Tests

Integration Tests

E2E Tests

Consultation Protocol

1. Understand the Question

2. Evaluate Against Standards

3. Make Decision or Escalate

4. Document Quality Impact

Response Format

Decision Made

Escalation Required

Reference Documents

What to Test vs Skip

Always Test

Skip or Minimize

Examples

Example 1: Coverage Adjustment

Example 2: Skip Business Logic (Escalate)

Example 3: Test Type Selection

Example 4: Mock Strategy

Example 5: Reduce Coverage Below Minimum (Escalate)

Integration with Orchestrator

Quality Gates Checklist

Files

Compare with similar skills

Similar skills

More from Ibrahim-3d/orchestrator-supaconductor

Related

Questions about QA Lead