CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa-expert

Sets up QA testing processes: test strategies, Google Testing Standards test cases, P0-P4 bug tracking, quality metrics, progress reports, autonomous execution via master prompts, and OWASP security testing, with third-party QA handoff docs. Use when establishing QA infrastructure, writing test cases, executing test plans, or tracking bugs. Not for auditing an already-rendered UI (use frontend-visual-qa).

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-engineered instruction skill: executable commands, explicit validation checkpoints and recovery procedures for batch/autonomous execution, and clean one-level-deep progressive disclosure with all referenced bundle files present. The only real improvement is tightening duplicated coverage of initialization and autonomous execution scattered across multiple sections.

Suggestions

Merge the 'Autonomous Execution (⭐ Recommended)' section into Core Capability 3 (or vice versa) — the master prompt, its features, and its usage are currently covered in three separate places.

Drop the duplicated init command from Core Capability 1 (Quick Start already shows it verbatim) or replace one instance with a pointer.

Trim the 'Reference Documents' / 'Scripts' / 'Assets & Templates' directory sections to only files not already linked inline, or keep only the inline links, to cut redundant tokens.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no basic-concept padding, but has minor redundancy: the init command appears in both Quick Start and Core Capability 1, autonomous execution is covered in three places (Quick Start, Capability 3, and the dedicated 'Autonomous Execution' section), and the 'Reference Documents'/'Scripts' sections re-list links already given inline. This fits 'efficient; minor instances ... that could be trimmed' rather than the lean 5.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready 'uv run' commands for both scripts, concrete field requirements (Bug ID, Severity, Steps to Reproduce, Environment), explicit severity semantics (P0 24h fix → P4 optional), a concrete test-case ID format (TC-[CATEGORY]-[NUMBER]), and explicit CSV status conventions ('✅ PASSED' / '❌ FAILED', 'Completed'). Placeholder resolution for <qa-expert-dir> is explained.

5 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced with explicit checkpoints and feedback loops: manual execution mandates updating the tracking CSV 'immediately after EACH test (never batch)' and filing a bug on failure; the ground-truth principle guards against doc/CSV drift; interruption recovery requires reading back checkpoints and reconciling side effects; the metrics CLI's ✅/❌ gate output and 'stop on P0 bugs' provide validation for the batch/autonomous operations, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview: every detailed guide (master_qa_prompt, google_testing_standards, ground_truth_principle, day1_onboarding, five acceptance-recipe references, TEST-CASE-TEMPLATE.md) is one level deep, clearly signaled at point of use, and all referenced paths exist in the bundle. Dedicated 'Reference Documents', 'Assets & Templates', and 'Scripts' sections aid discovery.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong description: third-person voice, comprehensive and specific capability list, explicit 'Use when' triggers, and a negative boundary that disambiguates a neighboring skill. Only minor upside remains in adding a few more natural trigger synonyms.

DimensionReasoningScore

Specificity

The description enumerates concrete actions: 'test strategies, Google Testing Standards test cases, P0-P4 bug tracking, quality metrics, progress reports, autonomous execution via master prompts, and OWASP security testing, with third-party QA handoff docs' — comprehensive coverage of specific capabilities, not vague domain labels.

5 / 5

Completeness

Explicitly answers what ('Sets up QA testing processes: ...') and when ('Use when establishing QA infrastructure, writing test cases, executing test plans, or tracking bugs'), with concrete trigger phrases and an additional negative boundary ('Not for auditing an already-rendered UI').

5 / 5

Trigger Term Quality

'establishing QA infrastructure', 'writing test cases', 'executing test plans', 'tracking bugs' are natural phrases users would say. Coverage is good but a few common synonyms ('quality assurance', 'test suite', 'regression testing') are absent, matching the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Clear QA-infrastructure niche with distinct triggers, and it proactively disambiguates the one adjacent skill ('Not for auditing an already-rendered UI (use frontend-visual-qa)'), minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

daymade/claude-code-skills

Path

qa-expert/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.