agentleFS
Sign inStart free
xtermjsxtermjs/xterm.js/.agents/skills/benchmark/SKILL.md

benchmark

Skill21k starsChanged 7 months agoMITView on GitHub

Run and author benchmark tests in xterm.js. Use when editing benchmark files, working in `*.benchmark.ts`, or when asked how to run the full benchmark suite, a single benchmark file, or a single benchmark case.

95 other projects use a version of this.

Trending

Quiet since June.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 4 mentionsMar 2026: 4 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the xtermjs/xterm.js repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about xtermjs/xterm.js

The biggest 5 of 45 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 45

Talked about on GitHub, Stack Overflow, Hacker News and Bluesky (45 times).

On GitHub · 23

18 more on GitHub

On Stack Overflow · 16

11 more on Stack Overflow

On Bluesky · 1

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
  • Other versions95 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 95

    1. garrytan/gstack★ 141ksame name
    2. dragonflydb/dragonfly★ 32ksame name
    3. udecode/plate★ 17ksame name
    4. Z3Prover/z3★ 13ksame name
    5. androidx/androidx★ 6.1ksame name
    6. samchon/typia★ 6ksame name
    7. PaddlePaddle/FastDeploy★ 3.7ksame name
    8. zalando/skipper★ 3.3ksame name
    9. samchon/nestia★ 2.2ksame name
    10. DenchHQ/DenchClaw★ 1.7ksame name

    85 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use -t to get the path, then:

    line 15
  2. Distinctive:

    When writing benchmark instructions:

    line 20
  3. Very specific:

    Use RuntimeCase to measure pure runtime in ms.

    line 22
  4. Very specific:

    Use ThroughputRuntimeCase when measuring throughput in MB/s.

    line 23
  5. Very specific:

    Keep NODE_PATH=./out (handled by the npm script).

    line 28

“Common” is measured: kept by at least 6 in 10 of the 81 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 Run Instructions

Running Benchmarks

  • Full suite: npm run benchmark
  • Single benchmark file:
    • Tree: npm run benchmark -- -t out-test/benchmark/Event.benchmark.js
    • Run file: npm run benchmark -- -s "out-test/benchmark/Event.benchmark.js" out-test/benchmark/Event.benchmark.js
  • Single context/case:
    • Use -t to get the path, then:
    • npm run benchmark -- -s "<path>" out-test/benchmark/Event.benchmark.js

Benchmark Case Selection

When writing benchmark instructions:

  • Use RuntimeCase to measure pure runtime in ms.
  • Use ThroughputRuntimeCase when measuring throughput in MB/s.

Notes

  • Benchmarks run from built JS in out-test/benchmark/*.benchmark.js.
  • Keep NODE_PATH=./out (handled by the npm script).

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.

Check your setup, free