Command execution timing — microsecond precision, statistical analysis, comparison. Zero barrier — use with x-cmd or shell built-in time command. Use for "timing", "benchmark", "performance", "profiling".
71
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Measure command execution time. From single-shot microsecond timing to multi-run statistical analysis.
# With x-cmd
x time <command> # Single microsecond timing
x time stress -c 100 <command> # 100-run statistics
x time cmp 'cmd1' 'cmd2' 'cmd3' # Compare commands
# Without x-cmd — use shell built-ins
time <command> # Basic timing
# For benchmarking, use a loop:
for i in $(seq 1 100); do
start=$(date +%s%N)
<command>
end=$(date +%s%N)
echo $(( end - start ))
donex time <cmd> — Single run, microsecond precisionx time getms <cmd> — Millisecond precisionx time stress -c N <cmd> — N runs with full statsx time stress -b N <cmd> — Auto-decide runs within budgetx time cmp 'c1' 'c2' — Compare multiple commands--csv CSV for programmatic analysis--tsv Tab-separated--yml YAMLStarting with the essentials. Will add:
81ff596
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.