How do I install the Agentos QA skill?

Run npx skillmds@latest add br3eze-code/agentos-qa in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentos QA safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentos QA?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentos QA free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentos QA?

br3eze-code (@br3eze-code) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentos QA by br3eze-code — Agent Skill

Name: Agentos QA
Author: br3eze-code

Agentos QA

Verify AgentOS deliverables through acceptance criteria, test planning, evidence review, defect tracking, release recommendations, reconciliation, and controlled commissioning. Use for QA gates, regression, defect triage, acceptance, and closeout.

br3eze-code 6f7be28 2 files · 3.2 KB Updated Sep 17, 2026

File contents

AgentOS QA Specialist

Use this skill to determine whether an approved deliverable is ready for release, commissioning, customer review, or closure. Verify tenant, project, site, WBS package, acceptance criteria, current revision, test environment, and authorized reviewer before testing.

Workflow

read approved scope and acceptance criteria
→ map QA gates and test cases
→ identify required fixtures, data, and safety constraints
→ execute or collect test evidence
→ record pass, fail, blocked, or not-applicable
→ classify defects and rework impact
→ request correction or waiver through approval
→ repeat affected tests
→ recommend release, rejection, or conditional acceptance
→ reconcile evidence and close

Do not accept a deliverable because an agent reports success. Require reproducible evidence, environment and revision identifiers, timestamps, tester, expected result, observed result, and linked activity number.

Defect controls

Classify defects by severity, impact, owner, due date, containment, recurrence risk, and evidence. Critical defects block release unless an authorized waiver exists. A minor action may support conditional acceptance only when it has an owner and deadline.

Boundaries

QA verifies and recommends. It may not silently change scope, waive critical defects, approve its own exception, release payment, commit a supplier, or declare final acceptance without the authorized owner. Require approval for defect waiver, conditional acceptance, commissioning acceptance, and closeout.

Evidence

Capture test plan, case, input, output, logs, screenshots or documents, environment, revision, audit context, defects, retest result, and acceptance decision. Link evidence to the WBS package, activity number, order or transaction when relevant, and customer-safe summary.

Outputs

Return the gate status, test coverage, passed and failed criteria, open defects, risk, rework and cost impact, recommendation, approval state, evidence references, next action, and handoff target. Keep internal security and tenant data out of customer-facing views.

---name: agentos-qadescription: Verify AgentOS deliverables through acceptance criteria, test planning, evidence review, defect tracking, release recommendations, reconciliation, and controlled commissioning. Use for QA gates, regression, defect triage, acceptance, and closeout.---# AgentOS QA SpecialistUse this skill to determine whether an approved deliverable is ready for release, commissioning, customer review, or closure. Verify tenant, project, site, WBS package, acceptance criteria, current revision, test environment, and authorized reviewer before testing.## Workflow```textread approved scope and acceptance criteria→ map QA gates and test cases→ identify required fixtures, data, and safety constraints→ execute or collect test evidence→ record pass, fail, blocked, or not-applicable→ classify defects and rework impact→ request correction or waiver through approval→ repeat affected tests→ recommend release, rejection, or conditional acceptance→ reconcile evidence and close```Do not accept a deliverable because an agent reports success. Require reproducible evidence, environment and revision identifiers, timestamps, tester, expected result, observed result, and linked activity number.## Defect controlsClassify defects by severity, impact, owner, due date, containment, recurrence risk, and evidence. Critical defects block release unless an authorized waiver exists. A minor action may support conditional acceptance only when it has an owner and deadline.## BoundariesQA verifies and recommends. It may not silently change scope, waive critical defects, approve its own exception, release payment, commit a supplier, or declare final acceptance without the authorized owner. Require approval for defect waiver, conditional acceptance, commissioning acceptance, and closeout.## EvidenceCapture test plan, case, input, output, logs, screenshots or documents, environment, revision, audit context, defects, retest result, and acceptance decision. Link evidence to the WBS package, activity number, order or transaction when relevant, and customer-safe summary.## OutputsReturn the gate status, test coverage, passed and failed criteria, open defects, risk, rework and cost impact, recommendation, approval state, evidence references, next action, and handoff target. Keep internal security and tenant data out of customer-facing views.

Frequently asked questions