aiox-qa

Activate Quinn (qa) for Test Architect & Quality Advisor. Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and...

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/AIOX/agents/qa/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with concrete commands and well-sequenced validation-backed workflows, but it is verbose and monolithic — a giant inline YAML configuration block with duplicated command listings and no progressive disclosure into bundle files. Splitting configuration detail into referenced files and deduplicating the command list would improve token efficiency and navigability.

Suggestions

Move the large CodeRabbit integration configuration (workflow pseudocode, platform notes, execution_guidelines) into a referenced bundle file and keep SKILL.md to a concise overview with a clearly signaled link.

Remove the duplicated command listing — keep commands in one place (the YAML 'commands' block or the 'Quick Commands' section) and reference the other rather than repeating both.

Add a short top-of-body overview/Quick Start that orients the reader before the full YAML definition, improving progressive disclosure for a skill well over 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational rather than padded with basic-concept fluff, but it carries notable redundancy — the command list appears both in the YAML block and again in the 'Quick Commands' section — and the CodeRabbit execution_guidelines could be tightened.	2 / 3
Actionability	It provides concrete, executable guidance: specific CLI invocations ('~/.local/bin/coderabbit --prompt-only -t committed --base ${DEFAULT_BRANCH:-main}'), explicit git operations, command syntax with args, and concrete file paths, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with validation checkpoints — the activation STEP 1-5 sequence and the CodeRabbit self-healing loop (parse severity, break/continue, FAIL after max iterations) provide an explicit validate-fix-retry feedback loop.	3 / 3
Progressive Disclosure	Section headings and a one-level-deep dependency listing give some structure, but the core agent definition is a monolithic inline YAML block (~360 lines) with no bundle files to offload detail, so content that should be separate remains inline.	2 / 3
	Total	10 / 12 Passed

Description

60%Weight 40%Scale 1-3

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 names a clear QA domain with several concrete capabilities and an explicit 'Use for' trigger, but it is cut off mid-sentence and leans on the generic phrase 'code improvement'. Tightening the trigger vocabulary and completing the truncated list would materially raise its quality.

Suggestions

Complete the truncated description — replace the trailing 'and...' with a finite, well-scoped list of capabilities so the 'what' is fully resolved.

Add common natural trigger terms users would actually say (e.g., 'testing', 'test coverage', 'test strategy', 'QA review') alongside the existing QA vocabulary.

Replace or scope the generic 'code improvement' with a QA-specific framing (e.g., 'advisory code-quality findings') to reduce overlap with general code-review skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'test architecture review, quality gate decisions', 'requirements traceability, risk assessment' — matching the anchor for enumerating several specific capabilities rather than vague language.	3 / 3
Completeness	It supplies both a 'Use for ...' trigger and a capabilities statement, but the description is truncated mid-sentence ('...risk assessment, and...'), leaving the 'what' enumeration incomplete rather than cleanly resolved.	2 / 3
Trigger Term Quality	Includes relevant QA terms ('quality gate decisions', 'requirements traceability', 'risk assessment') but misses common natural variations a user might say such as 'testing', 'test coverage', or 'unit tests', so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The QA/test-architecture niche is reasonably distinct, yet the generic 'code improvement' term and the trailing ellipsis blur its boundaries with general code-review or dev skills, risking overlap.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .claude/skills/AIOX/agents/qa/SKILL.md
Commit: 0b32b68

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.