manage-translations

指导如何在 Project Graph 项目中管理多语言翻译。当需要添加新翻译、更新现有翻译或了解翻译系统结构时使用此技能。

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.trae/skills/manage-translations/SKILL.md

Quality

Content

58%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 concise and well-structured for a simple lookup-oriented skill, but it under-delivers on the skill's stated purpose of managing translations: it shows how to view supported languages yet provides no concrete steps or validation for adding or updating translations.

Suggestions

Add a concrete, executable workflow for the core add/update tasks, e.g. editing a specific locale .yml file with a key/value example and how new languages are registered.

Include a validation checkpoint after edits, such as checking for missing keys across locales or running the project's translation linter, since batch translation changes benefit from verification.

Remove the redundant opening restatement of the description to tighten token efficiency, or replace it with a one-line prerequisite (e.g., the locale directory path).

Dimension	Reasoning	Score
Conciseness	The body is lean—a locale directory tree and one ls command—with no over-explanation of YAML or translation concepts, matching the 'efficient; minor instances of over-explanation' anchor; not 5 because the opening line restates the description and the annotated tree adds slight padding.	4 / 5
Actionability	Provides one concrete executable command (`ls app/src/locales/*.yml`) and a concrete file-location tree, but gives no executable guidance for the skill's core add/update translation tasks, fitting the 'some concrete guidance but incomplete; missing key details' anchor.	3 / 5
Workflow Clarity	Only a rough implied sequence (view languages first, then modify) is present, with the actual add/modify translation steps entirely absent, matching the 'rough sequence present but many gaps; steps poorly defined' anchor; not 3 because key steps beyond the lookup are missing.	2 / 5
Progressive Disclosure	A short (<50 line) simple single-purpose skill with no bundle files and clear section headers; per the simple-skills note, well-organized sections warrant the top score even without external references.	5 / 5
	Total	14 / 20 Passed

Description

67%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 well-scoped with explicit what-and-when guidance and concrete actions, scoring solidly above average. Its main weakness is trigger-term breadth—missing synonyms and file extensions that would push it toward the top anchor.

Suggestions

Add natural synonyms and file extensions to the trigger clause, e.g. '本地化 (localization)、i18n、.yml 翻译文件', to broaden keyword coverage.

Mention destructive or validation-relevant actions (e.g., removing a language, verifying completeness after edits) to make the action list more comprehensive.

Tighten the trigger phrase to explicitly name the most common user requests such as '翻译缺失' or '新增语言支持'.

Dimension	Reasoning	Score
Specificity	Names the domain (multilingual translation) and lists three concrete actions—adding new translations, updating existing ones, and understanding the translation system structure—matching the 'several specific actions; minor gaps' anchor; not 5 because coverage isn't comprehensive (e.g., removing languages, validation).	4 / 5
Completeness	Clearly states both the 'what' (manage multilingual translations in Project Graph) and an explicit 'when' clause ('当需要添加新翻译、更新现有翻译或了解翻译系统结构时使用此技能'), matching the 'has both what and when; when could be more specific' anchor; not 5 because the trigger variety is narrower than the comprehensive anchor.	4 / 5
Trigger Term Quality	Includes natural trigger phrases a user might say ('当需要添加新翻译', '更新现有翻译'), but misses common synonyms and file extensions like .yml, '本地化', or 'i18n', fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Scoped to a specific project ('Project Graph') with a clear niche (multilingual translation) and concrete triggers, giving mostly distinct triggers with minimal overlap risk; not 5 because the phrasing is somewhat general within that niche.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: graphif/project-graph
Path: .trae/skills/manage-translations/SKILL.md
Commit: f187e86

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.