qtpass-linting

QtPass CI/CD workflow - run GitHub Actions locally with act, linters, formatters

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/qtpass-linting/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, packed with executable commands and valuable project-specific gotchas Claude would not otherwise know. Its main weaknesses are repetition that hurts conciseness and contradictory act-vs-prettier guidance that muddies the canonical workflow, plus a monolithic structure that could benefit from splitting into reference files.

Suggestions

Consolidate the repeated act/prettier-before-PR guidance into a single canonical section to remove redundancy across 'The Act Pattern', 'Prettier Patterns', 'Run Before PR Checklist', and 'Note on act'.

Resolve the conflicting act guidance: pick one canonical pre-push path and demote the 'act may fail, skip it' caveat to a clearly marked troubleshooting note rather than an equal-weight alternative.

Split large reference blocks (Doxygen details, per-linter specifics) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and focused on project-specific gotchas Claude would not know, but it repeats the same guidance across 'The Act Pattern', 'Prettier Patterns', 'Run Before PR Checklist', and 'Note on act', which is unnecessary padding that could be tightened.	2 / 3
Actionability	Provides extensive copy-paste-ready commands (docker run --entrypoint zizmor, act push -W ..., npx prettier --write, doxygen Doxyfile, coverxygen) and tables mapping linters to config files and workflows to filenames.	3 / 3
Workflow Clarity	The PR checklist and Doxygen sections have explicit sequenced steps and validation checkpoints, but competing contradictory guidance ('always run act' vs 'act may fail on new branches, skip it, prettier is sufficient') makes the canonical path ambiguous.	2 / 3
Progressive Disclosure	Well-sectioned with headers and tables, but at ~350 lines it is a monolithic single file with no bundle references, and content like per-linter and Doxygen details could be split into separate reference files.	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 is concise and names a concrete niche (QtPass CI/CD via act, linters, formatters), but it lacks an explicit 'Use when...' trigger clause and broader natural-language trigger terms. It is solid but generic enough to risk overlap with sibling linting skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when modifying QtPass code before pushing a PR, running CI locally with act, or fixing linter/formatter failures'.

Broaden trigger terms to include natural phrasings users would say ('run CI locally', 'lint before push', 'format C++ code', 'Doxygen warnings').

Tighten the 'linters, formatters' tail into specific, distinctive actions to reduce overlap with generic linting skills.

Dimension	Reasoning	Score
Specificity	Names the domain (QtPass CI/CD) and several concrete actions ('run GitHub Actions locally with act', 'linters, formatters'), but as a flat list rather than a comprehensive enumeration of specific actions.	2 / 3
Completeness	Clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant keywords ('CI/CD', 'GitHub Actions', 'act', 'linters', 'formatters') but misses common natural variations a user would say, such as 'run CI locally', 'before pushing a PR', or 'format my code'.	2 / 3
Distinctiveness Conflict Risk	The explicit 'QtPass' and 'act' anchoring gives it a clear niche, but the generic 'linters, formatters' tail and absent explicit triggers mean it could still overlap with other linting skills.	2 / 3
	Total	8 / 12 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-linting/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.