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
- TsukiNi22/skillstheir own version, first seen Nov 16, 2026
- TsukiNi22/ai-utilstheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- akshaypimprikar/pragmatheir own version, first seen Nov 11, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- accso/ai-context-mcptheir own version, first seen Nov 8, 2026
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-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
Saqlain-811Skillios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
seek888Skillpair-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
ShreyRaviSkilllanding-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
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
seek888Skillopen-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
Other versions98 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 98
- garrytan/gstack★ 142ksame name
- dragonflydb/dragonfly★ 32ksame name
- xtermjs/xterm.js★ 21ksame name
- udecode/plate★ 17ksame name
- Z3Prover/z3★ 13ksame name
- androidx/androidx★ 6.1ksame name
- samchon/typia★ 6ksame name
- PaddlePaddle/FastDeploy★ 3.7ksame name
- zalando/skipper★ 3.3ksame name
- samchon/nestia★ 2.2ksame name
88 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- active-learningSkill
- analyze-resultsSkill
- annotateSkill
- auto-experimentSkill
- compare-modelsSkill
- cvat-deploySkill
- cvat-pullSkill
- cvat-pushSkill
- explain-resultsSkill
- monitor-trainingSkill
- review-annotationsSkill
- review-datasetSkill
- setup-projectSkill
- training-loopSkill
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
- Distinctive: line 14
If the user provides a model path, use it directly.
- Distinctive: line 15
If not provided, look for the current best model:
- Very specific: line 16
Check experiments/summary.md for the latest best model path
- Very specific: line 17
Search experiments/*/weights/best.pt for the most recent
- Very specific: line 22
Default: [320, 640, 1280].
- Distinctive: line 82
If no latency requirement is specified, note the speed/accuracy tradeoff (larger imgsz = better accuracy, slower inference)
- Distinctive: line 83
If all sizes exceed the constraint, say so and suggest smaller model variants (n < s < m)
- Very specific: line 97
Do not export the model to other formats unless the user asks.
- Very specific: line 98
If training-plan.md has no deployment constraints, skip the constraint check and just report the numbers.
- Distinctive: line 99
Keep output factual. Report what the numbers show, suggest next steps if relevant.
- Distinctive: line 100
If the model file does not exist, stop and tell the user.
“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.
Files
Benchmark
Profile a YOLO model's inference performance across image sizes and devices.
Inputs
Model Path
- If the user provides a model path, use it directly.
- If not provided, look for the current best model:
- Check
experiments/summary.mdfor the latest best model path - Search
experiments/*/weights/best.ptfor the most recent - Fall back to asking the user
- Check
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
- Read
training-plan.md— check the "Deployment target" and "Secondary Goals" sections for latency/size constraints. - Locate the model using the lookup order above. Confirm the path exists before proceeding.
- 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.
- Collect results — from each benchmark call, extract:
- Inference time (ms)
- FPS (frames per second)
- Model size (MB)
- Format tested
- 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 | ... | ... | ... |- Analyze against deployment constraints — if
training-plan.mdspecifies:- 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
- 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:
- Model info (path, parameter count, variant)
- Results table(s) — one per device
- Deployment check — pass/fail against
training-plan.mdconstraints - 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.mdhas 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.
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
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.

