CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-qa

QA workflow for testing a feature or task implementation. Analyzes changes, produces test plans, and describes concrete test scenarios. Use when user says "test this", "write test plan", "what should I test", or "QA this branch".

Quality

80%

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

Fix and improve this skill with Tessl

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

Quality

Content

71%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-structured router skill: clear sequential pipeline, concrete config/slug handling, and exemplary progressive disclosure into three real reference files. The main weakness is verbosity — generic interaction policy, language-specific examples, and duplicated skill-context precedence rules inflate the body without adding QA-specific value.

Suggestions

Trim the 'Runtime-aware questions' section to 2-3 lines summarizing the contract (use an available question tool, else plain text; never prompt in non-interactive mode) and move the detailed rules to a shared reference, since they are generic interaction policy rather than QA-specific guidance.

Remove the duplicated skill-context precedence rules — Step 0.1's 'How to apply skill-context rules' repeats the 'Shared project skill-context' section; state the precedence rule once.

Drop the language-specific 'artifact_language = ru' example paragraph and keep only the general translation rule plus the technical_terms_policy list; the Russian-specific detail adds tokens without changing behavior.

DimensionReasoningScore

Conciseness

The workflow and config steps are dense and useful, but the generic "Runtime-aware questions" interaction contract, the language-specific "artifact_language = ru" paragraph, and skill-context precedence rules stated twice ("Shared project skill-context" vs Step 0.1) are unnecessary or duplicated. Mostly efficient with padding that could be trimmed, matching anchor 3 rather than anchor 2's heavily padded profile or anchor 4's minor-trim profile.

3 / 5

Actionability

Concrete file paths, exact commands ("git branch --show-current", "git hash-object --stdin <<< \"<resolved_branch>\""), explicit defaults, and a fully specified three-step slug algorithm give mostly executable guidance. Missing inline samples of the generated artifacts keeps it below anchor 5's copy-paste-ready coverage of common cases.

4 / 5

Workflow Clarity

The pipeline is clearly sequenced (change-summary → test-plan → test-cases) with an explicit mode table, hard dependency gates ("MUST NOT create a test-plan without a change-summary"), and failure handling ("stop the pipeline and report which stage failed"). No explicit validation/verification of generated artifacts prevents anchor 5.

4 / 5

Progressive Disclosure

The body is a clear router/overview with well-signaled one-level-deep references (references/CHANGE-SUMMARY.md, TEST-PLAN.md, TEST-CASES.md — all present in the bundle), and mode-specific detail is appropriately split into those files. Easy navigation with no nested references.

5 / 5

Total

16

/

20

Passed

Description

83%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: concrete third-person capability statements paired with an explicit 'Use when' clause containing multiple natural, quoted trigger phrases. The only weaknesses are minor — a few missing trigger variations and slight overlap risk with related testing skills.

DimensionReasoningScore

Specificity

"Analyzes changes, produces test plans, and describes concrete test scenarios" lists several specific third-person actions with only minor gaps in coverage (e.g., risk assessment is implied but not stated). It exceeds the 1-2 concrete actions of anchor 3 but does not meet anchor 5's comprehensiveness.

4 / 5

Completeness

It clearly answers both what ("Analyzes changes, produces test plans, and describes concrete test scenarios") and when ("Use when user says 'test this', 'write test plan'...") with concrete quoted trigger phrases, exactly matching the anchor-5 pattern. Not 4, because the 'when' clause is already fully explicit with multiple triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases like "test this", "write test plan", "what should I test", and "QA this branch" match what users would actually say. A few natural variations (e.g., "create test cases", "check this feature") are missing, keeping it below anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The QA-planning niche with triggers like "QA this branch" is mostly distinct, with only minor overlap risk against generic test-writing or code-review skills. Not 5, because adjacent skills for automated test generation could plausibly compete for some triggers.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-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.