perf-investigation-logger

Use when appending structured perf investigation notes and evidence.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%

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 tight, well-structured instruction skill: concrete path, clear required-content checklist, complete output template, and a single cleanly signaled external reference. It fully meets the rubric across all dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding; the path, required-content checklist, output template, and constraints each earn their place.	3 / 3
Actionability	Concrete file path, a complete labeled output-format template, and a resolved default (AI_STATE_DIR default .claude) give specific, copy-paste-ready guidance for this instruction-only skill.	3 / 3
Workflow Clarity	This is a single-action skill under 50 lines where the action (append notes to a file) is unambiguous; no destructive or batch operation requires validation checkpoints.	3 / 3
Progressive Disclosure	Under 50 lines with well-organized sections and one clearly signaled one-level-deep reference (docs/perf-requirements.md as the canonical contract); no bundle files are present to verify.	3 / 3
	Total	12 / 12 Passed

Description

75%

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 and answers both what and when with an explicit trigger, but it names only a single action and offers limited trigger-term variation. Strengthening specificity and keyword coverage would raise it further.

Suggestions

Add one or two more concrete actions (e.g., capturing decisions, linking evidence) to lift specificity beyond a single named action.

Broaden trigger terms with natural variations users might say (e.g., "performance notes", "perf evidence", "investigation log") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("perf investigation") and a concrete action ("appending structured perf investigation notes and evidence"), but only a single action rather than multiple specific ones, matching the score-2 anchor.	2 / 3
Completeness	An explicit "Use when..." clause provides the trigger, and "appending structured perf investigation notes and evidence" states the action, clearly answering both when and what.	3 / 3
Trigger Term Quality	Relevant natural terms ("perf investigation", "notes", "evidence") are present but coverage is limited with no common variations, fitting the score-2 anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	"perf investigation notes and evidence" defines a narrow, distinct niche with a specific trigger unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: composio-community/awesome-claude-plugins
Path: perf/skills/investigation-logger/SKILL.md
Commit: e521f7a

Reviewed: about 12 hours 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.