CtrlK
BlogDocsLog inGet started
Tessl Logo

fill-i18n-phase2

运行 Phase 2 工作流。执行脚本扫描缺失的多语言词条,并按注册表补全启用语言(如 en-US、zh-TW、vi-VN、ja-JP、fr-FR),最后修复相关测试。

60

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/fill-i18n-phase2/SKILL.md
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.

The content is an efficient, fully executable workflow with concrete commands, file paths, formatting rules, an explicit validation checkpoint, and a retry loop. It assumes Claude's competence and stays lean while remaining actionable.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it gives concrete commands and file paths without explaining what i18n or PO files are — with only minor wording that could be trimmed (e.g. the parenthetical clarifications).

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands (generate_missing_report.py, build_mo.py, the exact pytest invocation) plus precise file paths and concrete formatting rules (JSON commas, PO msgstr with blank lines), covering the common cases.

5 / 5

Workflow Clarity

A clearly numbered sequence with explicit validation (pytest终检), a feedback loop ('如果有缺失,重复步骤 3 直到全部通过'), and a cleanup checkpoint (删除报告), which matches the anchor for clear sequencing with error-recovery feedback loops.

5 / 5

Progressive Disclosure

This is a short, single-purpose skill with no external bundle files; the content is well-organized into a short numbered workflow with clear sections, so under the simple-skill exception progressive disclosure scores 5.

5 / 5

Total

19

/

20

Passed

Description

45%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 conveys a concrete, narrow capability but omits any explicit 'when to use' trigger phrasing and leans on project-internal jargon ('Phase 2', '注册表') rather than natural user language. It is specific and distinctive but incomplete as a trigger.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill, e.g. 'Use when asked to fill in missing translations or onboard a new locale for the i18n registry.'

Include natural trigger phrases users would actually say, such as 'missing translations', '补全 i18n', or 'add a new language', alongside the technical terms.

Spell out one or two more concrete actions (e.g. 'compile .po files' and 'run locale pytest tests') so the capability list reads as comprehensive rather than partial.

DimensionReasoningScore

Specificity

Names the domain (i18n Phase 2 workflow) and two concrete actions — running a script to scan for missing translations and fixing related tests — but coverage is partial and the registry-completion action is stated generically rather than as multiple specific actions.

3 / 5

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is only weakly implied by 'Phase 2 工作流'; the rubric caps completeness at 3 when trigger guidance is missing, and here the 'when' is effectively absent.

2 / 5

Trigger Term Quality

Contains relevant domain keywords like '多语言词条', '注册表', '补全', and named languages (en-US, zh-TW, vi-VN, ja-JP, fr-FR), but lacks the natural request phrasings a user would say (e.g. '翻译缺失', '补全 i18n', 'missing translations') and offers few synonyms.

3 / 5

Distinctiveness Conflict Risk

The narrow niche of i18n Phase 2 translation completion with a specific registry and named languages is clearly distinct from generic skills and unlikely to trigger for unrelated work, with only minor overlap risk with a hypothetical general i18n skill.

4 / 5

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
4thfever/cultivation-world-simulator
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.