skills.rest
jmagar
jmagarCOMMUNITY
Explore all skills by this author →
GitHub

review-lab-plugin

Audit MCP plugins against the homelab canonical spec and generate findings reports.

Updated Aug 27, 2026
Search Tags:#reports#validation#audit#plugin#review#spec#canonical
One-click install
npx skills add https://github.com/jmagar/plugin-templates --skill review-lab-plugin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-lab-plugin
Source: https://github.com/jmagar/plugin-templates/tree/main/skills/review-lab-plugin
Command: npx skills add https://github.com/jmagar/plugin-templates --skill review-lab-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review an MCP plugin against the homelab canonical plugin spec to detect misalignments and drift.

Core Features & Use Cases

  • Conduct structured spec audits against target plugins and canonical manifests.
  • Generate detailed review reports highlighting correctness, structural drift, runtime contract drift, and any missing required files.
  • Provide remediation guidance and a justification workflow to align plugins with canonical standards.

Quick Start

Provide the path to the target plugin and run the review to generate a comprehensive alignment report.

Frequently Asked Questions about review-lab-plugin

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

FAQPage Schema
How do I audit an MCP plugin against a canonical spec?▼

To audit an MCP plugin against a canonical spec, provide the target plugin repository path and the canonical-spec reference. The review generates a detailed findings report cataloging correctness issues, structural drift, and documentation gaps.

What is spec drift in MCP plugins and how is it detected?▼

Spec drift in MCP plugins refers to misalignments in structure and runtime contracts compared to a canonical reference. It is detected by performing a structured spec audit that validates target plugin surfaces and manifests against defined standards.

Do I need access to the plugin repository to run a spec validation?▼

Yes, running a spec validation requires access to the target plugin repository and the canonical-spec reference. This access is necessary to validate the plugin against defined surfaces and manifests for misalignments.

What is included in a plugin spec review report?▼

A plugin spec review report includes detailed findings on correctness issues, structural drift, runtime contract drift, missing required files, and documentation gaps. It also provides remediation guidance to align plugins with canonical standards.

How do I fix alignment issues found during a plugin audit?▼

To fix alignment issues found during a plugin audit, follow the remediation guidance and justification workflow provided in the findings report. This process helps align target plugins with the homelab canonical spec standards.

Related Skills

Explore More Software Engineering Skills→
tacogipstacogips

design-doc

Organizes design specs and references into a canonical directory structure with templates.

Community
Basic
murphyjosephmurphyjoseph

claude-automation-recommender

Analyze codebases to identify automation opportunities for Claude Code workflows.

Community
Advanced
tyronerosstyroneross
1

plugin-tests

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

Community
Intermediate
gileckgileck

full-project-audit

Audit repository deviations from guidelines and architecture rules without code changes.

Community
Advanced