OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Validates audio plugins through automated tests, pluginval, or manual DAW testing.
Install Plugin Testing
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-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/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plugin-testing .claude/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .claude/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-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 glittercowboy/plugin-freedom-system --skill plugin-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/plugin-testing .agents/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .agents/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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 glittercowboy/plugin-freedom-system --skill plugin-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/plugin-testing .cursor/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .cursor/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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/glittercowboy/plugin-freedom-system.git --path .claude/skills/plugin-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 glittercowboy/plugin-freedom-system --skill plugin-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/plugin-testing .gemini/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .gemini/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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 glittercowboy/plugin-freedom-system plugin-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 glittercowboy/plugin-freedom-system --skill plugin-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/plugin-testing .github/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .github/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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 glittercowboy/plugin-freedom-system --skill plugin-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 glittercowboy/plugin-freedom-system plugin-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/plugin-testing .opencode/skills/plugin-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 "plugin-testing" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-testing into .opencode/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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
plugin-testing- GitHub stars
- 216
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,200 words
- Files
- 9 (incl. references, assets)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Validates audio plugins through automated tests, pluginval, or manual DAW testing.
- Works in 4 steps: Detect Plugin and Mode Selection → Execute Test Mode → Failure Investigation (Option 1) → …
- MANUAL testing via /test command
- SKILL.md covers Workflow Overview, Phase 1: Detect Plugin and…, Phase 2: Execute Test Mode and Phase 3: Failure Investigation…, plus 5 more sections
- Calls git
What it does
Plugin Testing is an agent skill from glittercowboy/plugin-freedom-system. Validates audio plugins through automated tests, pluginval, or manual DAW testing. Use for MANUAL testing via /test command. Note - Automatic validation now built into workflow (validation-agent runs after each stage). This skill is for manual testing only, after bug fixes, or when user mentions test, validate, validation, pluginval, stability, automated tests, run tests, check plugin, or quality assurance.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files and assets (for example `assets/decision-menu-templates.md`, `assets/manual-testing-checklist.md` and `assets/report-templates.md`).
It sits in Testing & QA, covering QA and bug reports and Debugging. The repository describes itself as: AI-assisted JUCE plugin development system for MacOS by TÂCHES.
When your agent uses it
- MANUAL testing via /test command
- Automated tests
- Quality assurance
Example prompts
- “Use the plugin-testing skill to validate audio plugins through automated tests, pluginval, or manual DAW testing”
- “/plugin-testing”
Requirements
- Pre-approved tools (allowed-tools): Read, Bash, Task
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Detect Plugin and Mode Selection
- Execute Test Mode
- Failure Investigation (Option 1)
- Log Test Results and Checkpoint
What it can do on your machine
Read from SKILL.md and the folder at commit e965cdd. 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:
ReadBashTask
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Plugin Testing loads about 3.1k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 1,200 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Task
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 1,200 words (~3,099 tokens).
“Purpose: Catch crashes, parameter issues, and state bugs in 2 minutes with automated tests.”
- name
- plugin-testing
- allowed-tools
- Read, Bash, Task
Files
SKILL.md and 8 other files (references, assets) in .claude/skills/plugin-testing of glittercowboy/plugin-freedom-system.
- SKILL.md
- assets/decision-menu-templates.md
- assets/manual-testing-checklist.md
- assets/report-templates.md
- references/failure-investigation-guide.md
- references/manual-testing-guide.md
- references/pluginval-guide.md
- references/test-specifications.md
- references/troubleshooting.md
Open the folder on GitHubat commit e965cdd
Compare with similar skills
Plugin 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 |
|---|---|---|---|---|---|---|
| Plugin Testing this skillglittercowboy/plugin-freedom-system | 216 | — | ~3.1k | Automated safety check: Notes | None | |
| OpenWork Desktop CDP Driverdifferent-ai/openwork | 24k | — | ~465 | Automated safety check: Pass | Custom licence | |
| Structured Bug ReportsDonchitos/Claude-Code-Game-Studios | 26k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Pipensx Bug Report Triagei3sey/pipensx | 218 | — | ~1.5k | Automated safety check: Notes | GPL-3.0 | |
| Bug ReproducerAnastasiyaW/codex-claude-code-config | 154 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Dough Bug Fixingterryyin/lizard | 2.5k | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
Structured Bug Reports
Donchitos/Claude-Code-Game-Studios
Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.
Pipensx Bug Report Triage
i3sey/pipensx
Decodes QR-code bug report photos and screenshots from the pipensx app into a log, then triages crashes and update, download or install failures.
Bug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Dough Bug Fixing
terryyin/lizard
Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive…
Dogfood
RedWoodOG/Hermes-Desktop
Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports
More from glittercowboy/plugin-freedom-system
All 15 skills in this repoAesthetic Dreaming
glittercowboy/plugin-freedom-system
Create aesthetic templates without first creating a plugin - capture visual design concepts through adaptive questioning.
Deep Research
glittercowboy/plugin-freedom-system
Multi-agent parallel investigation for complex JUCE problems.
Plugin Ideation
glittercowboy/plugin-freedom-system
Adaptive brainstorming for plugin concepts and improvements when exploring ideas, not implementing.
Plugin Improve
glittercowboy/plugin-freedom-system
Fix bugs, add features to completed plugins. An agent skill from glittercowboy/plugin-freedom-system.
Plugin Lifecycle
glittercowboy/plugin-freedom-system
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
Plugin Packaging
glittercowboy/plugin-freedom-system
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
Related
Categories
Questions about Plugin Testing
What does Plugin Testing do?
Validates audio plugins through automated tests, pluginval, or manual DAW testing. Plugin Testing is an agent skill from glittercowboy/plugin-freedom-system. Validates audio plugins through automated tests, pluginval, or manual DAW testing.
When should I use Plugin Testing?
Plugin Testing fits situations like: MANUAL testing via /test command; automated tests; quality assurance.
How do I install Plugin Testing in Claude Code?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-testing -a claude-code`. Or copy the skill folder (.claude/skills/plugin-testing in glittercowboy/plugin-freedom-system) into .claude/skills/plugin-testing in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Testing in Codex?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-testing -a codex`. Or copy the skill folder (.claude/skills/plugin-testing in glittercowboy/plugin-freedom-system) into .agents/skills/plugin-testing in your project. Codex loads it when a task matches its description.
Can I use Plugin 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 glittercowboy/plugin-freedom-system --skill plugin-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/plugin-testing, .gemini/skills/plugin-testing, .github/skills/plugin-testing and .opencode/skills/plugin-testing in your project.
What does Plugin Testing need to run?
Going by SKILL.md and its folder, Plugin Testing needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Bash, Task.
Does Plugin Testing access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plugin Testing safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Plugin Testing use?
No licence was found for Plugin Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plugin Testing use?
About 3.1k tokens (SKILL.md is roughly 12k 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 7k tokens, read only when the agent opens those files.
What are the alternatives to Plugin Testing?
Skills that share tags, products or a category with Plugin Testing: OpenWork Desktop CDP Driver (different-ai/openwork, 24k stars), Structured Bug Reports (Donchitos/Claude-Code-Game-Studios, 26k stars), Pipensx Bug Report Triage (i3sey/pipensx, 218 stars) and Bug Reproducer (AnastasiyaW/codex-claude-code-config, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Testing?
glittercowboy (a GitHub user) maintains it in glittercowboy/plugin-freedom-system, which has 216 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on November 19, 2025.
Source: glittercowboy/plugin-freedom-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.