CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

76%

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

60%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.

A well-organized, opinionated methodology skill with a clear workflow and useful guardrails, but it stays at the level of principles: no concrete commands, tools, or benchmark examples make it fully actionable, and the workflow section duplicates the numbered sections. It is self-contained and free of dead references, so progressive disclosure is sound.

Suggestions

Add one or two concrete executable examples (e.g., a sample benchmark script invocation or a profiler command) so 'measure comprehensively' and 'instrument the system' translate into specific actions.

Remove the redundancy between sections 1–4 and 'Recommended workflow' — either fold the workflow into a single ordered checklist or cut the overlapping prose to tighten the token budget.

Make the validation loop explicit in the workflow (e.g., a step like 'If the re-measure shows no improvement or a regression, revert and re-attribute the bottleneck') to earn full workflow-clarity credit.

DimensionReasoningScore

Conciseness

The body is moderately lean but noticeably redundant — the 'Recommended workflow' section restates sections 1–4 (define metrics → measure → attribute → fix → re-measure), and phrases like "Do not optimize blindly" and "Prioritize the largest wins first" restate the numbered sections. This fits the anchor 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

As an instruction-only skill it gives specific direction (check for "wrong asymptotic complexity", "batching, caching, query patterns, parallelism") but no executable specifics — no commands, tool names, or instrumentation examples for "instrument the system so you can see where time and resources are going". This matches 'some concrete guidance but incomplete; missing key details', below 4 which would require mostly executable guidance.

3 / 5

Workflow Clarity

The 'Recommended workflow' lists a clear 8-step sequence with a re-measure step and a terminate condition ("Repeat until the target is met or tradeoffs stop being worth it"), and the guardrails add "Do not claim an optimization without before/after evidence" — a validation checkpoint. It sits at 4 rather than 5 because the re-validate/re-check loop is implicit rather than an explicit error-recovery step, and the workflow repeats earlier sections without adding operational detail.

4 / 5

Progressive Disclosure

The skill has no bundle files, and the body is well organized into clearly headed sections (Core principle, steps 1–4, Recommended workflow, Guardrails) with no dead references — all content is self-contained methodology prose, appropriately so. It scores 4 rather than 5 because at ~85 lines it exceeds the under-50-lines simple-skill exception, and the 'Recommended workflow' duplication suggests the content could be consolidated.

4 / 5

Total

14

/

20

Passed

Description

83%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.

A strong description with explicit 'Use when' triggers, natural user vocabulary, and a concrete multi-part methodology. Main gaps are missing common phrasings like 'faster', 'speed up', or 'profile', and moderate breadth that slightly raises conflict risk with adjacent performance-related skills.

DimensionReasoningScore

Specificity

The description names several concrete methodological actions — "defining target metrics, measuring comprehensively, attributing bottlenecks, validating with static analysis, and prioritizing macro-optimizations before micro-optimizations" — which matches the 'lists several specific actions; minor gaps in coverage' anchor. It falls short of 5 because the actions describe methodology rather than a comprehensive set of concrete deliverables, and short of nothing below 4 since the verbs are specific and varied.

4 / 5

Completeness

Both halves are explicit: "Use when improving performance, latency, throughput, memory usage, or general efficiency" answers when with concrete trigger phrases, and "Start by defining target metrics, measuring comprehensively, attributing bottlenecks..." answers what. This matches the score-5 anchor; the 4 anchor would require the 'when' to be less specific than it is.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "improving performance, latency, throughput, memory usage, or general efficiency" — good keyword coverage matching the score-4 anchor ('a few natural terms missing'). Not 5 because common variations like 'make it faster', 'speed up', 'reduce cost', or 'profile' are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (performance/efficiency optimization) that is mostly distinct with minor overlap risk against closely related skills (e.g., database tuning or profiling tools), matching the 4 anchor. It is not 5 because 'performance' and 'efficiency' are broad enough that other skills could plausibly claim overlapping triggers.

4 / 5

Total

17

/

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.

Validation — 15 / 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

Path

.jcode/skills/optimization/SKILL.md

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.