CtrlK
BlogDocsLog inGet started
Tessl Logo

time

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

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

time — skill0

Measure command execution time. From single-shot microsecond timing to multi-run statistical analysis.

Quick Start

# 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 ))
done

What's Available

  • x time <cmd> — Single run, microsecond precision
  • x time getms <cmd> — Millisecond precision
  • x time stress -c N <cmd> — N runs with full stats
  • x time stress -b N <cmd> — Auto-decide runs within budget
  • x time cmp 'c1' 'c2' — Compare multiple commands

Output Formats

  • --csv CSV for programmatic analysis
  • --tsv Tab-separated
  • --yml YAML

This skill0 grows

Starting with the essentials. Will add:

  • Benchmarking patterns
  • Statistical interpretation guide
  • Common performance anti-patterns

Related

Repository
x-cmd/x-cmd
Last updated
First committed

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.