flame-graph-generator
Flame Graph Generator - Auto-activating skill for Performance Testing. Triggers on: flame graph generator, flame graph generator Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill flame-graph-generatorOverall
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 relies entirely on the skill name without explaining what flame graphs are, what the skill does with them, or when Claude should use it. The redundant trigger terms and missing action verbs make this description ineffective for disambiguation among multiple skills.
Suggestions
Add specific actions the skill performs, e.g., 'Generates flame graph visualizations from profiling data, analyzes CPU/memory stack traces, identifies performance bottlenecks'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user wants to visualize profiling data, analyze stack traces, identify hot code paths, or debug performance issues'
Expand trigger terms to include variations users would naturally say: 'flame graph', 'flamegraph', 'CPU profile', 'stack visualization', 'perf data', 'profiling visualization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Flame Graph Generator') and category ('Performance Testing') but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'generates', 'analyzes', 'visualizes', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause. The 'Triggers on' line is not a proper when-clause - it just repeats the skill name without describing user scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('flame graph generator' listed twice) and miss natural variations users might say like 'flame graph', 'flamegraph', 'CPU profiling', 'performance visualization', 'stack traces', or 'profiler output'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'flame graph' is a fairly specific term that wouldn't conflict with many other skills, the vague 'Performance Testing' category could overlap with other performance-related skills. The lack of specific use cases makes it harder to distinguish from other profiling tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about flame graph generation. It contains only generic boilerplate describing what a skill should do without providing any actionable information about profiling, sampling, visualization tools (like perf, async-profiler, or flamegraph.pl), or interpretation of flame graphs.
Suggestions
Add executable code examples showing how to generate flame graphs (e.g., using perf + flamegraph.pl, async-profiler for Java, or py-spy for Python)
Include a clear workflow: 1) Capture profiling data, 2) Process/fold stacks, 3) Generate SVG, 4) Interpret results
Provide specific tool commands and options (e.g., 'perf record -F 99 -g -- ./myapp' followed by 'perf script | stackcollapse-perf.pl | flamegraph.pl > output.svg')
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about flame graphs. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on generating flame graphs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger phrases and vague capabilities without any actual sequence for generating flame graphs. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related resources. The content is a shallow placeholder with no depth. | 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.