CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-qa

Review changes for correctness, security, accessibility, and performance. Use for scoped quality reviews or verification plans; bug fixes use oma-debug.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, lean operational definition for a QA agent: a prioritized review order, concrete tool commands, a severity rubric, reproducibility requirements, and a clearly sequenced workflow with validation and failure recovery. Its weaknesses are modest — slight redundancy between the Goal/Intent/Guardrails sections and references to resource files that are not present in this bundle.

Suggestions

De-duplicate the scheduling sections: fold "Goal" and "Intent signature" into a single "When to use" block, and remove the overlap between "Transitions" and Guardrails 1/5.

Ship the referenced bundle files (resources/execution-protocol.md, iso-quality.md, checklist.md, error-playbook.md) with the skill, or inline the checklist items, since the References section currently points at files not in the bundle.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no explanations of concepts Claude already knows — it states priorities, commands, and rules directly. Minor tightening is possible: the "Goal" and "Intent signature" sections overlap, and Guardrail 1/5 restate points already in "Transitions" (security priority, reproducible findings), which is the only thing keeping it from a 5.

4 / 5

Actionability

Concrete, executable guidance is present: named commands ("npm audit", "bandit -r .", "lighthouse <url>"), a defined severity rubric ("CRITICAL (security breach/data loss)..."), and hard output requirements ("Every finding must include file:line, description, and fix"). As an instruction-only skill this is actionable throughout; it stops short of a 5 only because several steps ("Detect the stack", "Analyze... against the applicable standards") rely on judgment rather than copy-paste-ready specifics.

4 / 5

Workflow Clarity

The 7-step "Canonical command path" gives a clear sequence with an explicit validation checkpoint ("Reproduce each candidate finding and reject false positives"), a dedicated "Failure and recovery" section for error feedback loops, and an external checklist (resources/checklist.md). This matches the anchor for clear sequence with explicit validation steps and feedback loops; the skill is review/read-heavy, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The SKILL.md is an appropriate overview with a References section that lists one-level-deep resources, each with an explicit condition for when to read it ("ISO quality guide... (standards-based review requested)"). However, none of the referenced files (resources/*.md, ../_shared/core/*, ../oma-observability/SKILL.md) exist in this bundle, so the references cannot be verified and several point outside the skill directory, which is a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

67%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, in third person, and covers both what the skill does and when to use it, with a useful negative trigger for the sibling debug skill. Its main weakness is thin natural trigger-term coverage — abstract phrases like "scoped quality reviews" and "verification plans" instead of the words users actually say (QA, audit, security review, test coverage).

Suggestions

Add natural trigger terms users would actually say, e.g. "Use for QA, security audits, performance or accessibility (WCAG) reviews, test-coverage analysis".

Include the oma-security boundary in the description (scanner-driven audits / pentest validation route elsewhere) to reduce overlap risk with a dedicated security skill.

DimensionReasoningScore

Specificity

"Review changes for correctness, security, accessibility, and performance" names the domain and enumerates four concrete review dimensions, which lists several specific capabilities with only minor gaps (test coverage and standards mapping appear only in the body, not the description). It is not a 5 because only one action verb ("review") is given rather than multiple distinct concrete actions.

4 / 5

Completeness

Both parts are explicit: the "what" ("Review changes for correctness, security, accessibility, and performance") and a "Use for..." clause ("Use for scoped quality reviews or verification plans"). It falls short of a 5 because the trigger phrases are somewhat abstract ("scoped quality reviews", "verification plans") rather than concrete user-utterable phrases, and the when-clause relies partly on a negative pointer ("bug fixes use oma-debug").

4 / 5

Trigger Term Quality

Trigger terms present are "quality reviews", "verification plans", and "bug fixes" — some relevant keywords, but common natural phrases users would say (QA, audit, security review, lint, test coverage, WCAG) are missing. It sits between anchor 3 (missing common variations/synonyms) and anchor 4, closer to 3 because coverage of natural synonyms is thin.

3 / 5

Distinctiveness Conflict Risk

The contrastive pointer "bug fixes use oma-debug" explicitly disambiguates from the sibling debug skill, and "scoped quality reviews" carves a niche. Minor overlap risk remains with adjacent skills (e.g., a security-review skill is only excluded in the body, not the description), so it does not reach a 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-qa/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.