CtrlK
BlogDocsLog inGet started
Tessl Logo

android-check-pr-translations

Audit changed Android translations in a GitHub PR.

59

Quality

68%

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 ./.agents/skills/android-check-pr-translations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 with a real, well-documented extraction script and a clear sequenced workflow including a completion checkpoint. Its main weakness is mild redundancy between the workflow and the dedicated script section.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with only minor redundancy: the extraction command and output schema are described in both the workflow step and the dedicated Extraction Script section, which could be consolidated.

4 / 5

Actionability

It provides a copy-paste-ready command referencing a real script (scripts/extract_pr_strings.py, verified present), a complete JSON output schema with worked examples, and concrete follow-up actions (delegate to /translation-review, validate Wikipedia links).

5 / 5

Workflow Clarity

A clear 3-step numbered sequence with an explicit completion checklist in step 1 serving as a validation checkpoint; the minor gap is no feedback loop describing what to do with review findings beyond reporting them.

4 / 5

Progressive Disclosure

Content is well-organized into headed sections (Workflow, Extraction Script) with a one-level-deep, clearly signaled reference to scripts/extract_pr_strings.py that exists in the bundle; the inlined output-schema field docs are reasonable but slightly long for an overview.

4 / 5

Total

17

/

20

Passed

Description

53%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 well-targeted to a clear niche but lacks an explicit "Use when..." trigger clause and natural synonyms like localization or i18n. Adding trigger phrasing and common synonyms would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when reviewing translation changes in an Android GitHub PR' clause to answer the 'when' half of completeness.

Include natural synonyms users might say, e.g. 'localization', 'i18n', 'locale', or 'string resources', to improve trigger-term coverage.

Optionally name a second concrete action (e.g. 'validate localized Wikipedia links') to lift specificity toward a higher anchor.

DimensionReasoningScore

Specificity

"Audit changed Android translations in a GitHub PR" names the domain (Android translations, GitHub PR) and one concrete action (audit), matching the anchor that lists domain plus 1-2 actions without being comprehensive.

3 / 5

Completeness

The description gives a clear "what" (audit changed translations) but no explicit "Use when..." trigger clause; per the rubric guidelines a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

It includes natural terms like "Android translations" and "PR", but misses common synonyms a user might say such as "localization", "i18n", "locale", or "string resources", fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Audit changed Android translations in a GitHub PR" carves a clear niche with distinct triggers, but has minor overlap risk with a general translation-review skill (which this skill itself delegates to), fitting the mostly-distinct anchor.

4 / 5

Total

13

/

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
kylecorry31/Trail-Sense
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.