CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa

General-purpose QA verdict for any artifact type

Quality

60%

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/qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a highly actionable, well-structured operational protocol: concrete tool invocations, a complete fallback chain, and explicit failure and delegation handling. Its main weaknesses are token efficiency (repeated threshold logic and one bloated run-on step) rather than correctness or clarity of the workflow itself.

Suggestions

State the score-to-loop-action mapping once (the verdict table) and reference it from the plugin-delegation and fallback sections instead of re-deriving it two more times.

Break the ~150-word step 3.5 run-on sentence into a short list of the four probes (process, browser, computer-use, artifact) with one line each, or move the probe detail into a references/ file.

Renumber step '3.5' into the main 1-5 sequence (or fold it into step 3) so the workflow reads as a clean, monotonic sequence.

DimensionReasoningScore

Conciseness

The body is dense and operational, explaining only Ouroboros-specific protocol Claude would not know, but it is not lean: the score-to-loop-action mapping is repeated three times (the verdict table, the plugin-delegation paragraph, and the fallback section), and step 3.5 is a ~150-word single sentence of parentheticals that could be tightened. It matches anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete guidance throughout: the exact tool name 'ouroboros_qa' with an argument-by-argument call template, a copy-paste-ready uvx fallback command, the exact footer format, and explicit handling of 'delegated_to_subagent' responses. Minor gaps keep it at 4 rather than 5: argument values are placeholders like '<the content to evaluate>', and named runtime capabilities ('inspect_code', 'orchestrate_subagents', 'run_shell') are invoked without concrete syntax.

4 / 5

Workflow Clarity

A clearly sequenced 1-5 workflow with explicit verdict-driven next actions, an iterative contract (qa_session_id + iteration_history, continue until pass/fail), a feedback loop (REVISE: address suggestions, run again), and failure handling for unparseable verdicts and missing MCP. Minor gaps: the awkward '3.5' step numbering and the crammed single-paragraph probe fan-out slightly blur the sequence; this is a read-only verdict skill, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

A single-file skill (~66 lines) with well-organized sections (Instructions, QA steps, Iterative QA, Fallback, Footer), and the one external reference (qa-judge.md) is one level deep with three clearly ordered fallback paths. Scored against the actual bundle structure: no references/, scripts/, or assets/ directories exist. Not 5 because the skill exceeds 50 lines and the step 3.5 probe-fan-out detail would fit well in a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

33%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 communicates a general quality-verdict capability but is too generic: no concrete actions, no trigger guidance, and broad scope that conflicts with many review-style skills. It sits well below the good examples, which pair concrete actions with explicit 'Use when' phrases.

Suggestions

Add concrete actions to the description, e.g., 'Scores artifacts on Correctness, Completeness, Quality, Intent Alignment, and Domain-Specific dimensions; returns PASS/REVISE/FAIL with actionable suggestions.'

Append an explicit trigger clause such as 'Use when the user asks to check, review, or grade the quality of an artifact (code, documents, test output, API responses).' This also lifts completeness above 3.

Narrow the claimed scope (e.g., 'Ouroboros loop QA' rather than 'general-purpose ... any artifact type') to reduce conflict with generic code-review and document-review skills.

DimensionReasoningScore

Specificity

The description 'General-purpose QA verdict for any artifact type' names the domain but gives only one generic action ('QA verdict') with no concrete capabilities (e.g., scoring dimensions, PASS/REVISE/FAIL outcomes, actionable suggestions), matching the anchor 'Names the domain but actions are minimal or generic'. It falls short of 3 because it does not list even 1-2 concrete actions.

2 / 5

Completeness

The 'what' is present ('QA verdict for any artifact type') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Only the generic keywords 'QA', 'verdict', and 'artifact type' appear; natural phrases a user would actually say ('check the quality of this', 'review this output', 'does this pass') and common variations are missing. It matches anchor 2 ('One or two generic keywords; missing the natural phrases users say') rather than 3, which would require a broader set of relevant keywords.

2 / 5

Distinctiveness Conflict Risk

'General-purpose' and 'any artifact type' make the scope extremely broad, creating high overlap risk with code-review, document-review, and general verification skills. It matches anchor 2 ('Very broad; high overlap risk with many similar skills'); the word 'verdict' adds slight distinctiveness, keeping it above 1.

2 / 5

Total

9

/

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

Q00/ouroboros

Path

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