CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

63

Quality

79%

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 ./.github/skills/chat-perf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable skill body with strong command coverage and real feedback loops, but it is noticeably verbose (teaching statistics and performance concepts Claude already knows) and monolithic with no bundle files, hurting token efficiency and progressive disclosure.

Suggestions

Cut the concept-explanation prose: drop the baseline rationale (line 44), the Welch's t-test / sample-size tutorial (lines 155-163), and the CSS-animation inflation explanation (lines 187-200) — keep the actionable thresholds and exit-code behavior, not the statistics lesson.

Move the full flag reference table and the CI bisecting command catalog into a reference file (e.g. references/ci-bisect.md) and link to it from SKILL.md, which would simultaneously fix progressive disclosure and cut inline length.

Consolidate `--no-baseline` — it is explained in the flag table, the blockquote, and the build-modes section; state it once and cross-reference.

DimensionReasoningScore

Conciseness

Noticeably verbose at ~318 lines: the line-44 blockquote explains what a baseline is for, lines 155-163 give a Welch's t-test / sample-size tutorial, lines 187-200 explain why CSS animations inflate layout/style counts, and the `--gc-object-stats` flag is a paragraph of rationale — several sections teach concepts Claude already knows.

2 / 5

Actionability

Abundant copy-paste-ready `npm run` and `gh` commands with a complete flag table and worked examples covering the common cases (local vs remote, resume, leak check, CI bisecting).

5 / 5

Workflow Clarity

Clear sequenced workflows with validation signals (statistical-significance gating, exit codes, resume-for-confidence feedback loop, and the 4-step CI bisect with a 'confirm real vs noise' checkpoint), though some checkpoints are implicit rather than explicit gating steps.

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets are empty) and the body is a monolith — the full flag table, entire CI command catalog, and statistics/metrics rationale all live inline where reference files would be more appropriate; section headers give structure but content that should be separate is inlined.

3 / 5

Total

14

/

20

Passed

Description

87%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, well-scoped description that answers both what and when with concrete, natural trigger phrases and minimal conflict risk. Minor additional specificity or synonym coverage would push specificity and trigger quality to full marks.

DimensionReasoningScore

Specificity

Lists concrete actions ('Run chat perf benchmarks and memory leak checks') against specific targets ('local dev build or any published VS Code version'), though it covers two macro-actions rather than an exhaustive action list.

4 / 5

Completeness

Explicitly states what ('Run chat perf benchmarks and memory leak checks...') and when ('Use when investigating chat rendering regressions, validating perf-sensitive changes...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural developer-facing triggers like 'chat rendering regressions', 'perf-sensitive changes to chat UI', and 'memory leaks' are present; a few synonyms (e.g. 'slow', 'latency') are missing.

4 / 5

Distinctiveness Conflict Risk

A clearly scoped niche (VS Code chat performance and leak checking) with distinct triggers, making collision with unrelated skills unlikely.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 4 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/chat-perf/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.