align-lab-plugin

Align MCP plugins to the homelab canonical spec with a documented plan.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jmagar/plugin-templates --skill align-lab-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: align-lab-plugin
Source: https://github.com/jmagar/plugin-templates/tree/main/skills/align-lab-plugin
Command: npx skills add https://github.com/jmagar/plugin-templates --skill align-lab-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns an existing MCP plugin to the homelab canonical spec, fixing drift and aligning manifests, Docker/CI, and runtime across surfaces.

Core Features & Use Cases

  • Reconciles manifests and version sync to canonical sources.
  • Aligns environment contracts and runtime assets with the canonical templates.
  • Converts review findings into concrete alignment plans and actionable tasks across ten surfaces.

Quick Start

Align my plugin to the latest canonical spec by providing a review report or a list of drifted files.

Frequently Asked Questions about align-lab-plugin

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

FAQPage Schema
How do I align an MCP plugin to a canonical spec?

To align an MCP plugin to a canonical spec, you provide a review report or drifted files to generate an actionable plan reconciling manifests, Docker, CI, and runtime across ten surfaces.

What surfaces are covered when reconciling MCP plugin drift?

Reconciling MCP plugin drift targets ten surfaces: manifests, version sync, environment contracts, Dockerfile, docker-compose, entrypoint, Justfile, hooks, CI, live tests, and README/CLAUDE/commands.

Can I convert a Docker plugin review report into an implementation plan?

Yes, you can convert a review report into an implementation plan by binding drift findings to concrete alignment tasks and verifications across Dockerfile, docker-compose, and CI configurations.

Does aligning MCP plugins require updating environment contracts and hooks?

Yes, aligning MCP plugins requires updating environment contracts and hooks to match canonical templates, enforcing targets across runtime assets, entrypoint, Justfile, and CI.

Why do I need to sync manifests and CI files when upgrading an MCP plugin?

Syncing manifests and CI files fixes configuration drift against canonical sources, ensuring Docker, entrypoint, and live tests meet current homelab standards during plugin upgrades.