CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-system-throughput

Analyze and optimize system throughput including request handling, data processing, and resource utilization. Use when identifying capacity limits or evaluating scaling strategies. Trigger with phrases like "analyze throughput", "optimize capacity", or "identify bottlenecks".

57

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

The body is a high-level, descriptive overview rather than actionable guidance: it lists vague steps, omits any use of the bundled scripts, and lacks validation checkpoints. It reads as a template-filled document rather than lean, executable instruction.

Suggestions

Replace abstract Instructions with concrete commands that invoke the bundled scripts, e.g. 'python scripts/analyze_throughput.py <dir> --json' and 'python scripts/identify_bottlenecks.py <input>'.

Reference the actual bundle files from the body (analyze_throughput.py, identify_bottlenecks.py) instead of the non-existent ${CLAUDE_SKILL_DIR}/metrics/throughput/ path, so progressive disclosure is correctly wired.

Add explicit validation checkpoints to the workflow (e.g. verify metrics were collected before identifying bottlenecks; confirm a baseline exists before recommending scaling strategies).

DimensionReasoningScore

Conciseness

The ~94-line body is mostly efficient but padded with vague platitudes such as 'provides a starting point for further investigation' and 'gain a more comprehensive understanding of system behavior' that could be tightened; it does not over-explain concepts Claude already knows, so it stays above a 1.

2 / 3

Actionability

The Instructions are abstract directions ('Collect request and data throughput metrics', 'Generate capacity planning recommendations') with no concrete commands or code, even though executable scripts exist in the bundle and are never invoked — it describes rather than instructs.

1 / 3

Workflow Clarity

A six-step Instructions sequence is present, but there are no validation checkpoints or feedback loops in the workflow; the separate Error Handling section lists generic troubleshooting rather than inline checkpoints.

2 / 3

Progressive Disclosure

Bundle scripts (analyze_throughput.py, identify_bottlenecks.py) exist but are never referenced from the body, and the Prerequisites point to a ${CLAUDE_SKILL_DIR}/metrics path that does not exist in the bundle — structure is present but references are not clearly signaled or correctly wired.

2 / 3

Total

7

/

12

Passed

Description

100%

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 well-formed: third-person voice, concrete capability listing, an explicit 'Use when' trigger clause, and natural trigger phrases. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across named domains — 'Analyze and optimize system throughput including request handling, data processing, and resource utilization' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Analyze and optimize system throughput...') and when ('Use when identifying capacity limits or evaluating scaling strategies') with explicit triggers, matching the top anchor.

3 / 3

Trigger Term Quality

Provides natural trigger phrases users would actually say — 'analyze throughput', 'optimize capacity', or 'identify bottlenecks' — giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Throughput/capacity analysis is a clear niche with distinct trigger phrases, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation14 / 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
jeremylongshore/claude-code-plugins-plus-skills
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.