memory-profiler-setup
Memory Profiler Setup - Auto-activating skill for Performance Testing. Triggers on: memory profiler setup, memory profiler setup Part of the Performance Testing skill category.
34
Quality
3%
Does it follow best practices?
Impact
90%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/memory-profiler-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete actions or capabilities, and provides no meaningful guidance on when Claude should select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configure heap profilers, set up memory allocation tracking, analyze memory snapshots, detect memory leaks'
Include a 'Use when...' clause with natural trigger terms like 'memory leak', 'heap dump', 'memory usage', 'RAM consumption', 'out of memory', or specific tool names like 'Valgrind', 'heaptrack'
Remove the duplicate trigger term and expand with variations users would naturally say when needing memory profiling help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Memory Profiler Setup' without describing any concrete actions. It doesn't explain what setting up a memory profiler actually involves or what capabilities the skill provides. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' guidance is just a repetition of the skill name rather than meaningful trigger scenarios. No 'Use when...' clause with explicit triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('memory profiler setup' listed twice) and overly narrow. Missing natural variations users might say like 'profile memory', 'memory usage', 'heap analysis', 'memory leaks', or specific tool names. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Performance Testing' category and 'memory profiler' terminology provide some specificity, but without concrete actions or tool names, it could overlap with other performance or debugging skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is entirely meta-description with no actual instructional value. It describes what a memory profiler setup skill should do without providing any concrete guidance, code examples, tool recommendations, or actionable steps. The content is essentially a placeholder template that would need to be completely rewritten to be useful.
Suggestions
Add concrete code examples for setting up memory profilers (e.g., Python's memory_profiler, Valgrind, or language-specific tools)
Include specific commands for installation and configuration of at least one memory profiling tool
Provide a clear workflow with steps: install tool -> configure -> run profiler -> interpret results -> identify leaks
Replace generic capability claims with actual executable guidance and example outputs showing memory profiler results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are filler with no actual information about memory profiler setup. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific tools, no actual steps for setting up a memory profiler. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for memory profiler setup. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no structure beyond generic headings, and no navigation to useful resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
0c08951
- 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.