profiling-application-performance
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill profiling-application-performanceExecute this skill enables AI assistant to profile application performance, analyzing cpu usage, memory consumption, and execution time. it is triggered when the user requests performance analysis, bottleneck identification, or optimization recommendations. the... Use when optimizing performance. Trigger with phrases like 'optimize', 'performance', or 'speed up'.
48%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 87 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'profiling-application-performance' | Pass |
description_field | 'description' field is valid (366 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
7%This skill is largely boilerplate with no actionable content. It describes what profiling conceptually does rather than providing concrete commands, code examples, or specific tool invocations. The entire document could be replaced with 10-15 lines of actual executable guidance showing how to invoke the profiler and interpret results.
Suggestions
- Replace abstract descriptions with concrete, executable commands showing how to invoke the application-profiler plugin (e.g., actual CLI commands or API calls)
- Add real code examples for each supported language stack (Node.js, Python, Java) showing exact profiling invocation and output interpretation
- Remove generic sections like 'Instructions', 'Output', 'Error Handling', and 'Resources' that contain no specific information
- Include example profiler output and how to interpret the results to identify specific bottlenecks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill', and 'Integration' contain redundant explanations. The 'Instructions' section is generic boilerplate that adds no value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill describes what it will do abstractly ('Activate the application-profiler plugin', 'Analyze memory allocation patterns') without showing how to actually invoke the profiler, what commands to run, or what output to expect. | 1 / 3 |
Workflow Clarity | Steps are vague and lack specificity. 'Activate the application-profiler plugin' and 'Analyze the application's memory allocation patterns' provide no actual execution details. No validation checkpoints, no error recovery, and no concrete sequence of commands or actions. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files. The structure exists but contains too much inline content that could be condensed, and references to 'Project documentation' and 'Related skills' are vague without actual links. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%The description has good trigger term coverage and completeness with explicit 'Use when' guidance, but suffers from a truncated capability list ('the...') that undermines specificity. The performance optimization domain is reasonably distinct but could conflict with more specialized optimization skills due to broad trigger terms.
Suggestions
- Complete the truncated description to fully list all capabilities (the '...' cuts off important information)
- Add more specific differentiators to distinguish from other optimization skills, such as specifying supported languages, profiling tools, or types of applications (web, CLI, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (performance profiling) and lists some actions (analyzing cpu usage, memory consumption, execution time, bottleneck identification, optimization recommendations), but the description is truncated ('the...') and doesn't provide comprehensive concrete actions. | 2 / 3 |
Completeness | Explicitly answers both what (profile application performance, analyze cpu/memory/execution time) and when (triggered for performance analysis, bottleneck identification, optimization) with a clear 'Use when' clause and explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'optimize', 'performance', 'speed up', 'performance analysis', 'bottleneck identification'. These are common phrases users naturally use when seeking performance help. | 3 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to performance profiling, but terms like 'optimize' and 'performance' are broad and could overlap with other optimization-related skills (database optimization, code refactoring, etc.). | 2 / 3 |
Total | 10 / 12 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.