m10-performance
CRITICAL: Use for performance optimization. Triggers: performance, optimization, benchmark, profiling, flamegraph, criterion, slow, fast, allocation, cache, SIMD, make it faster, 性能优化, 基准测试
Install with Tessl CLI
npx tessl i github:actionbook/rust-skills --skill m10-performance82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 natural phrases like 'make it faster' and technical terms like 'flamegraph' and 'criterion', making it highly discoverable. However, it lacks specificity about what concrete actions the skill performs - it reads more like a keyword list than a capability description. Adding explicit actions would significantly improve its utility.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Analyzes bottlenecks, generates flamegraphs, optimizes hot paths, configures criterion benchmarks'
Restructure to follow the pattern: '[Specific actions]. Use when [triggers]' rather than leading with 'CRITICAL: Use for'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (performance optimization) and lists related concepts (benchmark, profiling, flamegraph, criterion, SIMD, cache, allocation), but doesn't describe concrete actions like 'analyze bottlenecks', 'generate flamegraphs', or 'optimize hot paths'. | 2 / 3 |
Completeness | The 'when' is addressed via 'CRITICAL: Use for performance optimization' and trigger list, but the 'what' is weak - it doesn't explain what actions the skill actually performs beyond the domain it covers. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'performance', 'slow', 'fast', 'make it faster', 'optimization', plus technical terms like 'flamegraph', 'criterion', 'SIMD', and even Chinese translations '性能优化', '基准测试'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on performance optimization with highly specific triggers like 'flamegraph', 'criterion', 'SIMD', 'profiling' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that excels at conciseness and organization. It effectively uses tables to compress decision matrices and provides clear workflow guidance for when and how to optimize. The main weakness is the lack of complete, executable code examples - the techniques are named and briefly shown but not demonstrated in full context.
Suggestions
Add one complete, executable benchmark example using criterion showing before/after optimization
Include a minimal flamegraph workflow example with actual commands (e.g., `cargo flamegraph --bin myapp -- args`)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables extensively to compress information, avoids explaining basic concepts Claude knows, and every section delivers actionable value without padding. | 3 / 3 |
Actionability | Provides concrete tool names and techniques with specific syntax examples (e.g., `Vec::with_capacity(n)`, `Cow<T>`), but lacks complete executable code examples. The guidance is specific but more reference-style than copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear decision workflow with explicit sequencing: measure first, identify priority (with expected improvement ranges), then choose technique. The 'Thinking Prompt' section provides a clear checklist before optimization, and the priority ordering is explicit. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of tables for quick reference, and explicit cross-references to related skills (m01-ownership, m07-concurrency, domain-*). The 'Trace Up/Down' pattern provides clear navigation to related content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 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 |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 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.