plugin-tests

Validate Claude Code plugin structure and integrity with static analysis tests.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/tyroneross/build-loop --skill plugin-tests-tyroneross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-tests
Source: https://github.com/tyroneross/build-loop/tree/main/skills/plugin-tests
Command: npx skills add https://github.com/tyroneross/build-loop --skill plugin-tests-tyroneross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of inconsistent plugin functionality in Claude Code and related platforms by providing a static-analysis test suite for plugins.

Core Features & Use Cases

  • Static Analysis: Performs a variety of checks on plugins including namesake collision detection, manifest verification, and MCP registration validation.
  • Automated Testing: Triggers tests with specific commands and runs automatically during critical workflow phases.
  • Use Case: Before pushing a new version of a plugin, use this Skill to verify that it meets all the required standards and has not introduced any new issues.

Quick Start

From the plugin repo root, run the plugin tests by executing: python3 scripts/test_skill_resolution.py

Frequently Asked Questions about plugin-tests

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

FAQPage Schema
How do I validate Claude Code plugin structure before deployment?

To validate Claude Code plugin structure, run a static-analysis test suite that checks manifest accuracy, namesake collisions, MCP registration, and trigger-phrase coverage. This ensures plugin compatibility and resolves metadata issues before pushing a new version.

What causes namesake collisions in Claude Code plugins?

Namesake collisions occur when multiple plugins share identical identifiers or trigger phrases within Claude Code. Static-analysis testing detects these conflicts by verifying manifest metadata and trigger-phrase coverage to prevent inconsistent plugin functionality.

How do I run automated tests on my Claude Code plugin?

Run automated tests on your Claude Code plugin by executing `python3 scripts/test_skill_resolution.py` from the plugin repository root. This triggers static-analysis checks for manifest verification, MCP registration validation, and trigger-phrase coverage.

Does static analysis check MCP registration for Claude Code plugins?

Yes, static analysis checks MCP registration as part of its validation suite for Claude Code plugins. It verifies manifest accuracy, namesake collisions, trigger-phrase coverage, and MCP registration to ensure full plugin compliance before deployment.

Why does my Claude Code plugin fail build automation checks?

Claude Code plugin build automation checks fail due to manifest inaccuracies, namesake collisions, missing MCP registration, or insufficient trigger-phrase coverage. Static-analysis testing identifies these specific metadata issues so they can be resolved before deployment.

Do I need Python to test Claude Code plugin compliance?

Yes, you need Python 3 to test Claude Code plugin compliance. The static-analysis test suite is executed by running `python3 scripts/test_skill_resolution.py` from the plugin repository root to validate manifest integrity and metadata standards.