aggregating-performance-metrics

Aggregate and centralize performance metrics from applications, systems, databases, caches, and services. Use when consolidating monitoring data from multiple sources. Trigger with phrases like "aggregate metrics", "centralize monitoring", or "collect performance data".

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/metrics-aggregator/skills/aggregating-performance-metrics/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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

The body is well-sectioned and gives a coherent high-level process, but it is descriptive rather than executable and padded with generic marketing prose. Its biggest gap is actionability: no concrete config, code, or alert examples for a tool-configuration skill.

Suggestions

Replace abstract guidance with executable artifacts: add a sample Prometheus scrape config, a concrete alert-rule example, and reference the bundled scripts/*.py with actual invocation commands.

Cut the marketing-flavored Overview and How It Works prose ('empowers Claude', 'simplifies the process') so the remaining tokens all earn their place.

Add an explicit validation/verification checkpoint in the workflow (e.g., verify scrape targets are up and confirm alert thresholds fire before declaring setup complete).

Dimension	Reasoning	Score
Conciseness	The Overview ('empowers Claude to streamline...', 'simplifies the process...leading to improved insights') and How It Works restate generic concepts Claude already knows, so the body could be tightened, though most sections are reasonably structured.	2 / 3
Actionability	The body describes rather than instructs ('Guide the user in configuring...', 'Set up dashboards and alerts') with no executable code, Prometheus/StatsD config snippets, or concrete alert-rule examples; the scripts listed in scripts/README.md are never referenced or shown.	1 / 3
Workflow Clarity	The Instructions section gives a clear six-step sequence and Error Handling lists troubleshooting, but there are no explicit validation checkpoints or feedback loops, so checkpoints are only implicit.	2 / 3
Progressive Disclosure	Sections are well-organized, but the bundle is effectively empty (only READMEs; the listed scripts/*.py and assets template are not actual files) and the body references no real detail files beyond a phantom ${CLAUDE_SKILL_DIR}/metrics/ path, leaving generic content inline that could be split out.	2 / 3
	Total	7 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 well-constructed description that answers both what and when with natural trigger phrases and a clear niche. Its only weakness is that the two named actions are near-synonymous, limiting the specificity of capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain broadly ('applications, systems, databases, caches, and services') with two concrete actions ('Aggregate and centralize'), but the actions are near-synonymous rather than the multiple distinct actions of the anchor-3 example.	2 / 3
Completeness	Clearly states what it does (aggregate/centralize metrics from listed sources) and when to use it ('Use when consolidating monitoring data...') with explicit trigger guidance, in third-person/imperative voice.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('aggregate metrics', 'centralize monitoring', 'collect performance data') are terms a user would plausibly say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The metrics-aggregation/centralization niche with its specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: plugins/performance/metrics-aggregator/skills/aggregating-performance-metrics/SKILL.md
Commit: 0540a62

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.