CtrlK
BlogDocsLog inGet started
Tessl Logo

optimization

Use when improving performance, latency, throughput, memory usage, or general efficiency. Start by defining target metrics, measuring comprehensively, attributing bottlenecks, validating with static analysis, and prioritizing macro-optimizations before micro-optimizations.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.jcode/skills/optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-3

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 with a clear recommended workflow and guardrails, but it stays at a conceptual level with no concrete tooling or code and only implied validation checkpoints, which caps actionability and workflow clarity.

Suggestions

Add at least one concrete measurement example (e.g., a timing/profiling command or a repeatable benchmark snippet) to lift actionability from directional to executable.

Turn the workflow's 'Re-measure' step into an explicit validation gate (e.g., 'Only proceed to the next fix when the change is reproduced and shows a measurable improvement') to strengthen workflow clarity.

Trim restatements like 'Do not optimize blindly.' and consolidate the macro-vs-micro points, which currently recur across sections 1, 4, and Guardrails.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-organized, but explanatory restatements like 'Do not optimize blindly.' and repeated macro-before-micro points add mild padding that could be tightened without losing clarity.

2 / 3

Actionability

It gives strong directional guidance (instrument, attribute across the full path, check asymptotic complexity) but no concrete commands, tools, or code, so it instructs at the conceptual rather than executable level.

2 / 3

Workflow Clarity

The 'Recommended workflow' is a clear 8-step sequence with a re-measure loop, but explicit validation checkpoints (e.g., 'confirm baseline is repeatable before changing') are only implied rather than stated as gating steps.

2 / 3

Progressive Disclosure

With no bundle files and a single self-contained SKILL.md, the content is organized into clearly labeled sections (Core principle, numbered sections, Recommended workflow, Guardrails) that fit the simple-skill allowance for a top score.

3 / 3

Total

9

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 has a clear 'Use when...' trigger with strong natural keyword coverage and answers both what and when, but it lists metric categories rather than concrete actions and the optimization domain is broad enough to risk overlap with adjacent skills.

Suggestions

Lead the description with concrete verbs (e.g., 'Profile, instrument, and refactor to improve performance...') instead of a list of metric nouns to raise specificity.

Narrow the trigger with a disambiguating cue (e.g., 'Use when the user asks to make existing code faster or lighter — not for correctness-only changes') to reduce overlap with profiling or refactoring skills.

DimensionReasoningScore

Specificity

It names the domain (performance, latency, throughput, memory, efficiency) but lists metric nouns rather than concrete optimizing actions like 'profile', 'instrument', or 'refactor'; the actions appear later in the body, not the description.

2 / 3

Completeness

It answers both 'what' (define metrics, measure, attribute bottlenecks, validate, prioritize) and 'when' ('Use when improving performance, latency, throughput, memory usage, or general efficiency') with an explicit trigger clause.

3 / 3

Trigger Term Quality

It covers natural terms a user would say (performance, latency, throughput, memory usage, efficiency) and is phrased as an explicit trigger ('Use when improving...'), giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Optimization is a broad cross-cutting concern that could overlap with profiling, performance-testing, or refactoring skills; the description carves a niche but the trigger is general enough to risk overlapping activation.

2 / 3

Total

10

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
1jehuang/jcode
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.