code-translation

Convert code between programming languages while preserving functionality and semantics. Use when: (1) Translating functions, classes, or modules between languages (Python, JavaScript/TypeScript, Java, Go, Rust, C/C++), (2) Migrating entire projects to a different language, (3) Need idiomatic translation that follows target language conventions, (4) Converting between different paradigms (OOP to functional, etc.), (5) Porting legacy code to modern languages. Provides language-specific patterns, idiomatic translation guides, and project migration strategies.

1.08x

Quality

78%

Does it follow best practices?

Impact

99%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/code-translation/SKILL.md

Quality

Content

67%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 actionable and well-structured with good reference navigation, but is somewhat verbose due to trivial baseline-language examples and an inlined patterns section that duplicates reference material. Tightening these would materially improve token efficiency.

Suggestions

Trim or remove the 'Common Translation Patterns' section's trivial baseline examples (e.g. `numbers = [1, 2, 3]`) that Claude already knows; keep only the cross-language mapping insight, or move the section into language_patterns.md.

Make the 'Verify Correctness' workflow step more concrete with specific commands or test-porting steps rather than 'Port existing tests / Add behavioral tests / Compare outputs'.

Deduplicate the 'Common Translation Patterns' examples against language_patterns.md so the SKILL.md overview points to rather than repeats the detailed patterns.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but inlines several trivial examples Claude already knows (basic list/dict/map construction in Python/JS/Go) that pad the token budget without adding translation insight.	3 / 5
Actionability	Numerous executable, copy-paste-ready code examples across multiple language pairs cover the common translation cases, with only minor gaps in some edge-case mappings.	4 / 5
Workflow Clarity	A clear four-step Translation Workflow plus a decision tree and before/during/after checklists sequence the work, with a 'Verify Correctness' checkpoint; the verification step is high-level rather than command-level, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Three real, well-signaled one-level-deep references (idiomatic_guide.md, language_patterns.md, project_migration.md) organize detail well, but the inlined 'Common Translation Patterns' section overlaps content that could live in language_patterns.md, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

88%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 strong, specific, and follows best-practice structure with a clear 'Use when' trigger list and third-person voice. It could be marginally improved by adding a couple of natural synonyms like 'rewrite'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Translating functions, classes, or modules', 'Migrating entire projects', 'idiomatic translation', 'Converting between different paradigms', 'Porting legacy code' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' ('Convert code between programming languages while preserving functionality and semantics') and 'when' via a concrete 'Use when:' clause enumerating five trigger scenarios.	5 / 5
Trigger Term Quality	Strong natural terms ('Convert code', 'Translating', 'Migrating', 'Porting legacy code') plus an explicit language list, but a few common synonyms users might say (e.g. 'rewrite', 'replatform') are absent.	4 / 5
Distinctiveness Conflict Risk	The cross-language translation niche is clearly distinct from single-language refactoring skills, with trigger language unlikely to fire for the wrong skill; minor overlap risk remains with general code-modification skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (539 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/code-translation/SKILL.md
Commit: 4f38503

Reviewed: 8 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.