CtrlK
BlogDocsLog inGet started
Tessl Logo

coding

To implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.

66

1.05x
Quality

55%

Does it follow best practices?

Impact

80%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./instructions/r2/core/skills/coding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured and concise with real one-level references, but lacks executable code/examples and an explicit sequenced validation workflow for risky operations.

Suggestions

Add a minimal concrete code or command example to lift actionability beyond principle-level guidance.

Make the validation methodology an explicit ordered workflow with validation checkpoints (validate -> fix -> retry) for destructive/batch operations.

Tighten redundant directives (e.g., the zero-tolerance sentence restates several prior bullets) to reach peak conciseness.

DimensionReasoningScore

Conciseness

Mostly lean bullet-style guidance that assumes Claude's competence with minimal padding; a few directives repeat or over-specify (e.g., zero-tolerance sentence), keeping it just below 5.

4 / 5

Actionability

Provides concrete principles and checklists but no executable code, commands, or worked examples — it describes what to do rather than giving copy-paste-ready steps for a coding skill.

3 / 5

Workflow Clarity

A validation methodology and checklist imply a sequence, but there is no explicit ordered workflow with validation checkpoints for batch/destructive operations, capping clarity at 3.

3 / 5

Progressive Disclosure

Well-organized XML-style sections with one-level-deep references to real bundle files (assets/iac.md) and listed MCPs/skills; minor gaps in explicit navigation signals.

4 / 5

Total

14

/

20

Passed

Description

50%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 states a clear what but omits any explicit when/trigger guidance, capping completeness at 3. Trigger terms are natural but thin and jargon-heavy.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when implementing features, fixing bugs, or refactoring code').

Expand specific actions beyond the KISS/SOLID/DRY acronyms to describe what the skill concretely does.

Add synonyms/plain-language terms users would naturally say to improve trigger term quality.

DimensionReasoningScore

Specificity

Names the domain (features, bugs, refactors) and KISS/SOLID/DRY plus 'systematic validation', which are concrete-ish actions, but lacks comprehensive coverage of specific actions.

3 / 5

Completeness

Has a clear 'what' (implement features, fix bugs, refactor with validation) but no explicit 'Use when...' trigger clause, so 'when' is missing and completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms like 'features', 'bug fixes', 'refactors' a user would say, but has no file extensions or synonyms and leans on jargon acronyms (KISS/SOLID/DRY).

3 / 5

Distinctiveness Conflict Risk

Somewhat specific to implementation work but very broad — 'features, bugs, refactors' overlaps heavily with general coding assistance and many related skills.

3 / 5

Total

12

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
griddynamics/rosetta
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.