CtrlK
BlogDocsLog inGet started
Tessl Logo

qtpass-localization

QtPass localization workflow - translation files, updating, adding languages

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/qtpass-localization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is highly actionable and well-sequenced with validation checkpoints, but it is a monolithic single-file skill that would benefit from splitting the audit scripts and convention tables into reference files.

Suggestions

Extract the mnemonic-convention table and the Python audit scripts into a references/ file (e.g. CONVENTIONS.md, audit.py) and link to them, leaving SKILL.md as a lean overview.

Trim introductory asides that restate what Qt Linguist / .ts files are, since Claude already knows these.

Consider a short 'Quick start' summary at the top so the most common action (update translations after code changes) is discoverable before the detailed sections.

DimensionReasoningScore

Conciseness

Dense with executable commands and largely free of padding; minor over-explanation remains in asides like 'Qt uses Qt Linguist (.ts files) for translations' and some prose around conventions.

4 / 5

Actionability

Fully executable, copy-paste-ready bash commands, Python audit scripts, exact .ts skeleton, and git/gh PR commands cover the common cases concretely.

5 / 5

Workflow Clarity

Multi-step processes (bootstrap a language, update sources, fix reviewer findings) are clearly sequenced with explicit validation checkpoints such as 'Run the audit script before pushing' and 'Confirm via qmake6 2>&1 | grep'.

5 / 5

Progressive Disclosure

Well-sectioned with headers, but ~355 lines of content with no bundle files means substantial material (mnemonic conventions, audit scripts, reviewer-iteration workflow) that could live in separate reference files is inlined rather than split.

3 / 5

Total

17

/

20

Passed

Description

65%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 specific and clearly distinct, but lacks an explicit 'Use when' trigger clause, which caps its completeness. Adding a trigger phrase and a file-extension keyword would push it higher.

Suggestions

Append an explicit trigger clause, e.g. 'Use when updating translations, adding a new language, or fixing Qt Linguist .ts files in QtPass.'

Add the .ts file extension and the term 'i18n'/'translations' to broaden trigger-term coverage.

Mention building .qm files and translation testing in the description to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

Names the domain (QtPass localization) and three concrete actions ('translation files', 'updating', 'adding languages'), but coverage is not comprehensive — no mention of building .qm files, testing, or reviewer-iteration workflows present in the body.

3 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; per the rubric guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural keywords users would say ('QtPass', 'localization', 'translation files', 'adding languages') but omits common synonyms like 'translations', 'i18n', and the .ts file extension.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific named project (QtPass) and a narrow task (localization), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
IJHack/QtPass
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.