Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests).
Install Add Plugin Tool
$ npx skills add genex-games/genex-desktop --skill add-plugin-tool -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install genex-games/genex-desktop add-plugin-tool --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/genex-games/genex-desktop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-plugin-tool .claude/skills/add-plugin-tool && 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 "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .claude/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-toolType 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 genex-games/genex-desktop --skill add-plugin-tool -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install genex-games/genex-desktop add-plugin-tool --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genex-games/genex-desktop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/add-plugin-tool .agents/skills/add-plugin-tool && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .agents/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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 genex-games/genex-desktop --skill add-plugin-tool -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install genex-games/genex-desktop add-plugin-tool --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genex-games/genex-desktop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/add-plugin-tool .cursor/skills/add-plugin-tool && 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 "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .cursor/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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/genex-games/genex-desktop.git --path .agents/skills/add-plugin-tool--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 genex-games/genex-desktop --skill add-plugin-tool -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install genex-games/genex-desktop add-plugin-tool --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genex-games/genex-desktop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/add-plugin-tool .gemini/skills/add-plugin-tool && 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 "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .gemini/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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 genex-games/genex-desktop add-plugin-toolInstalls 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 genex-games/genex-desktop --skill add-plugin-tool -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/genex-games/genex-desktop.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/add-plugin-tool .github/skills/add-plugin-tool && 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 "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .github/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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 genex-games/genex-desktop --skill add-plugin-tool -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install genex-games/genex-desktop add-plugin-tool --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/genex-games/genex-desktop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/add-plugin-tool .opencode/skills/add-plugin-tool && 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 "add-plugin-tool" agent skill from https://github.com/genex-games/genex-desktop/tree/dev/.agents/skills/add-plugin-tool into .opencode/skills/add-plugin-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-plugin-tool", 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
add-plugin-tool- GitHub stars
- 390
- Token cost
- ~841 tokens
- SKILL.md length
- 348 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests).
- Works in 5 steps: Manifest - src/plugins//plugin.json,… → Backend - the tool(name, args, ctx)… → Skill text - if the agent needs… → …
- Bundled plugins in src/plugins/
- SKILL.md covers Files and Tests (red first)
- Calls npm
What it does
Add Plugin Tool is an agent skill from genex-games/genex-desktop. Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests). Use for bundled plugins in src/plugins/ or when changing how plugin tools are validated or dispatched.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA. The repository describes itself as: Desktop app for game dev with AI. macOS and Linux, Windows soon. The licence is MIT.
When your agent uses it
- Bundled plugins in src/plugins/
- Changing how plugin tools are validated
Example prompts
- “/add-plugin-tool”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Manifest - src/plugins//plugin.json, tools[]
- Backend - the tool(name, args, ctx) handler returned by activate() in the
- Skill text - if the agent needs guidance, update the plugin's skills[] entry so it
- Host changes (only when changing the tool system itself): validation in
- Docs - docs/plugins.md for contract changes; docs/product/assets-plugins.md for
What it can do on your machine
Read from SKILL.md and the folder at commit 235086f. 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:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Add Plugin Tool loads about 841 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 348 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
The full file from genex-games/genex-desktop at commit 235086f, republished under its MIT licence (© genex-games). 348 words, ~841 tokens.
Download SKILL.mdSave it as
.claude/skills/add-plugin-tool/SKILL.md (or your agent's skills folder).- name
- add-plugin-tool
- description
- Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests). Use for bundled plugins in src/plugins/* or when changing how plugin tools are validated or dispatched.
Add a plugin tool
A plugin tool is declared in the plugin's plugin.json, handled by its isolated backend
process and exposed to every engine as <plugin-id>__<tool-name>. Contract reference:
docs/plugins.md (manifest table, API versions, consent model) and src/plugin-sdk/index.d.ts.
Files
- Manifest -
src/plugins/<id>/plugin.json,tools[]:{name, description, parameters:{type:"object", properties, required}}.name: lowercase id, unique within the plugin.- Parameters are scalar (
string|number|boolean) under API 1 and 2;objectonly withapiVersion: 3. Anything else is rejected byvalidateManifest(src/substrate/plugins/manifest.ts). - Add
confirmation(1-300 chars, API 2+) when the tool spends money, publishes or otherwise needs the user's consent before each run. - The description is model-facing: say when to use it, what it costs and what not to do.
- Backend - the
tool(name, args, ctx)handler returned byactivate()in the plugin's backend (src/plugins/example/backend.mjsis the minimal pattern;src/plugins/genex/backend.ts,src/plugins/blender/backend.tsare real ones).- Treat
argsas untrusted: check types and ranges again, reject unknown operations. - Reach host services only through
ctx.host(...); a backend cannot read credentials, open URLs or touch files outside the bound project and its own storage. - Return plain JSON. Throw an
Errorwith an actionable message on refusal.
- Treat
- Skill text - if the agent needs guidance, update the plugin's
skills[]entry so it names the tool by its full<id>__<tool>name. - Host changes (only when changing the tool system itself): validation in
src/substrate/plugins/manifest.ts, dispatch/consent insrc/substrate/plugins/registry.ts, the call, its consent wait and its durable record insrc/main/core/plugin-tools.ts(PluginToolService), and engine exposure insrc/main/core/delegation.ts(searchpluginTools: the tool list handed to a session and the dispatch of its calls). - Docs -
docs/plugins.mdfor contract changes;docs/product/assets-plugins.mdfor anything a user sees.
Tests (red first)
- Registry behaviour against a copied package:
tests/conformance/plugins.test.ts(fixture()copiessrc/plugins/exampleinto a temp root) - declared vs undeclared fields, wrong types, disabled plugin fails closed, cancelled call not retried. - Manifest rules:
validateManifestcases in the same file. - Consent:
tests/conformance/plugin-consent.test.tswhenconfirmationis involved. - Genex/Blender tools:
tests/conformance/genex-plugin-cli.test.ts,tests/conformance/blender.test.ts. - Package as a user would see it:
npm run plugin:doctor -- src/plugins/<id>.
npm test -- tests/conformance/plugins.test.ts tests/conformance/plugin-devkit.test.ts
npm run plugin:doctor -- src/plugins/exampleNever let a tool argument choose a program, URL or path outside the project; those come from reviewed plugin code.
© genex-games, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/add-plugin-tool of genex-games/genex-desktop.
Open the folder on GitHubat commit 235086f
Compare with similar skills
Add Plugin Tool 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 |
|---|---|---|---|---|---|---|
| Add Plugin Tool this skillgenex-games/genex-desktop | 390 | — | ~841 | Automated safety check: Pass | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 31 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDfossasia/eventyay-interpretation | 1.6k | 28 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
fossasia/eventyay-interpretation
Test-driven development. An agent skill from fossasia/eventyay-interpretation.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
More from genex-games/genex-desktop
Add Event Type
genex-games/genex-desktop
Add a new persisted event (custom eventtype in the append-only log) or a transient UI event, with its producer, readers and tests.
Add Ipc Channel
genex-games/genex-desktop
Add or change a renderer-to-main IPC channel (a new window.studio call) end to end - main handler, preload, typed API, fixture classification and tests.
Harness Incident Fix
genex-games/genex-desktop
Fix a bug in the in-app harness loop (src/harness-seed/) test-first - write the incident row that reproduces it, see it fail, fix, then run the harness gate.
Run Area Tests
genex-games/genex-desktop
Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite.
Break
genex-games/genex-desktop
Renders a component you choose in every state and scenario on a temporary page and stress tests it.
Verify UI Via Dev Control
genex-games/genex-desktop
Verify renderer, IPC, preview or startup changes through owned studio:dev profiles, or hand off the real app for manual testing.
Related
Categories
Questions about Add Plugin Tool
What does Add Plugin Tool do?
Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests). Add Plugin Tool is an agent skill from genex-games/genex-desktop. Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests).
When should I use Add Plugin Tool?
Add Plugin Tool fits situations like: bundled plugins in src/plugins/; changing how plugin tools are validated.
How do I install Add Plugin Tool in Claude Code?
Run `npx skills add genex-games/genex-desktop --skill add-plugin-tool -a claude-code`. Or copy the skill folder (.agents/skills/add-plugin-tool in genex-games/genex-desktop) into .claude/skills/add-plugin-tool in your project. Claude Code loads it when a task matches its description.
How do I install Add Plugin Tool in Codex?
Run `npx skills add genex-games/genex-desktop --skill add-plugin-tool -a codex`. Or copy the skill folder (.agents/skills/add-plugin-tool in genex-games/genex-desktop) into .agents/skills/add-plugin-tool in your project. Codex loads it when a task matches its description.
Can I use Add Plugin Tool 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 genex-games/genex-desktop --skill add-plugin-tool -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-plugin-tool, .gemini/skills/add-plugin-tool, .github/skills/add-plugin-tool and .opencode/skills/add-plugin-tool in your project.
What does Add Plugin Tool need to run?
Going by SKILL.md and its folder, Add Plugin Tool needs the command-line tools its instructions call (npm).
Does Add Plugin Tool access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Add Plugin Tool 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 Add Plugin Tool use?
Add Plugin Tool is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Add Plugin Tool use?
About 841 tokens (SKILL.md is roughly 3.4k 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 Add Plugin Tool?
Skills that share tags, products or a category with Add Plugin Tool: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (fossasia/eventyay-interpretation, 1.6k stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Plugin Tool?
genex-games (a GitHub organization) maintains it in genex-games/genex-desktop, which has 390 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: genex-games/genex-desktop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.