CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

perf-profile

Performance profiling — find bottlenecks, measure against budgets, produce ranked optimization recommendations.

Quality

74%

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

Quality

Content

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

The body delivers a strongly sequenced, validated workflow with executable commands and a complete report template — workflow clarity is excellent. Its main weakness is token efficiency: the NOT ASSESSED/no-fabrication doctrine is repeated across four sections and could be consolidated into one authoritative statement.

Suggestions

Consolidate the NOT ASSESSED / no-fabrication doctrine — currently restated in the header, Phase 2, and Phase 4 — into a single authoritative section and reference it elsewhere in one line.

Define a rough estimation method for Phase 3 hotspot costs (e.g., per-frame call frequency × operation cost class) so "estimate cost" is actionable.

Consider moving the report template and the CPU/memory/rendering/I/O target lists into a reference file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The no-fabrication doctrine is restated four times ("A verdict of `NOT ASSESSED` is a success", "Absence of evidence is never evidence of absence", "do not leave a mandated cell to be filled", "the exact fabrication this skill's own header warns about"), which is more than minor over-explanation. It is not 2 because the content is project-specific policy rather than concepts Claude already knows, and most sections are concrete.

3 / 5

Actionability

Provides copy-paste-ready commands (the four `yaml-helper.sh get_effective_yaml_key` lines), a complete report template with exact file destination, and concrete Phase 5 options A–D. Not 5 because Phase 3 instructs to "estimate cost" without any estimation method, and hotspot impact figures have no defined procedure.

4 / 5

Workflow Clarity

Clear Phase 0–6 sequence with explicit validation checkpoints and recovery loops: the FOUND/ABSENT input checklist, "Surface any other value to the user and fall back to `warn`", ask-before-write for the report, and a closed verdict enum with an explicit could-not-run state. Matches the explicit-validation-with-feedback-loops anchor; the neighboring anchor 4 is weaker than what is written.

5 / 5

Progressive Disclosure

Single-file skill (no bundle files exist) with well-organized phased sections and clearly signaled external docs (`.claude/docs/automation-modes.md`, `config-resolution.md`). At ~230 lines, the report template and the profiling-target lists could be split into reference files, so organization is good but not optimal.

4 / 5

Total

16

/

20

Passed

Description

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

The description is concise, specific, and uses natural trigger vocabulary, but it omits any explicit "Use when..." guidance, which both caps completeness and slightly raises conflict risk. Adding a trigger clause with common synonyms (slow, lag, framerate, FPS) would lift it to the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions performance, slowdowns, lag, framerate/FPS, or asks to optimize a system."

Include natural synonyms users actually say — "slow", "lag", "framerate", "speed up" — alongside the current technical terms.

Mention the concrete deliverable (a written profiling report with ranked recommendations) to close the coverage gap.

DimensionReasoningScore

Specificity

Lists three concrete actions — "find bottlenecks, measure against budgets, produce ranked optimization recommendations" — which matches the several-specific-actions anchor, but omits report generation and the scope/timeline decision step, leaving minor gaps in coverage rather than comprehensive coverage.

4 / 5

Completeness

The "what" is clearly stated (find bottlenecks, measure, produce ranked recommendations) but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not 2 because the "what" is specific and unambiguous.

3 / 5

Trigger Term Quality

"Performance profiling", "bottlenecks", "budgets", and "optimization" are terms users would naturally say, but common variations like "slow", "lag", "framerate", "FPS", or "speed up" are missing, so keyword coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Performance profiling" carves a mostly distinct niche with domain-specific triggers, though the absent when-clause and the generic "optimization recommendations" phrasing leave minor overlap risk with related optimization or gate-checking skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/perf-profile/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.