agentleFS
Sign inStart free
NoizefieldNoizefield/audio-plugin-coder/.agents/skills/test/SKILL.md

test

Skill334 starsChanged 34 days agoMITView on GitHub

Run the APC testing and validation workflow for an audio plugin after implementation, including testing gates and results.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, execute the complete workflow from:

    line 16

“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test - Plugin Testing & Validation

Trigger: /test [PluginName] Phase: Testing (can run after Implementation) Primary Skill: .claude\skills\skill_testing\SKILL.md

EXECUTION

When invoked, execute the complete workflow from: .claude\skills\skill_testing\SKILL.md

WORKFLOW GATES

See .claude\workflows\test.md for:

  • Prerequisites (requires completed Implementation phase)
  • Test procedures
  • Validation criteria

PARAMETERS

  • PluginName - Name of existing plugin to test

OUTPUT

  • Test results
  • Validation report
  • Updates $PluginPath/status.json with test status

TEST TYPES

  • Build validation
  • Parameter range testing
  • UI/DSP integration verification
  • DAW compatibility check

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free