CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

translate-skill

将 mattpocock/skills 的内容翻译、刷新或复核到简体中文本地化仓库 vinvcn/mattpocock-skills-zh-CN 时使用这个项目级 skill。适用于 skill files、README content、CLAUDE.md、GLOSSARY.md、docs,以及其他需要保留行为关键 identifiers 的上游用户可见内容。

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.skills/translate-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured, highly actionable instruction skill with two clearly sequenced workflows, an explicit verification checklist with executable commands, and fail-closed error handling. Its weaknesses are redundant restatement of the same preservation invariants across many sections and two concrete mechanisms (fragment protection, review-flag format) left unspecified.

Suggestions

Consolidate the behavior-preservation invariants into one canonical section and reference it from the workflows, 验证步骤, and 复核输出格式 instead of restating the same list six times.

Specify a concrete convention for 保护行为关键片段 (e.g. a placeholder marker like ⟦PATH:...⟧) and for 复核标记 (e.g. a `REVIEW:` prefix) so the single-file workflow is fully executable.

Move the contributor-facing 「术语决定与落地流程」 details into CONTRIBUTING.md (already referenced) and keep only a one-line pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no explanations of concepts Claude already knows, and sections are dense with rules — but the behavior-preservation invariants (frontmatter keys unchanged, code blocks untouched, paths/identifiers preserved) are restated across at least six sections (「操作原则」, 「原样保留哪些内容」, 「Frontmatter 规则」, 「单文件工作流」 step 6, 「验证步骤」 item 4, 「复核输出格式」's 「不变量检查」), which goes beyond minor trimming. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete, executable guidance dominates: exact commands (「node scripts/check-translation.mjs」, 「node scripts/audit-english.mjs」, 「git diff --check」), a literal path-substitution pair (mattpocock/skills → vinvcn/mattpocock-skills-zh-CN), a filled-in frontmatter example, and a dated SYNC.md entry example. It stops short of anchor 5 because two key mechanisms are unspecified: how to 「保护行为关键片段」 before translating (no placeholder/marker convention is given) and what a 复核标记 should look like — matching 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

Two explicitly numbered workflows (「单文件工作流」, 「仓库刷新工作流」) with a dedicated 8-item 「验证步骤」 checklist of concrete commands and expected outcomes, and the refresh workflow's step 6 explicitly chains into that checklist. Error-recovery feedback exists via the fail-closed rule (「拿不准...先原样保留并打上复核标记」) and audit-english.mjs being defined as a review-flag queue rather than a hard gate. This matches anchor 5 (explicit validation steps, feedback loops, checklists); anchor 4 would require missing checkpoints, which are not missing here.

5 / 5

Progressive Disclosure

No bundle files exist, so this scores on the body's structure: 13 clearly headed sections, and every external file it points to (TRANSLATION-GLOSSARY.md as the authoritative glossary, CONTRIBUTING.md for the term/PR process, SYNC.md, the two scripts) is clearly signaled with its purpose. It does not reach anchor 5 because some content that could live in separate files is inlined — notably the ~10-line contributor-process details in 「术语决定与落地流程」 that duplicate CONTRIBUTING.md, and the full 「复核输出格式」 template — matching anchor 4 ('most content appropriately placed; references mostly clear; minor organization gaps') rather than anchor 3, since references are clearly signaled and structure is good.

4 / 5

Total

16

/

20

Passed

Description

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

A strong, well-scoped description that names both repositories, three concrete operations (translate/refresh/review), and the applicable content types, with an explicit 'use when' clause. Its main limitations are missing natural trigger synonyms (sync/汉化/Chinese) and a when-clause anchored to operations rather than user-facing trigger phrases.

Suggestions

Add natural trigger synonyms such as 「同步」/「汉化」 or English terms like 'zh-CN'/'Chinese' so users phrasing a sync request in different ways still match the description.

Make the 'when' clause user-trigger oriented (e.g. 「当用户要求翻译、同步上游或复核中文翻译时使用」) in addition to naming the repos and operations.

DimensionReasoningScore

Specificity

The description names the domain (localizing mattpocock/skills into vinvcn/mattpocock-skills-zh-CN) and lists several concrete actions — 「翻译、刷新或复核」 (translate, refresh, review) — plus enumerated content types (「skill files、README content、CLAUDE.md、GLOSSARY.md、docs」). It falls short of anchor 5 because it does not mention what the operation concretely involves (glossary enforcement, path localization, verification), and short of comprehensive coverage, matching 'several specific actions with minor gaps'.

4 / 5

Completeness

Both 'what' (translate/refresh/review upstream user-visible content into the zh-CN localization repo while preserving behavior-critical identifiers) and 'when' (「将...时使用这个项目级 skill」 — an explicit 'Use when' clause naming both repos) are present. The when-clause is concrete but phrased around the operations/repos rather than natural user trigger phrases (e.g. 'when the user asks to sync upstream changes'), matching anchor 4 ('when' could be more explicit or specific) rather than anchor 5.

4 / 5

Trigger Term Quality

Natural keywords a user would say are present — 「翻译」(translate), 「刷新」(refresh), 「复核」(review), 「简体中文」, 「本地化」, plus both repo names and concrete file names. Common variations like 「同步」(sync), 「汉化」, or 'zh-CN' as a standalone trigger are missing, matching 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description pins a clear niche by naming the exact upstream repo (mattpocock/skills), the exact target repo (vinvcn/mattpocock-skills-zh-CN), and the specific operation set, so it is unlikely to trigger for any other skill. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') — no neighboring anchor fits better since anchor 4 only applies where overlap risk still exists.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

vinvcn/mattpocock-skills-zh-CN

Path

.skills/translate-skill/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.