CtrlK
BlogDocsLog inGet started
Tessl Logo

code-optimizer

Deep code optimization audit using parallel specialist agents. Each agent hunts for performance anti-patterns, inefficiencies, and suboptimal code using pattern-based detection (Grep/Glob) WITHOUT reading the full source code first — avoiding anchoring bias on existing implementations. Covers ALL optimization domains: database queries, memory leaks, algorithmic complexity, concurrency, bundle size, dead code, I/O & network, rendering/UI, data structures, error handling, caching, build config, security-performance, logging, and infrastructure. Use when asked to: "optimize my code", "find performance issues", "audit code quality", "speed up my app", "find bottlenecks", "code review for performance", "find anti-patterns", "improve code efficiency", "reduce latency", "optimize performance", "code smell detection", "find slow code", "optimize this project", "performance audit", "code optimization". Also triggers on: "optimizar codigo", "encontrar cuellos de botella", "mejorar rendimiento".

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clean progressive-disclosure structure and verified reference files. Its main gaps are a missing consolidation-time validation checkpoint for the batch agent run and some explanatory prose that could be trimmed.

Suggestions

Add an explicit validation/dedup step to Step 3 (e.g., confirm each finding against the cited file:line before surfacing it) to close the batch-operation feedback loop.

Trim the anchoring-bias rationale in 'Critical Principle' since the numbered rules already enforce the behavior, and shorten the report-format template to its essential structure.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the 'Critical Principle' section restates the anchoring-bias rationale already implied by the rules, and the full report-format markdown template is elaborate; it could be tightened without losing clarity.

2 / 3

Actionability

Provides a concrete agent-to-reference table, a copy-paste-ready prompt template with explicit placeholders, and specific Grep/Glob detection guidance, giving fully executable guidance.

3 / 3

Workflow Clarity

Steps are clearly sequenced (detect stack, spawn agents, consolidate), but this batch operation across 13 agents has no validation/feedback checkpoint in the consolidate phase, capping workflow clarity per the rubric's batch-operation rule.

2 / 3

Progressive Disclosure

SKILL.md is a clear orchestration overview with a well-signaled, one-level-deep reference table; all 15 referenced files exist on disk and content is appropriately split between SKILL.md and references/.

3 / 3

Total

10

/

12

Passed

Description

92%

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 strong and specific, clearly stating capabilities and providing rich, natural trigger terms in both English and Spanish. Its only weakness is that several broad triggers risk overlap with general code-review skills.

Suggestions

Narrow overlapping triggers like 'audit code quality' and 'code smell detection' toward performance-specific phrasing (e.g., 'find performance code smells') to reduce conflict with general review skills.

Tighten the domain list into the description's lead so the performance focus registers before the long trigger enumeration.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('hunts for performance anti-patterns, inefficiencies, and suboptimal code', 'pattern-based detection (Grep/Glob)') and enumerates 15 specific optimization domains, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what the skill does ('Deep code optimization audit using parallel specialist agents') and when to use it via a 'Use when asked to...' clause with explicit triggers, satisfying both what AND when.

3 / 3

Trigger Term Quality

Includes a broad set of natural user phrases ('optimize my code', 'find performance issues', 'speed up my app', 'find bottlenecks', 'code review for performance') plus Spanish variants, giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The performance-optimization niche is clear, but broad triggers like 'audit code quality', 'code review for performance', and 'code smell detection' could overlap with general code-review or linting skills, so it is somewhat specific but not fully conflict-free.

2 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gsd-build/gsd-2
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.