m10-performance
CRITICAL: Use for performance optimization. Triggers: performance, optimization, benchmark, profiling, flamegraph, criterion, slow, fast, allocation, cache, SIMD, make it faster, 性能优化, 基准测试
44
46%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/m10-performance/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage with a comprehensive list of natural keywords users would use, including colloquial phrases like 'make it faster' and multilingual terms. However, it critically lacks specificity about what the skill actually does—no concrete actions, tools used, or outputs are described. The 'what' portion is essentially just the phrase 'performance optimization' which is too vague to help Claude understand the skill's actual capabilities.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Profiles code with flamegraphs, runs Criterion benchmarks, identifies allocation hotspots, optimizes cache usage, and applies SIMD vectorization.'
Clarify the scope/language context—the mention of 'criterion' and 'SIMD' suggests Rust-specific optimization, which should be stated explicitly to improve distinctiveness and reduce conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Use for performance optimization' but lists no concrete actions. It doesn't describe what the skill actually does—no verbs like 'profile', 'analyze bottlenecks', 'generate flamegraphs', or 'optimize allocations'. The trigger list names tools/concepts but not actions the skill performs. | 1 / 3 |
Completeness | The 'when' is explicitly addressed via the 'Triggers:' list, but the 'what' is extremely weak—it only says 'performance optimization' without describing what concrete actions or outputs the skill provides. The trigger list partially compensates but the 'what' remains vague. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'performance', 'optimization', 'benchmark', 'profiling', 'flamegraph', 'criterion', 'slow', 'fast', 'allocation', 'cache', 'SIMD', 'make it faster', plus Chinese equivalents. These are terms users would naturally use when seeking performance help. | 3 / 3 |
Distinctiveness Conflict Risk | The domain of 'performance optimization' is fairly specific, and the trigger terms like 'flamegraph', 'criterion', 'SIMD' suggest Rust-specific performance work, which narrows the niche. However, 'performance' and 'optimization' are broad enough to potentially conflict with language-specific or web performance skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves as a reasonable reference card for Rust performance optimization concepts, with good use of tables for quick lookup. However, it lacks executable code examples and a clear step-by-step optimization workflow with validation checkpoints, which are critical for a skill that guides performance work. The content also has some redundancy between sections (optimization priority appears twice, anti-patterns and common mistakes overlap).
Suggestions
Add a concrete, sequential workflow section: 'Profile with flamegraph → Identify hotspot → Write criterion benchmark → Apply optimization → Re-benchmark → Verify improvement meets SLA', with explicit validation at each step.
Include at least one complete, executable example showing a before/after optimization (e.g., a criterion benchmark setup, or a flamegraph generation command sequence).
Merge 'Common Mistakes' and 'Anti-Patterns' tables to reduce redundancy, and remove the duplicated optimization priority information.
Remove the abstract 'Trace Up/Trace Down' navigation pattern and replace with direct, actionable cross-references only where needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables, but includes some unnecessary framing ('Thinking Prompt', 'Core Question') and the 'Trace Up/Trace Down' sections add conceptual overhead that Claude doesn't need. The optimization priority list is duplicated (once in the decision table area and once in Quick Reference). Some sections like 'Common Mistakes' and 'Anti-Patterns' overlap significantly. | 2 / 3 |
Actionability | Provides concrete tool names and some specific code snippets (e.g., `Vec::with_capacity(n)`, `Cow<T>`, `SmallVec`), but lacks executable, copy-paste-ready code examples. The guidance is more of a reference/checklist than actionable step-by-step instructions. No complete profiling workflow or benchmark setup code is provided. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for actually performing optimization. The content presents checklists and tables but never walks through a concrete multi-step process like 'profile → identify hotspot → benchmark → optimize → re-benchmark → validate improvement'. For a performance optimization skill involving potentially destructive changes, the lack of validation checkpoints and feedback loops is a significant gap. | 1 / 3 |
Progressive Disclosure | References to related skills (m01-ownership, m07-concurrency, m02-resource, domain-*) are present and clearly signaled in tables, but no bundle files exist to support them. The content itself is moderately well-organized with sections and tables, but the 'Trace Up/Trace Down' pattern adds structural complexity without clear navigation benefit. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
fa60f79
- 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.