agentleFS
MacroMan5MacroMan5/autotrain-yolo/.claude/skills/benchmark/SKILL.md

benchmark

Skill8 starsChanged 8 months agoMITView on GitHub

Profile YOLO model inference speed, FPS, and size across image sizes and export formats.

98 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-clean, ios-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 8 projects that use this

  • +1 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 84 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides a model path, use it directly.

    line 14
  2. Distinctive:

    If not provided, look for the current best model:

    line 15
  3. Very specific:

    Check experiments/summary.md for the latest best model path

    line 16
  4. Very specific:

    Search experiments/*/weights/best.pt for the most recent

    line 17
  5. Very specific:

    Default: [320, 640, 1280].

    line 22
  6. Distinctive:

    If no latency requirement is specified, note the speed/accuracy tradeoff (larger imgsz = better accuracy, slower inference)

    line 82
  7. Distinctive:

    If all sizes exceed the constraint, say so and suggest smaller model variants (n < s < m)

    line 83
  8. Very specific:

    Do not export the model to other formats unless the user asks.

    line 97
  9. Very specific:

    If training-plan.md has no deployment constraints, skip the constraint check and just report the numbers.

    line 98
  10. Distinctive:

    Keep output factual. Report what the numbers show, suggest next steps if relevant.

    line 99
  11. Distinctive:

    If the model file does not exist, stop and tell the user.

    line 100

“Common” is measured: kept by at least 6 in 10 of the 84 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Benchmark

Profile a YOLO model's inference performance across image sizes and devices.

Inputs

Model Path

  1. If the user provides a model path, use it directly.
  2. If not provided, look for the current best model:
    • Check experiments/summary.md for the latest best model path
    • Search experiments/*/weights/best.pt for the most recent
    • Fall back to asking the user

Image Sizes

Default: [320, 640, 1280]. The user can override this list.

Device

Detect available devices. Run on GPU (0) if available, CPU (cpu) always. If both exist, benchmark both and compare.

Procedure

  1. Read training-plan.md — check the "Deployment target" and "Secondary Goals" sections for latency/size constraints.
  2. Locate the model using the lookup order above. Confirm the path exists before proceeding.
  3. Run benchmarks — for each image size and each available device, run:
from ultralytics import YOLO
import torch

model = YOLO(path)

# Check GPU availability
gpu_available = torch.cuda.is_available()
devices = ["cpu"]
if gpu_available:
    devices.insert(0, 0)  # GPU first

for device in devices:
    for imgsz in image_sizes:
        results = model.benchmark(imgsz=imgsz, half=False, device=device)

model.benchmark() handles warm-up internally. Do not add manual warm-up runs.

  1. Collect results — from each benchmark call, extract:
    • Inference time (ms)
    • FPS (frames per second)
    • Model size (MB)
    • Format tested
  2. Report — print a summary table:
## Benchmark Results: <model_name>

### GPU (NVIDIA <name>) / CPU

| Format   | imgsz | Inference (ms) | FPS    | Size (MB) |
|----------|-------|----------------|--------|-----------|
| PyTorch  | 320   | ...            | ...    | ...       |
| PyTorch  | 640   | ...            | ...    | ...       |
| PyTorch  | 1280  | ...            | ...    | ...       |
  1. Analyze against deployment constraints — if training-plan.md specifies:
    • A latency target (e.g., "< 10ms"): flag any configuration that exceeds it
    • A model size limit: flag if the model exceeds it
    • A target device: highlight the relevant device results
  2. Recommend optimal imgsz — based on the results:
    • Identify the largest imgsz that meets latency requirements
    • If no latency requirement is specified, note the speed/accuracy tradeoff (larger imgsz = better accuracy, slower inference)
    • If all sizes exceed the constraint, say so and suggest smaller model variants (n < s < m)

Output Format

Print results directly to the conversation. Do not write to a file unless the user asks.

Structure:

  1. Model info (path, parameter count, variant)
  2. Results table(s) — one per device
  3. Deployment check — pass/fail against training-plan.md constraints
  4. Recommendation — optimal imgsz and format for the stated deployment target

Important

  • Do not export the model to other formats unless the user asks. model.benchmark() tests the PyTorch format by default.
  • If training-plan.md has no deployment constraints, skip the constraint check and just report the numbers.
  • Keep output factual. Report what the numbers show, suggest next steps if relevant.
  • If the model file does not exist, stop and tell the user. Do not train a model.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.