What is plugin-verification for?

It provides layered checks for Claude extensions and plugins across hooks, skills, sub-agents, teams, manifest, structure, runtime loading, and CI parity to ensure reliable releases.

Which verification levels are included?

Component-level checks (hooks/skills/sub-agents/teams), manifest JSON + schema checks, directory/file layout checks, CLI load/visibility tests, and Docker parity with CI.

How do I run the checks?

Run the full suite with scripts/verify-all.sh, or run level-specific scripts like verify-manifest.sh, verify-structure.sh, verify-load.sh, and verify-ci.sh to target individual areas.

plugin-verification

Scanned

npx machina-cli add skill yu-iskw/google-cloud-observability-plugin/plugin-verification --openclaw

Files (1)

SKILL.md

1.9 KB

Plugin Verification

Run layered verification for extension components and plugin packaging before CI and release.

Validation Levels

Component-level verification (hooks, skills, sub-agents, teams).
Manifest JSON + schema checks.
Directory and file layout checks.
CLI load and visibility checks.
Docker smoke-test parity with CI.

Progressive Disclosure

Validation level model: references/validation-levels.md
Troubleshooting guide: references/common-issues.md
CLI command reference: references/cli-commands.md
CI/CD alignment: references/ci-integration.md
Hook verification guidance: references/verify-hooks.md
Skill verification guidance: references/verify-skills.md
Sub-agent verification guidance: references/verify-subagents.md
Team verification guidance: references/verify-teams.md
Level 2 script: scripts/verify-manifest.sh
Level 3 script: scripts/verify-structure.sh
Level 4 script: scripts/verify-load.sh
Level 5 script: scripts/verify-ci.sh
All levels: scripts/verify-all.sh
Checklist: assets/checklists/verification-checklist.md
Mistake guide: assets/checklists/common-mistakes.md

Related Skills

Umbrella guide: ../implement-claude-extensions/SKILL.md
Hooks implementation: ../implement-hooks/SKILL.md
Agent Skills implementation: ../implement-agent-skills/SKILL.md
Sub-Agent implementation: ../implement-sub-agents/SKILL.md
Agent Team implementation: ../implement-agent-teams/SKILL.md
Plugin packaging: ../implement-plugin/SKILL.md

Sources

Source

git clone https://github.com/yu-iskw/google-cloud-observability-plugin/blob/main/.claude/skills/plugin-verification/SKILL.md

View on GitHub

Overview

Plugin Verification runs layered checks to validate Claude extensions and plugin packaging before CI and release. It covers hooks, skills, sub-agents, teams, manifests, structure, runtime loading, and CI parity, with clear guidance and scripts to enforce quality.

How This Skill Works

It orchestrates five verification levels: component-level checks for hooks, skills, sub-agents, and teams; manifest JSON and schema validation; directory and file layout checks; CLI load/visibility verification; and Docker parity with CI. Each level maps to dedicated scripts (verify-manifest.sh, verify-structure.sh, verify-load.sh, verify-ci.sh, verify-all.sh) and reference guides to troubleshoot issues.

When to Use It

Before releasing a Claude extension or plugin, run the full verification suite to ensure all levels pass.
After making changes to hooks, skills, sub-agents, teams, or manifest to catch regressions early.
When packaging plugins for distribution to guarantee correct structure and loading behavior.
When updating CLI load or visibility logic to confirm runtime behavior remains correct.
To ensure Docker parity with CI by running verification in local or containerized environments.

Quick Start

Step 1: Prepare your environment with the repository tools and scripts.
Step 2: Run the verification suite (e.g., scripts/verify-all.sh) to perform all checks.
Step 3: Review the results, fix issues per guidance, and re-run until all levels pass.

Best Practices

Run the full verification (verify-all.sh) before every release or major merge.
Keep manifest.json and its schema up to date and validated by the manifest checks.
Use level-specific scripts (verify-manifest.sh, verify-structure.sh, verify-load.sh, verify-ci.sh) during development.
Run Docker parity checks in CI and locally to align runtime behavior with CI results.
Consult the progressive-disclosure references for troubleshooting and guidance.

Example Use Cases

Running scripts/verify-all.sh to catch cross-cutting issues before a release.
Using verify-manifest.sh to validate the manifest JSON against its schema after changes.
Running verify-structure.sh following a refactor to ensure proper directory layout.
Executing verify-load.sh to confirm CLI visibility and runtime loading in a local test environment.
Executing verify-ci.sh in a Docker container to ensure CI parity with local runs.

Frequently Asked Questions

Add this skill to your agents