qtpass-testing

Comprehensive guide for QtPass unit testing with Qt Test

Quality

62%

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 ./.opencode/skills/qtpass-testing/SKILL.md

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.

The content is highly actionable with complete, executable templates and clear workflows for adding and debugging test suites. Its weaknesses are length/redundancy and a monolithic structure with no reference files, despite referencing repo paths and an external skill.

Suggestions

Move the long catalog of existing test suites and/or the template blocks into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Remove the redundant 'Qt Test Macro Reminder' section and consolidate the duplicated assertion guidance into a single section.

Add an explicit fix-and-rerun feedback loop in the test-running workflow (e.g., on failure, run `./tests/auto/util/tst_util -v2`, fix, then `make check` again).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and lists, but it is long (~510 lines) with redundant sections (QtTest Macros vs. Qt Test Macro Reminder, repeated assertion guidance) and an exhaustive inline catalog of existing suites that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready templates (test file, .pro, plist), concrete build/run/debug commands, and a numbered procedure for adding a new suite — fully executable guidance covering common cases.	5 / 5
Workflow Clarity	'Adding a New Test Suite' is a clear 7-step sequence ending in `make check` as a validation checkpoint, with a separate debugging section; minor feedback-loop gaps (no explicit fix-and-rerun inline) keep it below 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the single ~510-line file inlines material that could be split out (suite catalog, templates); section headers give structure but bulk content stays inline.	3 / 5
	Total	15 / 20 Passed

Description

53%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 clearly identifies the domain and framework but is terse and lacks an explicit 'Use when...' trigger clause, which caps completeness. It is distinctive because of the project-specific scope. Trigger-term coverage is decent but misses common synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when writing or running QtPass unit tests, adding a Qt Test suite, or debugging failing tst_ tests.'

Replace the generic word 'guide' with concrete actions such as 'write, run, and debug QtPass unit tests using the Qt Test framework'.

Include common trigger synonyms like 'tests', 'QtTest', and 'test suites' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('QtPass unit testing') and a concrete action ('testing with Qt Test'), but 'guide' is generic and the coverage of what is performed is not comprehensive.	3 / 5
Completeness	Provides a clear 'what' (guide for QtPass unit testing) but no 'Use when...' trigger clause, capping completeness at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Includes relevant keywords ('unit testing', 'QtPass', 'Qt Test') but misses common variations users might say such as 'tests', 'QtTest', or 'test suite'.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific project (QtPass) and framework (Qt Test), giving it a clear niche with only minor overlap risk against generic Qt-testing skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (519 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: IJHack/QtPass
Path: .opencode/skills/qtpass-testing/SKILL.md
Commit: 9972a3c

Reviewed: 6 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.