qtpass-docs

Documentation guide for QtPass - README, FAQ, localization

Quality

57%

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-docs/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 concrete commands and templates, and it is reasonably well sectioned. Its main weaknesses are duplicated commands, unsegregated version-specific details, a few vague validation steps, and inline Doxygen detail that could be split into a reference file.

Suggestions

De-duplicate the prettier and doxygen command blocks and move the detailed Doxyfile settings table plus "common doc mistakes" list into a references/ file linked from the body.

Segregate time-sensitive version details (Doxygen 1.17.0, dated CHANGELOG example) into a clearly labeled section or note so they do not penalize the evergreen body.

Tighten vague validation steps: replace "Test the changes render correctly" with a concrete check and add a verification step to the version-update workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tables and commands, but it repeats prettier and doxygen commands across sections and embeds unsegregated time-sensitive details ("Doxygen 1.17.0", "1.5.1 - 2026-03-30", "grep 1\.5"), so it could be tightened rather than fully token-efficient.	2 / 3
Actionability	It provides copy-paste-ready commands (prettier, doxygen, grep), a FAQ template, a Doxyfile settings table, and a Doxygen comment example, giving concrete executable guidance throughout.	3 / 3
Workflow Clarity	Workflows like "Adding New FAQ Entry" are sequenced and the Doxygen section has an explicit validation checkpoint ("Any output = warning = CI will fail"), but other flows have gaps such as the vague "Test the changes render correctly" step and no verification for version updates.	2 / 3
Progressive Disclosure	Sections are well organized and the localization reference is a clearly signaled one-level link, but no bundle files exist and roughly 80 lines of inline Doxyfile/Doxygen detail that could live in a separate reference keep it from a clean overview-plus-references structure.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 identifies the QtPass documentation domain and a few areas but is missing concrete action verbs and any explicit "Use when..." trigger guidance. It is adequate but generic, which caps several dimensions at 2.

Suggestions

Add concrete action verbs, e.g. "Edit, format, and generate QtPass documentation across README, FAQ, and API docs".

Append an explicit trigger clause such as "Use when updating QtPass README/FAQ, localizing strings, or fixing Doxygen/CI doc warnings".

Include more natural trigger variations users would say (e.g. "QtPass docs", "CHANGELOG", "Doxygen warnings", "prettier formatting").

Dimension	Reasoning	Score
Specificity	"Documentation guide for QtPass - README, FAQ, localization" names the domain and several areas, but lists topic/file names rather than concrete actions like "edit", "generate", or "lint", so it does not reach the multiple-specific-actions level.	2 / 3
Completeness	The description answers what (a documentation guide for QtPass covering README/FAQ/localization) but provides no "Use when..." trigger; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"QtPass", "README", "FAQ", and "localization" are relevant terms a user might say, but coverage is thin with no common variations, so it is only partial rather than good coverage.	2 / 3
Distinctiveness Conflict Risk	Tying it to QtPass gives a niche, but "documentation guide" is generic enough that it could overlap with other documentation skills, so it is not clearly distinct with unambiguous triggers.	2 / 3
	Total	8 / 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
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: IJHack/QtPass
Path: .opencode/skills/qtpass-docs/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.