CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qtpass-linting

Reproduces QtPass CI lint failures locally and fixes them with clang-format, Prettier, textlint, shfmt, zizmor, Doxygen or the pinned super-linter image. Use when lint failed, super-linter or CI is red, clang-format or Prettier complains, markdownlint or textlint flags a file, Doxygen warns, or before pushing a PR to check formatting.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A high-quality, deeply repo-specific skill body: every command is executable, the fix-loop workflow has explicit validation and feedback loops, and detail is correctly pushed into three real, one-level-deep reference files. The only deduction is minor: version pins and a few explanatory sentences sit inline and will age or could be trimmed.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely repo-specific, non-obvious facts (CI config locations, act quirks, config-trap notes) with no explanation of concepts Claude already knows. Minor penalty for time-sensitive version pins embedded in prose ("v9.0.0", "clang-format 22", "Doxygen 1.18.0") and a few sentences that could be tightened.

4 / 5

Actionability

Everything is copy-paste ready: a failure-name-to-command table, complete docker run invocations, per-tool apply/check command pairs, and an executable pre-PR checklist. Specific commands cover all the common failure cases.

5 / 5

Workflow Clarity

The fix loop is an explicitly sequenced workflow with validation checkpoints and feedback loops ("Re-run the same check. Not clean yet: back to step 2", "Repeat until every check is clean", "Any step not clean: go back to the fix loop"), plus a widening step so one fix cannot silently break another linter.

5 / 5

Progressive Disclosure

The body is a clear overview with core commands inline and three well-signaled, condition-scoped references ("read references/super-linter.md when changing lint.yml", etc.); all three files exist and link only one level deep. Content is appropriately split with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

96%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.

An exemplary description: concrete third-person actions, named tools, and an explicit, naturally worded "Use when" trigger clause covering both reactive (CI red, linter complains) and proactive (before pushing a PR) cases. The only weak point is slight trigger overlap with sibling QtPass skills around Doxygen and general CI status.

DimensionReasoningScore

Specificity

"Reproduces QtPass CI lint failures locally and fixes them with clang-format, Prettier, textlint, shfmt, zizmor, Doxygen or the pinned super-linter image" names multiple concrete actions with the exact tools used. Coverage is comprehensive across the repo's linters, matching the top anchor.

5 / 5

Completeness

It explicitly answers both questions: the "what" (reproduces CI lint failures locally and fixes them with the named tools) and the "when" (a full "Use when..." clause with concrete trigger phrases). This mirrors the rubric's 5-anchor example structure.

5 / 5

Trigger Term Quality

"Use when lint failed, super-linter or CI is red, clang-format or Prettier complains, markdownlint or textlint flags a file, Doxygen warns, or before pushing a PR" uses natural user phrasings with synonym variation (failed / red / complains / flags / warns). Trigger coverage is comprehensive for this domain.

5 / 5

Distinctiveness Conflict Risk

The QtPass linting niche with named linters is mostly distinct, but "Doxygen warns" and CI-status triggers overlap slightly with closely related sibling skills (qtpass-docs, qtpass-github). Not fully 5 because of that minor overlap within its own skill family.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

IJHack/QtPass

Path

.opencode/skills/qtpass-linting/SKILL.md

Reviewed

Table of Contents

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.