qtpass-releasing

Release workflow for QtPass - versioning, builds, publishing

Quality

71%

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-releasing/SKILL.md

Quality

Content

82%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 executable commands throughout and a clear sequenced release checklist. It is concise with only minor over-explanation, and well-structured, though it references script files that are not present in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean checklists and executable commands with little concept padding; minor instances of over-explanation (the semver MAJOR/MINOR/PATCH recap and generic shell 'Script Best Practices') could be trimmed, keeping it just below the 'every token earns its place' anchor.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands for every phase (grep, make check, git archive, git tag, gh release create, gh pr create) plus exact file/field targets for version bumps, with placeholders explicitly flagged — covering the common cases concretely.	5 / 5
Workflow Clarity	A clear numbered 7-step release sequence is present with a test checkpoint ('make check') before building, but there are minor validation gaps (no explicit artifact-verification step before tagging/releasing).	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections in a single self-contained file appropriate for a release checklist; references to ./scripts/release-linux.sh and release-mac.sh are clearly signaled, though no bundle directory exists to back those referenced paths.	4 / 5
	Total	17 / 20 Passed

Description

61%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 is clear and project-specific with a reasonable set of release-related trigger terms, but it lacks an explicit 'Use when...' trigger clause, capping its completeness. Specificity is adequate but the listed actions are somewhat generic.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when preparing, cutting, or publishing a QtPass release.'

Make the actions more concrete, e.g. 'bump versions across build files, build Linux/macOS/Windows artifacts, tag and publish GitHub releases' instead of the generic 'versioning, builds, publishing'.

Include a couple of natural synonyms users might say ('cut a release', 'ship a new QtPass version') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Release workflow for QtPass') and a few concrete actions ('versioning, builds, publishing'), but the actions are high-level and generic rather than comprehensively specific, fitting the 'names domain and concrete actions but not comprehensive' anchor.	3 / 5
Completeness	The description clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('release', 'versioning', 'builds', 'publishing') with good coverage; a few synonyms or variations are missing but the keyword set is solidly above the midpoint.	4 / 5
Distinctiveness Conflict Risk	Tying the workflow to the specific QtPass project gives it a clear niche with low conflict risk, though the generic release terms could overlap with other release-oriented skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

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