SkillAgentSearch skills...

m10-performance

CRITICAL: Use for performance optimization. Triggers: performance, optimization, benchmark, profiling, flamegraph, criterion, slow, fast, allocation, cache, SIMD, make it faster, 性能优化, 基准测试

Install / Use

npx skills add actionbook/rust-skills --skill m10-performance

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of m10-performance

m10-performance scores 87/100 on our quality scale, 2174th of 4,698 Development & Engineering skills we index (top 47%).

Its SKILL.md is 4.0 KB long, well organised into 12 sections with 3 code examples: a solid amount of guidance for an agent.

With 1,479 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so m10-performance is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

m10-performance compared with similar skills

All 4 of these similar skills score higher than m10-performance; compare them before choosing.

SkillScoreStarsUpdatedFormat
m10-performance (this skill)by actionbook871.5k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install m10-performance?
Run npx skills add actionbook/rust-skills --skill m10-performance. The install tabs above show the steps for each supported agent.
Which AI agents does m10-performance work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is m10-performance safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is m10-performance still maintained?
The repository was last updated about 3 months ago, so m10-performance is actively maintained.

name: m10-performance description: "CRITICAL: Use for performance optimization. Triggers: performance, optimization, benchmark, profiling, flamegraph, criterion, slow, fast, allocation, cache, SIMD, make it faster, 性能优化, 基准测试" user-invocable: false

Performance Optimization

Layer 2: Design Choices

Core Question

What's the bottleneck, and is optimization worth it?

Before optimizing:

  • Have you measured? (Don't guess)
  • What's the acceptable performance?
  • Will optimization add complexity?

Performance Decision → Implementation

| Goal | Design Choice | Implementation | |------|---------------|----------------| | Reduce allocations | Pre-allocate, reuse | with_capacity, object pools | | Improve cache | Contiguous data | Vec, SmallVec | | Parallelize | Data parallelism | rayon, threads | | Avoid copies | Zero-copy | References, Cow<T> | | Reduce indirection | Inline data | smallvec, arrays |


Thinking Prompt

Before optimizing:

  1. Have you measured?

    • Profile first → flamegraph, perf
    • Benchmark → criterion, cargo bench
    • Identify actual hotspots
  2. What's the priority?

    • Algorithm (10x-1000x improvement)
    • Data structure (2x-10x)
    • Allocation (2x-5x)
    • Cache (1.5x-3x)
  3. What's the trade-off?

    • Complexity vs speed
    • Memory vs CPU
    • Latency vs throughput

Trace Up ↑

To domain constraints (Layer 3):

"How fast does this need to be?"
    ↑ Ask: What's the performance SLA?
    ↑ Check: domain-* (latency requirements)
    ↑ Check: Business requirements (acceptable response time)

| Question | Trace To | Ask | |----------|----------|-----| | Latency requirements | domain-* | What's acceptable response time? | | Throughput needs | domain-* | How many requests per second? | | Memory constraints | domain-* | What's the memory budget? |


Trace Down ↓

To implementation (Layer 1):

"Need to reduce allocations"
    ↓ m01-ownership: Use references, avoid clone
    ↓ m02-resource: Pre-allocate with_capacity

"Need to parallelize"
    ↓ m07-concurrency: Choose rayon or threads
    ↓ m07-concurrency: Consider async for I/O-bound

"Need cache efficiency"
    ↓ Data layout: Prefer Vec over HashMap when possible
    ↓ Access patterns: Sequential over random access

Quick Reference

| Tool | Purpose | |------|---------| | cargo bench | Micro-benchmarks | | criterion | Statistical benchmarks | | perf / flamegraph | CPU profiling | | heaptrack | Allocation tracking | | valgrind / cachegrind | Cache analysis |

Optimization Priority

1. Algorithm choice     (10x - 1000x)
2. Data structure       (2x - 10x)
3. Allocation reduction (2x - 5x)
4. Cache optimization   (1.5x - 3x)
5. SIMD/Parallelism     (2x - 8x)

Common Techniques

| Technique | When | How | |-----------|------|-----| | Pre-allocation | Known size | Vec::with_capacity(n) | | Avoid cloning | Hot paths | Use references or Cow<T> | | Batch operations | Many small ops | Collect then process | | SmallVec | Usually small | smallvec::SmallVec<[T; N]> | | Inline buffers | Fixed-size data | Arrays over Vec |


Common Mistakes

| Mistake | Why Wrong | Better | |---------|-----------|--------| | Optimize without profiling | Wrong target | Profile first | | Benchmark in debug mode | Meaningless | Always --release | | Use LinkedList | Cache unfriendly | Vec or VecDeque | | Hidden .clone() | Unnecessary allocs | Use references | | Premature optimization | Wasted effort | Make it work first |


Anti-Patterns

| Anti-Pattern | Why Bad | Better | |--------------|---------|--------| | Clone to avoid lifetimes | Performance cost | Proper ownership | | Box everything | Indirection cost | Stack when possible | | HashMap for small sets | Overhead | Vec with linear search | | String concat in loop | O(n^2) | String::with_capacity or format! |


Related Skills

| When | See | |------|-----| | Reducing clones | m01-ownership | | Concurrency options | m07-concurrency | | Smart pointer choice | m02-resource | | Domain requirements | domain-* |

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryDevelopment
Updated2mo ago
Forks114

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium