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
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 title and category label with no substantive content. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other performance testing skills and provides no useful information for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures memory profiling tools (Valgrind, heaptrack, dotMemory), sets up heap snapshots, and analyzes memory allocation patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about memory leaks, heap profiling, memory usage analysis, RAM consumption tracking, or setting up memory profiling tools.'
Remove the duplicate trigger term and expand with varied natural language terms users might actually say, such as 'memory leak detection', 'heap analysis', 'memory consumption', 'profiling setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Memory Profiler Setup') and its category ('Performance Testing') but does not describe any concrete actions. There are no specific capabilities listed such as configuring profilers, analyzing memory leaks, or generating reports. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and provides no explicit 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'memory profiler setup' repeated twice, providing no variation or natural keywords a user might say (e.g., 'memory leak', 'heap analysis', 'memory usage', 'profiling tool', 'RAM consumption'). | 1 / 3 |
Distinctiveness Conflict Risk | The term 'memory profiler setup' is somewhat specific to a niche domain, which reduces conflict risk compared to fully generic descriptions. However, it could overlap with other performance testing or profiling skills due to lack of detailed scoping. | 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 is essentially an empty placeholder. It contains no actionable content whatsoever—no code examples, no commands, no tool-specific guidance for memory profiling. Every section describes what the skill would theoretically do rather than actually providing instructions for setting up a memory profiler.
Suggestions
Replace the entire body with actual memory profiler setup instructions, including concrete code examples for at least one tool (e.g., Python's memory_profiler, Valgrind, or heaptrack) with executable, copy-paste-ready commands.
Add a clear step-by-step workflow: install profiler → instrument code → run profiling → analyze results → validate findings, with explicit validation checkpoints.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) as they provide no value to Claude and waste context window tokens.
If the skill covers multiple profiling tools or languages, add a quick-start section with the most common case and reference separate files for advanced scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific tools, no configuration examples. The skill contains only vague promises like 'provides step-by-step guidance' and 'generates production-ready code' without actually delivering any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for how to actually set up a memory profiler, no validation checkpoints, and no sequenced actions of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections that exist (Purpose, When to Use, Capabilities) are all boilerplate with no substance. | 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
4dee593
- 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.