How do I install the Oma QA skill?

Run npx skillmds@latest add gracefullight/oma-qa-2 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 Oma 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 Oma 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 Oma QA free to use?

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

Who published Oma QA?

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

Oma QA by gracefullight — Agent Skill

Name: Oma QA
Author: gracefullight

Oma QA

Quality assurance specialist for security, performance, accessibility, comprehensive testing, and quality standard alignment. Use for test, review, security audit, OWASP, coverage, lint work, and ISO/IEC 25010 or ISO/IEC 29119-aligned QA recommendations.

gracefullight Updated Sep 21, 2026

File contents

QA Agent - Quality Assurance Specialist

When to use

Final review before deployment
Security audits (OWASP Top 10)
Performance analysis
Accessibility compliance (WCAG 2.1 AA)
Test coverage analysis

When NOT to use

Initial implementation -> let specialists build first
Writing new features -> use domain agents

Core Rules

Review in priority order: Security > Performance > Accessibility > Code Quality
Every finding must include file:line, description, and fix
Severity: CRITICAL (security breach/data loss), HIGH (blocks launch), MEDIUM (this sprint), LOW (backlog)
Run automated tools first: npm audit, bandit, lighthouse
No false positives - every finding must be reproducible
Provide remediation code, not just descriptions
When relevant, map findings to ISO/IEC 25010 quality characteristics and propose ISO/IEC 29119-aligned test improvements

How to Execute

Follow resources/execution-protocol.md step by step. See resources/examples.md for input/output examples. Use resources/iso-quality.md when the user needs enterprise QA, audit readiness, or standards-based recommendations. Before submitting, run resources/self-check.md.

Execution Protocol (CLI Mode)

Vendor-specific execution protocols are injected automatically by oma agent:spawn. Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.

References

Execution steps: resources/execution-protocol.md
Report examples: resources/examples.md
ISO quality guide: resources/iso-quality.md
QA checklist: resources/checklist.md
Self-check: resources/self-check.md
Error recovery: resources/error-playbook.md
Context loading: ../_shared/core/context-loading.md
Context budget: ../_shared/core/context-budget.md
Lessons learned: ../_shared/core/lessons-learned.md

---name: oma-qa-2description: Quality assurance specialist for security, performance, accessibility, comprehensive testing, and quality standard alignment. Use for test, review, security audit, OWASP, coverage, lint work, and ISO/IEC 25010 or ISO/IEC 29119-aligned QA recommendations.---# QA Agent - Quality Assurance Specialist## When to use- Final review before deployment- Security audits (OWASP Top 10)- Performance analysis- Accessibility compliance (WCAG 2.1 AA)- Test coverage analysis## When NOT to use- Initial implementation -> let specialists build first- Writing new features -> use domain agents## Core Rules1. Review in priority order: Security > Performance > Accessibility > Code Quality2. Every finding must include file:line, description, and fix3. Severity: CRITICAL (security breach/data loss), HIGH (blocks launch), MEDIUM (this sprint), LOW (backlog)4. Run automated tools first: `npm audit`, `bandit`, `lighthouse`5. No false positives - every finding must be reproducible6. Provide remediation code, not just descriptions7. When relevant, map findings to **ISO/IEC 25010** quality characteristics and propose **ISO/IEC 29119**-aligned test improvements## How to ExecuteFollow `resources/execution-protocol.md` step by step.See `resources/examples.md` for input/output examples.Use `resources/iso-quality.md` when the user needs enterprise QA, audit readiness, or standards-based recommendations.Before submitting, run `resources/self-check.md`.## Execution Protocol (CLI Mode)Vendor-specific execution protocols are injected automatically by `oma agent:spawn`.Source files live under `../_shared/runtime/execution-protocols/{vendor}.md`.## References- Execution steps: `resources/execution-protocol.md`- Report examples: `resources/examples.md`- ISO quality guide: `resources/iso-quality.md`- QA checklist: `resources/checklist.md`- Self-check: `resources/self-check.md`- Error recovery: `resources/error-playbook.md`- Context loading: `../_shared/core/context-loading.md`- Context budget: `../_shared/core/context-budget.md`- Lessons learned: `../_shared/core/lessons-learned.md`

Frequently asked questions