qtpass-testing

Comprehensive guide for QtPass unit testing with Qt Test

Quality

61%

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

65%

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, project-specific templates and commands, and its workflows are clearly sequenced. Its main weaknesses are duplicated macro/test listings inflating token use and a monolithic single-file structure with no split-out references.

Suggestions

De-duplicate the Qt Test macro guidance — keep a single "Assertions / macros" section and remove the redundant "QtTest Macros" vs "Qt Test Macro Reminder" listings.

Add an explicit validation step to "Adding a New Test Suite", e.g. "Rebuild and run `make check`; confirm the new `<name>` suite appears and passes before committing."

Move the full .pro/plist templates and the testable-source catalog into a referenced file (e.g. references/templates.md) so SKILL.md stays a lean overview with one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient project-specific guidance, but the Qt Test macro list is duplicated ("QtTest Macros" and "Qt Test Macro Reminder") and the "Testable Source Files" catalog repeats much of the "Existing Test Suites" method listings, so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready material: complete compilable test-file template, .pro and plist templates, exact build/run/lint commands, and concrete assertion examples specific to the project.	3 / 3
Workflow Clarity	"Adding a New Test Suite" is a clear 7-step sequence and the settings-pollution section offers a backup/restore loop, but the main workflow lacks an explicit validation checkpoint (e.g. confirming the new suite is picked up by `make check`) before proceeding.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic (519 lines, no bundle files), keeping reference catalogs and full templates inline that could be split into one-level-deep files; the under-50-line lenient rule does not apply here.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 is distinctive and clearly scoped to QtPass testing, but it lacks explicit trigger guidance and concrete enumerated actions, leaning on the vague "Comprehensive guide" framing. Adding a "Use when…" clause and listing specific testing tasks would raise it.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or running unit tests for QtPass, adding a new test suite, or debugging a failing Qt Test."

Replace the "Comprehensive guide for" framing with concrete actions, e.g. "Write, build, and run QtPass unit tests with Qt Test; add new test suites and debug failures."

Include natural keyword variations like "unit tests", "test suite", and "Qt Test framework" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and activity ("QtPass unit testing with Qt Test") but does not enumerate multiple concrete actions; the "Comprehensive guide for" framing is buzzword-style rather than a specific verb list.	2 / 3
Completeness	It states what the skill is (a guide for QtPass unit testing) but provides no "Use when…" clause or explicit trigger guidance, so the "when" is only implied — capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	"QtPass unit testing" and "Qt Test" are natural terms a user might say, but common variations ("tests", "test suite", "Qt Test framework", "unit tests") are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Naming both the specific project (QtPass) and the framework (Qt Test) carves out a clear niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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: 04899e4

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