What do the manifest validators check?

They verify schema safety, required fields, and directory structure conformance per the manifest rules.

Where are the manifest templates located?

Templates are in assets/templates (e.g., minimal-plugin.json, complete-plugin.json, plugin-with-components.json) and project references provide guidance.

How do I test runtime load?

Run the runtime load check script (test-plugin-load.sh) or load the plugin with --plugin-dir to ensure correct wiring and runtime behavior.

implement-plugin

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

Files (1)

SKILL.md

1.7 KB

Implement Plugin

Implement plugin-level packaging, manifest wiring, structure checks, runtime load checks, and distribution guidance.

Workflow

Define plugin metadata and distribution scope.
Update .claude-plugin/plugin.json and component path mappings.
Validate manifest and directory structure.
Verify runtime load with --plugin-dir and optional install flow.
Run CI-parity smoke tests before distribution.

Progressive Disclosure

Manifest schema and field rules: references/manifest-schema.md
Directory conventions and anti-patterns: references/directory-structure.md
Test strategy across local/CI: references/testing-strategies.md
Distribution checklist and channels: references/plugin-distribution.md
Scope and install context guidance: references/plugin-scopes.md
Manifest validator: scripts/validate-manifest.sh
Layout validator: scripts/check-structure.sh
Runtime load check: scripts/test-plugin-load.sh
Minimal manifest template: assets/templates/minimal-plugin.json
Complete manifest template: assets/templates/complete-plugin.json
Manifest with components template: assets/templates/plugin-with-components.json

Component Skills

Hooks: ../implement-hooks/SKILL.md
Agent Skills: ../implement-agent-skills/SKILL.md
Sub-Agents: ../implement-sub-agents/SKILL.md
Agent Teams: ../implement-agent-teams/SKILL.md
Umbrella selection guide: ../implement-claude-extensions/SKILL.md

Sources

Source

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

View on GitHub

Overview

Implement Plugin focuses on packaging Claude Code plugins with schema-safe manifests, canonical layout, and release-ready validation. It guides you through metadata, manifest wiring, and structure checks to ensure reliable distribution. This skill covers running validators, runtime load checks, and CI-ready smoke tests before release.

How This Skill Works

Define plugin metadata and distribution scope, then update .claude-plugin/plugin.json and component path mappings. Validate the manifest and directory structure, verify runtime load with --plugin-dir (and optional install flow), and run CI-parity smoke tests prior to distribution. You can leverage scripts like scripts/validate-manifest.sh, scripts/check-structure.sh, and scripts/test-plugin-load.sh along with manifest templates (minimal, complete, and with components).

When to Use It

You are packaging a new Claude Code plugin and need a clean manifest and canonical layout
You are updating an existing plugin's manifest, component mappings, or distribution scope
You want to validate the plugin's directory structure against established conventions
You need to verify runtime load using --plugin-dir before releasing
You are preparing CI smoke tests and distribution checks for channels

Quick Start

Step 1: Define plugin metadata and distribution scope
Step 2: Update .claude-plugin/plugin.json and component path mappings
Step 3: Run validators and runtime-load checks (validate-manifest.sh, check-structure.sh, test-plugin-load.sh) and review CI-smoke results

Best Practices

Match manifest fields and layout to the manifest-schema.md guidance to ensure schema safety
Use the provided templates (minimal, complete, with components) to standardize structure
Run both manifest and layout validators locally and in CI to catch issues early
Maintain accurate component path mappings and perform runtime load checks with --plugin-dir
Follow the distribution checklist and scope guidance to align with release processes

Example Use Cases

Packaging a new Claude Code plugin with a minimal manifest and validating structure
Adding a component and updating plugin.json to wire the new module
Running validate-manifest.sh and check-structure.sh as part of PR checks
Performing runtime load tests via test-plugin-load.sh before publishing
Completing a CI-parity smoke test suite to ensure release-quality plugin distribution

Frequently Asked Questions

Add this skill to your agents