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.

Install with Tessl CLI

npx tessl i github:ArabelaTso/Skills-4-SE --skill code-translation

What are skills?

Review — 86%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms including language names and common user phrases, explicit 'Use when' guidance with five distinct scenarios, and a clear niche that distinguishes it from general coding assistance. The third-person voice is used correctly throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Translating functions, classes, or modules', 'Migrating entire projects', 'idiomatic translation', 'Converting between different paradigms', 'Porting legacy code'. Also specifies concrete languages (Python, JavaScript/TypeScript, Java, Go, Rust, C/C++).	3 / 3
Completeness	Clearly answers both what ('Convert code between programming languages while preserving functionality and semantics') and when with explicit numbered triggers covering five distinct use cases. The 'Use when:' clause is explicit and comprehensive.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'convert code', 'translating', 'migrating', specific language names, 'porting', 'legacy code', 'OOP to functional'. These match how users naturally describe code translation tasks.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on cross-language code conversion. The specific mention of 'between programming languages', paradigm conversion, and migration strategies distinguishes it from general coding skills or single-language refactoring tools.	3 / 3
	Total	12 / 12 Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent code examples covering multiple language pairs and translation patterns. The progressive disclosure is well-executed with clear references to detailed guides. However, the content could be more concise by trimming explanatory text, and the workflow would benefit from explicit validation commands and error recovery steps.

Suggestions

Add concrete validation commands in the workflow (e.g., specific test runner commands, diff tools for comparing outputs)

Trim explanatory prose in sections like 'Analyze Source Code' - Claude already knows how to analyze code

Add a feedback loop to the workflow: 'If tests fail → identify divergent behavior → adjust translation → re-test'

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some unnecessary verbosity, such as explaining basic concepts like 'Understand what the code does' and listing obvious pros/cons. The extensive examples are valuable but could be more condensed.	2 / 3
Actionability	Excellent actionability with fully executable code examples across multiple language pairs. Every translation pattern includes complete, copy-paste ready code with clear before/after comparisons.	3 / 3
Workflow Clarity	The 4-step workflow is clear but lacks explicit validation checkpoints. The 'Verify Correctness' step is mentioned but doesn't include concrete validation commands or feedback loops for when tests fail.	2 / 3
Progressive Disclosure	Well-structured with clear navigation to external references (idiomatic_guide.md, language_patterns.md, project_migration.md). The decision tree helps users find the right path, and content is appropriately split between overview and detailed guides.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 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	10 / 11 Passed

Reviewed: about 12 hours 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.