Repro
vaadin/web-components
Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.
Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.
Install Repro
$ npx skills add vaadin/flow-components --skill repro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vaadin/flow-components repro --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/vaadin/flow-components.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/repro .claude/skills/repro && 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 "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .claude/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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/vaadin/flow-components/tree/main/.claude/skills/reproType 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 vaadin/flow-components --skill repro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vaadin/flow-components repro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vaadin/flow-components.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/repro .agents/skills/repro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .agents/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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 vaadin/flow-components --skill repro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vaadin/flow-components repro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vaadin/flow-components.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/repro .cursor/skills/repro && 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 "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .cursor/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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/vaadin/flow-components.git --path .claude/skills/repro--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 vaadin/flow-components --skill repro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vaadin/flow-components repro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vaadin/flow-components.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/repro .gemini/skills/repro && 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 "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .gemini/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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 vaadin/flow-components reproInstalls 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 vaadin/flow-components --skill repro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vaadin/flow-components.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/repro .github/skills/repro && 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 "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .github/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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 vaadin/flow-components --skill repro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vaadin/flow-components repro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vaadin/flow-components.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/repro .opencode/skills/repro && 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 "repro" agent skill from https://github.com/vaadin/flow-components/tree/main/.claude/skills/repro into .opencode/skills/repro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repro", 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
repro- GitHub stars
- 129
- Token cost
- ~1.3k tokens
- SKILL.md length
- 630 words
- Files
- 6 (incl. references, assets)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- None found
At a glance
Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.
- Works in 7 steps: Setup (once per session) → Understand the bug → Build the reproduction → …
- Tasks that involve Root cause analysis
- 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/flow-components. Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow. Builds a minimal integration-test View, 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 Root cause analysis, Browser testing and Integration testing. It works with Playwright, GitHub, Java and Git. The repository describes itself as: Java counterpart of Vaadin Web Components.
When your agent uses it
- Tasks that involve Root cause analysis
- Tasks that involve Browser testing
- Tasks that involve Integration testing
Example prompts
- “/repro”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(mvn:*), 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.
- Setup (once per session)
- Understand the bug
- Build the reproduction
- Run and reproduce
- Report
- Locate the root cause
- Decide the disposition (always ask)
What it can do on your machine
Read from SKILL.md and the folder at commit 2268d3e. 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:
ReadWriteEditGlobGrepBash(gh:*)Bash(mvn:*)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:
gitghnpxnpm
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 ~7.3k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 630 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 630 words (~1,327 tokens).
“You are a tester reproducing a Vaadin Flow component bug. Input $0 is a GitHub issue URL in vaadin/flow-components or vaadin/flow. Work the phases in order. Never claim a bug is reproduced until you have seen it in a running…”
- name
- repro
- allowed-tools
- Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(mvn:*), Bash(playwright-cli:*), Bash(npx:*), Bash(git:*), Bash(curl:*), Bash(lsof:*), Bash(kill:*)
- argument-hint
- <issue-url>
- disable-model-invocation
- true
Files
SKILL.md and 5 other files (references, assets) in .claude/skills/repro of vaadin/flow-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 2268d3e
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repro this skillvaadin/flow-components | 129 | — | ~1.3k | Automated safety check: Pass | None | |
| Reprovaadin/web-components | 582 | — | ~1.3k | Automated safety check: Pass | None | |
| E2E Testinglangflow-ai/langflow | 156k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Fix Failing Playwright Specappsmithorg/appsmith | 41k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Playwright Component Testingmellowagain/gitarena | 115 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Playwright Rollmicrosoft/playwright-dotnet | 3k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
E2E Testing
langflow-ai/langflow
Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.
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.
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.
- Official
Playwright Roll
microsoft/playwright-dotnet
Roll Playwright .NET to a new version
Agent Integration Replay
Comfy-Org/ComfyUI_frontend
Replay recorded agent conversations as Playwright tests against the real chat panel and canvas.
More from vaadin/flow-components
Signal Rules
vaadin/flow-components
Read these rules whenever you add, modify, or review bind methods (e.g.
Cherry Pick
vaadin/flow-components
Cherry-pick a PR to a target version branch. An agent skill from vaadin/flow-components.
Related
Works with
Categories
Questions about Repro
What does Repro do?
Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow. Repro is an agent skill from 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.
When should I use Repro?
Repro fits situations like: tasks that involve Root cause analysis; tasks that involve Browser testing; tasks that involve Integration testing.
How do I install Repro in Claude Code?
Run `npx skills add vaadin/flow-components --skill repro -a claude-code`. Or copy the skill folder (.claude/skills/repro in vaadin/flow-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/flow-components --skill repro -a codex`. Or copy the skill folder (.claude/skills/repro in vaadin/flow-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/flow-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(mvn:*), 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 5.3k 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 5.9k 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/web-components, 582 stars), E2E Testing (langflow-ai/langflow, 156k stars), Fix Failing Playwright Spec (appsmithorg/appsmith, 41k stars) and Playwright Component Testing (mellowagain/gitarena, 115 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/flow-components, which has 129 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: vaadin/flow-components on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.