skills.rest
Star1131
Star1131COMMUNITY
Explore all skills by this author →
GitHub

performance

Detect RTK CLI performance regressions in startup time, binary size, memory usage, regex handling, and token-saving behavior.

Updated Apr 8, 2026
Search Tags:#performance#memory#regression#benchmark#startup#binary-size#rtk
One-click install
npx skills add https://github.com/Star1131/smart_insole --skill performance-star1131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance
Source: https://github.com/Star1131/smart_insole/tree/main/.claude/skills/rtk-master/.claude/skills/performance
Command: npx skills add https://github.com/Star1131/smart_insole --skill performance-star1131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch and prevent performance regressions in RTK CLI workflows by turning startup latency, binary size, memory use, and token efficiency into measurable release criteria.

Core Features & Use Cases

  • Startup Benchmarking: Measure cold and warm command startup time before and after changes.
  • Binary and Memory Auditing: Check release build size and resident memory against strict limits.
  • Regression Investigation: Inspect regex compilation, dependency impact, and allocation hotspots when a change gets slower or heavier.
  • Use Case: A developer adds a new crate and wants to confirm the CLI still starts fast, stays small, and preserves token-saving behavior.

Quick Start

Use this skill to benchmark the change, compare it against the current RTK performance targets, and report any regressions clearly.

Frequently Asked Questions about performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect CLI performance regressions in startup time and binary size?▼

Detect CLI performance regressions by benchmarking cold and warm startup time, measuring binary size, and comparing before-after changes against strict release targets like sub-10ms startup and sub-5MB limits.

What is the best way to benchmark memory usage and token-saving behavior for a CLI?▼

Benchmark memory usage and token-saving behavior by auditing resident memory against sub-5MB limits and verifying at least 60% token savings before and after dependency additions or optimization reviews.

How do I investigate why my CLI startup latency increased after adding a dependency?▼

Investigate increased CLI startup latency by inspecting regex compilation, analyzing dependency impact, and identifying allocation hotspots to pinpoint the exact cause of the performance regression.

What are the strict performance targets for keeping a CLI fast and lean?▼

The strict performance targets for keeping a CLI fast and lean require sub-10ms startup time, sub-5MB binary and resident memory usage, and at least 60% token savings during repeatable benchmarking.

When should I run startup benchmarking and binary auditing during development?▼

Run startup benchmarking and binary auditing during release-sensitive changes, dependency additions, and optimization reviews to ensure repeatable benchmarking confirms no performance regressions were introduced.

Does the performance skill work without external benchmarking dependencies?▼

The performance skill operates without external dependencies, applying repeatable benchmarking and before-after comparison directly to release builds to verify strict startup, memory, and token-saving criteria.

Related Skills

Explore More Software Engineering Skills→
rtk-airtk-ai
75.3k

performance

Analyze and optimize RTK CLI startup time, binary size, and memory usage.

Official
Advanced
OutlineDrivenOutlineDriven
5

perf-profile

Identify performance hotspots using flamegraphs, allocation data, and latency profiles.

Official
Advanced
xrehpicxxrehpicx
4

test-tui

Validate Codex TUI startup, logging, and input-sequence behavior.

Community
Basic
nano-stepnano-step
3

rtk

Prefix shell commands with rtk to compress and filter command output.

Official
Intermediate