CtrlK
BlogDocsLog inGet started
Tessl Logo

optimize

Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.

85

0.98x
Quality

80%

Does it follow best practices?

Impact

88%

0.98x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/optimize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 content is actionable and well-sequenced with strong verification checkpoints, but it is verbose with generic advice Claude already knows and monolithic with no progressive disclosure into reference files.

Suggestions

Trim well-known guidance (image formats, code splitting, Core Web Vitals definitions) to lean checklists, keeping only the non-obvious callouts like the 'NEVER' list.

Split the detailed Core Web Vitals and framework-specific sections into reference files (e.g. CORE_WEB_VITALS.md, REACT.md) referenced one level deep from SKILL.md.

DimensionReasoningScore

Conciseness

The body is efficient and well-organized but restates widely-known web performance guidance (WebP/AVIF, lazy loading, code splitting, Core Web Vitals thresholds) that Claude already knows, so it could be tightened considerably.

2 / 3

Actionability

It provides complete, executable examples — responsive `<img srcset>`, dynamic `import()` lazy loading, `@font-face` with `font-display`, batched read/write to avoid layout thrashing, and IntersectionObserver — that are copy-paste ready.

3 / 3

Workflow Clarity

The Assess → Optimize → Verify sequence is explicit, with measurement checkpoints ("Measure before and after", a dedicated Verify Improvements section) forming a clear measure/optimize/re-measure feedback loop.

3 / 3

Progressive Disclosure

Content is well sectioned but monolithic — everything is inline with no external reference files, so material that should be split out (e.g. the per-vital checklists) is not progressively disclosed.

2 / 3

Total

10

/

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 is specific and uses natural trigger terms with a clear, distinctive front-end performance niche, but it omits any explicit 'Use when...' guidance, leaving the 'when' half of completeness implicit.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to speed up a UI, reduce load times, improve Core Web Vitals, or shrink bundle size.'

Tighten the trailing "Makes experiences faster and smoother." since it restates the opening and adds little trigger value.

DimensionReasoningScore

Specificity

The description enumerates concrete capability areas — "loading speed, rendering, animations, images, and bundle size" — matching the anchor for listing multiple specific actions rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or explicit trigger guidance, which per the judging guidelines caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Terms like "loading speed", "animations", "images", and "bundle size" are natural phrasing a user would say when requesting performance work, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The front-end interface-performance niche with its named sub-areas is clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
The-Vibe-Company/companion
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.