Agent skill

Repro

by vaadin in vaadin/web-components

Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.

No licenceAuto-check passedTesting & QA

Install Repro

skills CLI
$ npx skills add vaadin/web-components --skill repro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vaadin/web-components repro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vaadin/web-components.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/repro .claude/skills/repro && rm -rf skills-src

Use ~/.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/

Facts

Skill name
repro
GitHub stars
582
Token cost
~1.3k tokens
SKILL.md length
607 words
Files
6 (incl. references, assets)
Skills in repo
2
Repo updated
First seen
Licence
None found

At a glance

Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.

  • Works in 7 steps: Setup (once per session) → Understand the bug → Build the reproduction → …
  • Tasks that involve Design systems
  • SKILL.md covers Phase 0 — Setup (once per…, Phase 1 — Understand the bug, Phase 2 — Build the reproduction and Phase 3 — Run and reproduce, plus 4 more sections
  • Calls git, gh and npx

What it does

Repro is an agent skill from vaadin/web-components. Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components. Builds a minimal dev-page reproduction, confirms the bug in a running browser with playwright-cli, points at the likely root cause, pushes a shareable repro/<issue branch, and (after confirmation) posts a verification-pending summary comment on the issue.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `assets/summary-template.md`, `references/issue-analysis.md` and `references/reproduce.md`).

It sits in Testing & QA, covering Design systems, Root cause analysis and Browser testing. It works with Playwright, GitHub and Git. The repository describes itself as: A set of high-quality standards based web components for enterprise web applications. Part of Vaadin 20+.

When your agent uses it

  • Tasks that involve Design systems
  • Tasks that involve Root cause analysis
  • Tasks that involve Browser testing

Example prompts

  • “/repro”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(yarn:*), Bash(playwright-cli:*), Bash(npx:*), Bash(git:*), Bash(curl:*), Bash(lsof:*), Bash(kill:*)

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Setup (once per session)
  2. Understand the bug
  3. Build the reproduction
  4. Run and reproduce
  5. Report
  6. Locate the root cause
  7. Decide the disposition (always ask)

What it can do on your machine

Read from SKILL.md and the folder at commit 1ce9d4d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash(gh:*)
    • Bash(yarn:*)
    • Bash(playwright-cli:*)
    • Bash(npx:*)
    • Bash(git:*)

    …and 3 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh, 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

Repro loads about 1.3k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 607 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.3k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 607 words (~1,258 tokens).

“You are a tester reproducing a Vaadin web component bug. Input $0 is a GitHub issue URL in vaadin/web-components. Work the phases in order. Never claim a bug is reproduced until you have seen it in a running browser.”

— opening of SKILL.md by vaadin
name
repro
allowed-tools
Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(yarn:*), Bash(playwright-cli:*), Bash(npx:*), Bash(git:*), Bash(curl:*), Bash(lsof:*), Bash(kill:*)
argument-hint
<issue-url>
disable-model-invocation
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 5 other files (references, assets) in .claude/skills/repro of vaadin/web-components.

  • SKILL.md
  • assets/summary-template.md
  • references/issue-analysis.md
  • references/reproduce.md
  • references/share.md
  • references/verify.md

Open the folder on GitHubat commit 1ce9d4d

Compare with similar skills

Repro 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.

Repro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repro this skillvaadin/web-components582—~1.3kAutomated safety check: PassNone
Reprovaadin/flow-components129—~1.3kAutomated safety check: PassNone
Handsontable Performance Testinghandsontable/handsontable22k—~3.4kAutomated safety check: PassCustom licence
UI QA SweepLanternOps/breeze132—~3kAutomated safety check: NotesAGPL-3.0
PR Screenshotsbradygaster/squad3.3k—~1.1kAutomated safety check: PassMIT
Fix Failing Playwright Specappsmithorg/appsmith41k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • 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.

    129 GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Handsontable Performance Testing

    handsontable/handsontable

    Guide to Handsontable's performance-tests package: Playwright scenarios measured through CDP traces and compared against golden baselines taken from the develop branch.

    22k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed
  • UI QA Sweep

    LanternOps/breeze

    Broad regression QA of the Breeze RMM web UI via Playwright — exercising everyday MSP workflows and setup tasks like a human QA tester, logging functional PASS/FAIL plus UI/UX observations, and…

    132 GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check: notes
  • PR Screenshots

    bradygaster/squad

    Capture Playwright screenshots and embed them in GitHub PR descriptions

    3.3k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Fix Failing Playwright Spec

    appsmithorg/appsmith

    Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.

    41k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright Component Testing

    mellowagain/gitarena

    Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime.

    115 GitHub starsUsed in 1 repo~2.6k tokens
    Testing & QAAuto-check passed

More from vaadin/web-components

  • Stable Release Notes

    vaadin/web-components

    Prepare GitHub release notes for a beta or stable web-components release.

    582 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Repro

What does Repro do?

Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components. Repro is an agent skill from vaadin/web-components. Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.

When should I use Repro?

Repro fits situations like: tasks that involve Design systems; tasks that involve Root cause analysis; tasks that involve Browser testing.

How do I install Repro in Claude Code?

Run `npx skills add vaadin/web-components --skill repro -a claude-code`. Or copy the skill folder (.claude/skills/repro in vaadin/web-components) into .claude/skills/repro in your project. Claude Code loads it when a task matches its description.

How do I install Repro in Codex?

Run `npx skills add vaadin/web-components --skill repro -a codex`. Or copy the skill folder (.claude/skills/repro in vaadin/web-components) into .agents/skills/repro in your project. Codex loads it when a task matches its description.

Can I use Repro 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 vaadin/web-components --skill repro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repro, .gemini/skills/repro, .github/skills/repro and .opencode/skills/repro in your project.

What does Repro need to run?

Going by SKILL.md and its folder, Repro needs the command-line tools its instructions call (git, gh, npx and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(yarn:*), Bash(playwright-cli:*), Bash(npx:*), Bash(git:*), Bash(curl:*), Bash(lsof:*), Bash(kill:*).

Does Repro access the network?

SKILL.md contains no URLs. Its commands use git, gh, npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Repro 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 Repro use?

No licence was found for Repro or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Repro use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.

What are the alternatives to Repro?

Skills that share tags, products or a category with Repro: Repro (vaadin/flow-components, 129 stars), Handsontable Performance Testing (handsontable/handsontable, 22k stars), UI QA Sweep (LanternOps/breeze, 132 stars) and PR Screenshots (bradygaster/squad, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repro?

vaadin (a GitHub organization) maintains it in vaadin/web-components, which has 582 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: vaadin/web-components on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.