CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance

Profile PsychSift query, retrieval, rendering, bundle, worker, queue, memory, and capacity bottlenecks with reproducible local evidence. Use for latency, throughput, resource, scaling, or bundle-budget work.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An extremely lean, well-sequenced performance methodology that fully respects the token budget and needs no bundle files. Its main gap is actionability: it never names the concrete profiling/budget tools, fixture commands, or measurement invocations that would make the guidance executable rather than purely methodological.

Suggestions

In step 2, name the actual profiling and budget tools available in the PsychSift repo (e.g., the profiler CLI or budget script with an example invocation) instead of the generic "existing profiling or budget tools".

Add one concrete example of the step-4 comparison, such as the command used to capture before/after latency distributions and how many runs constitute a distribution.

Specify what "deterministic local fixtures" means in this codebase — a path or command to run them — so the instruction is executable without guesswork.

DimensionReasoningScore

Conciseness

Six one-line directives ("Define the user-visible metric, baseline, workload, environment, and target before optimizing", "Make one scoped change at a time") with zero padding and no explanation of concepts Claude already knows — every token earns its place. Matches the lean-and-efficient anchor exactly.

5 / 5

Actionability

Lines like "Use deterministic local fixtures and existing profiling or budget tools first" and "Isolate CPU, memory, I/O, ... effects" give concrete methodological direction but name no actual tool, command, fixture path, or example, so key executable details are missing. Above anchor 2 because the guidance is specific in intent (distributions not single runs, approval-gating), below anchor 4 because nothing is directly executable.

3 / 5

Workflow Clarity

A clear ordered sequence (define metrics → local fixtures → isolate effects → one scoped change → gate risky profiling → report) with implicit checkpoints via the baseline in step 1 and "compare before/after distributions, not a single run" in step 4. Not a 5 because there is no explicit validation/feedback loop for what to do when a change regresses or a checkpoint fails.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external content that needs splitting, no bundle files exist, and the single numbered list under one header is well-organized and easy to navigate. Per the rubric's simple-skill guideline, this earns a 5 with just well-organized sections.

5 / 5

Total

17

/

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 description: it pairs a specific, tool-anchored capability statement with an explicit multi-trigger use clause in third-person voice. The only weaknesses are a single action verb limiting action coverage and the absence of everyday synonyms like "slow", "faster", or "optimize" in the trigger list.

DimensionReasoningScore

Specificity

Enumerates eight concrete bottleneck domains ("query, retrieval, rendering, bundle, worker, queue, memory, and capacity") and anchors the action to "reproducible local evidence", which is more comprehensive than the 1-2-action anchor. It stays below a 5 because there is only one action family ("Profile ... bottlenecks") rather than multiple distinct concrete actions like extract/fill/merge/convert.

4 / 5

Completeness

Explicitly answers what ("Profile PsychSift ... bottlenecks with reproducible local evidence") and when ("Use for latency, throughput, resource, scaling, or bundle-budget work") with five concrete trigger phrases, matching the structure of the anchor-5 example. Not a 4 because the when-clause is already explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

The when-clause "Use for latency, throughput, resource, scaling, or bundle-budget work" provides good natural keyword coverage, and "profile" and "bottlenecks" appear in the what-clause. It misses common user phrasings like "slow", "faster", "optimize", or "performance" itself, so it is not comprehensively synonym-covered (5).

4 / 5

Distinctiveness Conflict Risk

Naming the specific system ("PsychSift") plus performance-specific triggers (latency, throughput, scaling, bundle-budget) gives it a clear niche with minimal conflict risk, matching the anchor-5 example's tool-specific pattern.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.agents/skills/performance/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.