Repro
vaadin/web-components
Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.
Guide to Handsontable's performance-tests package: Playwright scenarios measured through CDP traces and compared against golden baselines taken from the develop branch.
Install Handsontable Performance Testing
$ npx skills add handsontable/handsontable --skill performance-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install handsontable/handsontable performance-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/performance-testing .claude/skills/performance-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .claude/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add handsontable/handsontable --skill performance-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install handsontable/handsontable performance-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/performance-testing .agents/skills/performance-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .agents/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add handsontable/handsontable --skill performance-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install handsontable/handsontable performance-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/performance-testing .cursor/skills/performance-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .cursor/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/handsontable/handsontable.git --path .claude/skills/performance-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add handsontable/handsontable --skill performance-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install handsontable/handsontable performance-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/performance-testing .gemini/skills/performance-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .gemini/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install handsontable/handsontable performance-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add handsontable/handsontable --skill performance-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/performance-testing .github/skills/performance-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .github/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add handsontable/handsontable --skill performance-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install handsontable/handsontable performance-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/performance-testing .opencode/skills/performance-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/performance-testing into .opencode/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
performance-testing- GitHub stars
- 22k
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,325 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guide to Handsontable's performance-tests package: Playwright scenarios measured through CDP traces and compared against golden baselines taken from the develop branch.
- Works in 3 steps: scenario.config.mjs → fixture.html → Spec
- Adding a new performance scenario for a Handsontable feature
- SKILL.md covers Package structure, Adding a scenario, Existing scenarios and Run commands, plus 5 more sections
- Calls node, npx and npm
What it does
The performance-tests package measures rendering and interaction speed with Playwright and CDP traces. It is a standalone package outside the pnpm workspace, with its own package.json, node_modules and ESLint config. Each scenario traces one interaction, parses the trace into DevTools categories (scripting, rendering, painting and idle), and produces a markdown PR comment and an HTML report compared with a golden baseline from develop.
Adding a scenario means three files in the scenarios folder: a config module whose name equals the folder, a standalone fixture page that exposes the grid as window.__hot with automatic row and column sizing turned off, and a Playwright spec. The config's measurementVersion is bumped when the measured window or iteration count changes, because baselines only draw on goldens of the same version, while HARNESS_VERSION covers runner-wide changes. Playwright runs sequentially with one worker, a 5 minute timeout and Chromium only, and golden snapshots are fetched from GitHub Pages.
When your agent uses it
- Adding a new performance scenario for a Handsontable feature
- Debugging a performance test or its trace parsing
- Benchmarking filtering or sorting with hook timing
- Understanding the golden snapshot and CI comparison pipeline
Example prompts
- “Add a performance scenario that measures scrolling a large grid and explain the grid size in the config.”
- “Why did the median baseline restart after my change to the iteration count?”
- “Benchmark the column sorting feature with hook timing.”
Requirements
- A checkout of the Handsontable repository
- Playwright with Chromium
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- scenario.config.mjs
- fixture.html
- Spec
What it can do on your machine
Read from SKILL.md and the folder at commit fff66b1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nodenpxnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Handsontable Performance Testing loads about 3.4k tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 1,325 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,325 words (~3,434 tokens).
“performance-tests/ measures rendering and interaction performance with Playwright + CDP traces. It is a standalone package outside the pnpm workspace (own package.json, node_modules, ESLint config). Each scenario traces one interaction, parses the trace into DevTools categories (scripting, rendering, painting, idle)…”
- name
- performance-testing
- path
- performance-tests/**
Files
Just SKILL.md in .claude/skills/performance-testing of handsontable/handsontable.
Open the folder on GitHubat commit fff66b1
Compare with similar skills
Handsontable Performance Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Handsontable Performance Testing this skillhandsontable/handsontable | 22k | — | ~3.4k | Automated safety check: Pass | Custom licence | |
| Reprovaadin/web-components | 582 | — | ~1.3k | Automated safety check: Pass | None | |
| PR Screenshotsbradygaster/squad | 3.3k | — | ~1.1k | Automated safety check: Pass | MIT | |
| LangBot Environment Setuplangbot-app/LangBot | 18k | — | ~496 | Automated safety check: Notes | Apache-2.0 | |
| Playwright Best Practicessanity-io/sanity | 6.4k | 7 repos | ~6.4k | Automated safety check: Pass | MIT | |
| Reprovaadin/flow-components | 129 | — | ~1.3k | Automated safety check: Pass | None |
Similar skills
PR Screenshots
bradygaster/squad
Capture Playwright screenshots and embed them in GitHub PR descriptions
LangBot Environment Setup
langbot-app/LangBot
Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.
- Official
Playwright Best Practices
sanity-io/sanity
A skill your agent uses when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling…
Repro
vaadin/flow-components
Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.
Plugin Installer
IgorWarzocha/Opencode-Workflows
Find, install, and configure OpenCode plugins from the catalog or community.
More from handsontable/handsontable
All 31 skills in this repoHandsontable Playwright E2E Tests
handsontable/handsontable
Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.
Handsontable Angular Wrapper Development
handsontable/handsontable
Guides changes to the @handsontable/angular-wrapper package: the HotTableComponent lifecycle, NgZone performance handling, settings services and the ng-packagr build.
BrowserStack Live Testing
handsontable/handsontable
Opens a live BrowserStack session on a real Android, iOS or desktop browser for a local or public URL, tunneling localhost through Cloudflare when needed.
Handsontable Changelog Entry
handsontable/handsontable
Decides whether a code change needs a changelog entry and creates the JSON file in .changelogs with the right type, framework and user-facing title.
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Handsontable Coordinate Systems
handsontable/handsontable
Explains Handsontable's physical, visual and renderable row and column coordinate spaces and how to convert between them with IndexMapper, for debugging misplaced rows or columns.
Related
Works with
Categories
Questions about Handsontable Performance Testing
What does Handsontable Performance Testing do?
Guide to Handsontable's performance-tests package: Playwright scenarios measured through CDP traces and compared against golden baselines taken from the develop branch. The performance-tests package measures rendering and interaction speed with Playwright and CDP traces.json, node_modules and ESLint config.
When should I use Handsontable Performance Testing?
Handsontable Performance Testing fits situations like: adding a new performance scenario for a Handsontable feature; debugging a performance test or its trace parsing; benchmarking filtering or sorting with hook timing; understanding the golden snapshot and CI comparison pipeline.
How do I install Handsontable Performance Testing in Claude Code?
Run `npx skills add handsontable/handsontable --skill performance-testing -a claude-code`. Or copy the skill folder (.claude/skills/performance-testing in handsontable/handsontable) into .claude/skills/performance-testing in your project. Claude Code loads it when a task matches its description.
How do I install Handsontable Performance Testing in Codex?
Run `npx skills add handsontable/handsontable --skill performance-testing -a codex`. Or copy the skill folder (.claude/skills/performance-testing in handsontable/handsontable) into .agents/skills/performance-testing in your project. Codex loads it when a task matches its description.
Can I use Handsontable Performance Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add handsontable/handsontable --skill performance-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performance-testing, .gemini/skills/performance-testing, .github/skills/performance-testing and .opencode/skills/performance-testing in your project.
What does Handsontable Performance Testing need to run?
Going by SKILL.md and its folder, Handsontable Performance Testing needs the command-line tools its instructions call (node, npx and npm). Our summary lists: A checkout of the Handsontable repository; Playwright with Chromium.
Does Handsontable Performance Testing access the network?
SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Handsontable Performance Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Handsontable Performance Testing use?
Handsontable Performance Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Handsontable Performance Testing use?
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Handsontable Performance Testing?
Skills that share tags, products or a category with Handsontable Performance Testing: Repro (vaadin/web-components, 582 stars), PR Screenshots (bradygaster/squad, 3.3k stars), LangBot Environment Setup (langbot-app/LangBot, 18k stars) and Playwright Best Practices (sanity-io/sanity, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Handsontable Performance Testing?
handsontable (a GitHub organization) maintains it in handsontable/handsontable, which has 22,060 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 8, 2026.
Source: handsontable/handsontable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.