skill_test

Launch the APC testing harness and execute plugin-specific QA suites.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/joshband/LocusQ --skill skill-test-joshband
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill_test
Source: https://github.com/joshband/LocusQ/tree/main/.codex/skills/test
Command: npx skills add https://github.com/joshband/LocusQ --skill skill-test-joshband

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the validation of plugins by routing APC plugin validation through a structured testing workflow, reducing manual setup and ensuring repeatable QA outcomes.

Core Features & Use Cases

  • Harness-driven testing: launches the QA harness and runs the plugin-specific validation suite.
  • Workflow gates and reporting: validates prerequisites, updates plugin status, and emits evidence artifacts.
  • Evidence and traceability: updates plugins/[Name]/TestEvidence with build summaries and validation trends, and stores results in plugins/[Name]/status.json.
  • Flexible plugin targeting: accepts a PluginName parameter to select which plugin to test.

Quick Start

Invoke the skill with a PluginName to start the harness-driven testing workflow for that plugin.

Frequently Asked Questions about skill_test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate plugin validation through a testing harness?

Automate plugin validation by routing it through an APC testing harness that launches the QA suite, executes plugin-specific tests, and generates standardized evidence artifacts. You invoke the workflow with a PluginName parameter to target a specific plugin.

What evidence artifacts are generated by automated plugin QA testing?

Automated plugin QA testing generates suite_result.json and test-summary.md files. It also updates the plugins/[Name]/TestEvidence directory with build summaries and validation trends, while storing the overall execution state in plugins/[Name]/status.json.

Can I run automated harness-based testing for a specific plugin?

Yes, you can run harness-based testing for a specific plugin by providing the PluginName parameter. This flexible targeting mechanism selects which plugin undergoes the automated QA suite validation and subsequent status updates.

What is the purpose of status tracking in a plugin validation workflow?

Status tracking in a plugin validation workflow records prerequisites validation, execution progress, and final outcomes in status.json. This ensures repeatable QA outcomes by providing traceability and updating the plugin's current validation state.

Does automated plugin validation require any external dependencies?

No external dependencies are required to run the automated plugin validation workflow. The harness-driven testing process operates independently to validate prerequisites, execute the QA suite, and emit evidence artifacts within a standardized directory structure.

When should I use a harness-driven testing workflow for plugin validation?

Use harness-driven testing for plugin validation when you need repeatable QA outcomes, automated evidence generation, and structured status updates. It is designed for plugins that require standardized, automated harness-based testing rather than manual setup.