CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factory-qa

Prove one task's acceptance criteria at the cheapest test layer that runs the real product code, extending the project's feature specs, record a test plan and a test-gap ledger, and capture screenshots for the pull request. Use for the QA stage, after work and before review, when FACTORY.json enables stages.qa.

Quality

97%

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

100%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 an exemplar skill body: lean imperative instructions with zero padding, fully executable commands and templates, a clearly sequenced workflow with validation and feedback loops, and a clean overview-plus-references structure. Every dimension lands on the top anchor without ambiguity.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes competence throughout — e.g. "Read product code only where a test needs a selector, a route, or a fixture" and "Never use `pkill -f` with a pattern that also appears in your own command line" — with no explanation of concepts Claude already knows. The few rationale sentences ("dev servers often listen on IPv6 only", "means nothing once the ticket closes") are short, non-obvious, and improve adherence rather than pad.

5 / 5

Actionability

Fully executable guidance: copy-paste-ready commands (`pnpm exec playwright test <file> --timeout=15000 --max-failures=1`, `pytest tests/api/test_orders.py -x -k create`, `cmd & pid=$!`), complete markdown templates for test-plan.md and ledger.md, concrete naming examples (`live-updates.e2e.ts`, `screenshots/ac2-filter-after-reload.png`), and named harnesses (Django's test client, FastAPI's `TestClient`, `supertest`, Rails request specs) covering the common cases.

5 / 5

Workflow Clarity

A clear sequence (read `.factory/CONTEXT.md` → sort criteria observable/internal → choose the cheapest layer → write one test per criterion → record plan and ledger → output the template) with explicit validation checkpoints ("Run only that test", "stop at the first failure") and feedback loops ("Fix the test with a small edit and run it again"; "A failure that shows the product misses the criterion is a finding, not something to fix"). Validation is present throughout, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The body is a well-organized overview that delegates detail through three clearly signaled, one-level-deep references — [references/api.md], [references/playwright.md], and [references/output.md] — each verified to exist and appropriately scoped (34, 29, and 26 lines). Content is split at the right boundaries: per-layer testing detail, tool-specific practices, and the output template all live outside the main file.

5 / 5

Total

20

/

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: it names the skill's concrete actions comprehensively, gives an explicit and unusually specific when-clause tied to pipeline position and a config flag, and is tightly scoped to a niche with negligible conflict risk. The only weakness is keyword coverage that lacks synonyms a user might naturally say.

DimensionReasoningScore

Specificity

Lists four concrete actions covering the skill's full scope: "Prove one task's acceptance criteria at the cheapest test layer that runs the real product code", "extending the project's feature specs", "record a test plan and a test-gap ledger", and "capture screenshots for the pull request". This matches the comprehensive-coverage anchor rather than 4, since no meaningful action of the skill is missing.

5 / 5

Completeness

Explicitly answers both what ("Prove one task's acceptance criteria... record a test plan and a test-gap ledger, and capture screenshots") and when ("Use for the QA stage, after work and before review, when FACTORY.json enables stages.qa") with concrete trigger conditions. The when-clause is more specific than the 4 anchor's "could be more explicit" example, so it fits the 5 anchor.

5 / 5

Trigger Term Quality

Includes good natural keywords — "QA", "acceptance criteria", "test plan", "screenshots", "pull request", "stages.qa" — but offers no synonyms or variations a user might also say (e.g. "testing", "e2e", "verify"). Good coverage with a few natural terms missing fits the 4 anchor; it is above 3 (coverage is well beyond "some relevant keywords") and below 5 (no synonym coverage).

4 / 5

Distinctiveness Conflict Risk

Distinctive artifacts and triggers — "test-gap ledger", "QA stage, after work and before review", "when FACTORY.json enables stages.qa" — carve out a clear pipeline niche with minimal risk of triggering for the wrong skill. Clearly matches the 5 anchor's "clear niche with distinct triggers".

5 / 5

Total

19

/

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

geut/factory-skills

Path

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