perftest
Skill383 starsChanged 40 days agoLicence not identifiedView on GitHub
Run Firefox performance tests locally or in CI. Use when the user asks how to run a perf test, needs the mach invocation for Raptor, Talos, MozPerftest, AWSY, or browsertime, wants to push perf tests to try, wants to run the tests belonging to an alert summary (`mach try perf --alert <id>`), or mentions `mach try perf`, `mach perftest`, `mach raptor`, or `mach talos-test`. Covers picking the right harness, finding a test's name, and the local-vs-CI tradeoff. Not for triaging or root-causing a Perfherder regression bug — confirming whether a regression is real, identifying the culprit patch, interpreting a PerfCompare result, or deciding backout vs fix-forward (use perf-regression-triage). Not for analyzing an existing Firefox profile (use profiler-analysis) or SpiderMonkey/JS engine benchmarking (use js-perf-investigation).
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions1 project uses a version of this.
Word for word · 1
- mozilla-firefox/firefox★ 14k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- js/AGENTS.mdAGENTS.md
- layout/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- js/CLAUDE.mdCLAUDE.md
- layout/CLAUDE.mdCLAUDE.md
- accessibility-frontend-reviewSkill
- android-new-moduleSkill
- androidSkill
- bug-filingSkill
- documentationSkill
- file-good-first-bugSkill
- find-reviewerSkill
- firefox-commitsSkill
- firefox-desktop-frontendSkill
- fluent-migrationSkill
- gecko-web-standard-implementationSkill
- js-perf-investigationSkill
- media-patch-reviewSkill
- mozlintSkill
- nimbus-prefsSkill
- perf-regression-triageSkill
- perftestSkill
- profiler-analysisSkill
- specmapSkill
- spec-traceSkill
- stack-reorganizeSkill
- stack-split-commitSkill
- stmoSkill
- webspec-indexSkill
- accessibility-frontend-reviewSkill
- android-new-moduleSkill
- androidSkill
- bug-filingSkill
- documentationSkill
- file-good-first-bugSkill
- find-reviewerSkill
- firefox-commitsSkill
- firefox-desktop-frontendSkill
- fluent-migrationSkill
- gecko-web-standard-implementationSkill
- js-perf-investigationSkill
- media-patch-reviewSkill
- mozlintSkill
- nimbus-prefsSkill
- perf-regression-triageSkill
- profiler-analysisSkill
- specmapSkill
- spec-traceSkill
- stack-reorganizeSkill
- stack-split-commitSkill
- stmoSkill
- webspec-indexSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

