CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-classes

Generate bytecode classes from DSL scripts (MAL, OAL, LAL, Hierarchy). Runs the compiler and dumps .class files for inspection.

84

2.32x
Quality

77%

Does it follow best practices?

Impact

100%

2.32x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/generate-classes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

67%

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 technically specific and clearly identifies a narrow domain with concrete actions and named DSL languages, making it highly distinctive. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are domain-appropriate but could benefit from more natural language variations.

Suggestions

Add a 'Use when...' clause such as 'Use when the user wants to compile MAL, OAL, LAL, or Hierarchy DSL scripts into bytecode, inspect generated .class files, or debug compiler output.'

Include natural trigger variations like 'compile DSL', 'generate classes', 'bytecode generation', or 'inspect compiled output' to improve matching.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Generate bytecode classes', 'from DSL scripts (MAL, OAL, LAL, Hierarchy)', 'Runs the compiler', 'dumps .class files for inspection'. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' (generate bytecode classes from DSL scripts, run compiler, dump .class files), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes domain-specific terms like 'bytecode', 'DSL scripts', 'MAL', 'OAL', 'LAL', 'Hierarchy', '.class files', and 'compiler'. However, these are highly technical/jargon terms that a user might use, but lacks common variations or more natural phrasing a user might say (e.g., 'compile DSL', 'generate classes').

2 / 3

Distinctiveness Conflict Risk

Very specific niche: bytecode generation from particular DSL scripts (MAL, OAL, LAL, Hierarchy) with .class file output. This is highly unlikely to conflict with other skills due to the very specific domain and named DSL languages.

3 / 3

Total

10

/

12

Passed

Implementation

87%

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

This is a well-crafted, concise skill that provides fully actionable commands for generating DSL bytecode classes across four DSL types. Its main weakness is the lack of explicit validation/error-handling guidance—there's no mention of checking test results or handling failures before proceeding to inspect output. Overall it's a strong reference skill for a specific development task.

Suggestions

Add a brief validation step after each command, e.g., 'Verify the test passed (exit code 0 / BUILD SUCCESS) before looking for generated classes. If it fails, check the test output for compilation errors in the DSL script.'

DimensionReasoningScore

Conciseness

Every section is lean and purposeful. No unnecessary explanations of what DSLs are, what bytecode is, or how Maven works. Each DSL type gets exactly the command and output location—nothing more.

3 / 3

Actionability

All commands are fully executable, copy-paste ready bash commands with specific test class names, Maven flags, and exact output paths. The javap decompilation command and clean command are also concrete and complete.

3 / 3

Workflow Clarity

The steps are clearly sequenced (run command → find output → decompile with javap), but there's no explicit validation checkpoint—e.g., checking if the test passed before looking for output files, or what to do if generation fails. For a build/generation workflow, a feedback loop on failure would strengthen this.

2 / 3

Progressive Disclosure

For a single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear section headers per DSL type, a post-generation section, and a cleanup section. The structure is easy to navigate and appropriately scoped.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
apache/skywalking
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.