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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill memory-profiler-setupOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as its own trigger term and fails to describe what actions the skill performs or when it should be used. The description needs substantial expansion to be functional.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures memory profiling tools, analyzes heap dumps, identifies memory leaks, tracks allocation patterns'
Include a 'Use when...' clause with natural trigger terms like 'memory leak', 'heap analysis', 'out of memory', 'memory usage', 'profiling tools', or specific tool names (Valgrind, heaptrack, etc.)
Remove the duplicate trigger term and expand with variations users would naturally say when needing memory profiling assistance
| 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 explicit 'Use when...' clause with actionable context. | 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 leak', 'heap analysis', 'memory usage', or specific tool names. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'memory profiler' is somewhat specific to a particular domain, but 'Performance Testing' category mention is generic. Could potentially conflict with other performance or debugging skills without clearer boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what a memory profiler setup skill should do but provides absolutely no concrete guidance, code examples, tool recommendations, or workflows for actually setting up memory profilers like Valgrind, heaptrack, memory_profiler (Python), or similar tools.
Suggestions
Add concrete, executable code examples for at least one memory profiler (e.g., Python's memory_profiler with @profile decorator, or Node.js heap snapshots)
Include a clear workflow with numbered steps: install profiler, instrument code, run profiling, analyze results, with validation at each step
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific tool names, commands, and configuration snippets
Add a quick reference section linking to detailed guides for different profilers (Python, Node.js, Java, etc.) if multiple tools are in scope
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for setting up any 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 flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.