CtrlK
BlogDocsLog inGet started
Tessl Logo

qtpass-localization

QtPass localization workflow - translation files, updating, adding languages

56

Quality

64%

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

72%

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 and audit scripts, and is well organized as a single cohesive document. Its main weaknesses are recurring redundancy across sections and missing validation feedback loops on the destructive merge/PR-merge paths.

Suggestions

Consolidate the repeated 'make distclean before qmake6' guidance into one canonical location and cross-reference it, rather than restating it in 'Updating Translations', the bootstrap workflow, and 'Common Pitfalls'.

Add an explicit validate->fix->retry loop to the destructive merge paths (e.g. verify the merged .ts loads via qmake6/lrelease before finalizing a 'git checkout --theirs' or 'gh pr merge --squash --auto --delete-branch').

Consider extracting the long mnemonic-conventions and Python audit scripts into a references file so the core SKILL.md stays leaner.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no 'what is a .ts file' preamble), but the 'distclean before qmake' point and the Weblate-vs-local guidance recur across multiple sections, so it could be tightened toward level 3.

2 / 3

Actionability

Guidance is fully executable and copy-paste ready: concrete bash commands, the 4-line skeleton heredoc, runnable Python audit scripts, and a worked example, with specific Good/Avoid contrasts for tr() formatting.

3 / 3

Workflow Clarity

Core workflows (bootstrap, reviewer iteration, PR update) have explicit validation checkpoints (grep confirmation, 'run the audit script before pushing'), but destructive/batch merge paths like 'git checkout --theirs' and 'gh pr merge --squash --auto --delete-branch' lack a validate->fix->retry feedback loop, which caps this dimension at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the single self-contained SKILL.md is well organized with clear ##/### headings and no nested file references, so it earns full marks for organization and easy navigation.

3 / 3

Total

10

/

12

Passed

Description

57%

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 a clear niche and lists relevant actions, but it lacks an explicit 'when to use' trigger clause and several natural trigger-term variations. Adding a 'Use when...' clause and terms like 'translations', 'i18n', or 'Qt Linguist' would lift it toward the top of the scale.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or updating QtPass translations, adding a new language, or working with .ts/localization files.'

Include natural user-facing variations such as 'translations', 'i18n', 'Qt Linguist', and '.ts files' alongside 'localization'.

Spell out the concrete actions more specifically (e.g. 'update source references via qmake6, bootstrap a new locale skeleton, build .qm files') rather than the generic 'updating, adding languages'.

DimensionReasoningScore

Specificity

Names the domain and three action areas ('translation files, updating, adding languages'), but the actions are terse and generic rather than the multiple concrete actions (e.g. 'extract text and tables... fill forms... merge documents') of a level-3 anchor.

2 / 3

Completeness

It states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms like 'localization', 'translation files', 'updating', and 'adding languages', but omits common variations a user might say such as 'translations', 'i18n', 'Qt Linguist', or '.ts files'.

2 / 3

Distinctiveness Conflict Risk

The 'QtPass localization' qualifier carves out a clear, project-specific niche with distinct triggers that are unlikely to conflict with other skills.

3 / 3

Total

9

/

12

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.