from groundwork36
Validate Groundwork plugin installation, report errors and warnings, and suggest (or offer) automated fixes for common plugin issues.
Performs a health check of the Groundwork Claude Code plugin by running validator scripts, collecting issues, and presenting actionable results. It identifies missing frontmatter, YAML formatting problems, permission issues, non-standard fields, and other common packaging mistakes, and maps each to a specific remediation.
Invoke this skill when installing, upgrading, or debugging the Groundwork plugin or any Claude plugin that follows the same structure. Use it before publishing to verify packaging, or after errors appear during plugin load to produce a prioritized list of fixes.
Useful for agents that can run repository scripts and suggest file edits (Claude Code, Codex-like agents).
Groundwork plugin health check command that validates YAML frontmatter, file references, and naming conventions in a Groundwork plugin installation. The SKILL.md body was null/empty in the database — the actual content lives in a commands/ markdown file and a lib/ JS validation script. No bundled scripts were present for execution. The validation logic itself is solid (checks frontmatter fields, naming, permissions), but the skill was ingested without its main content body.
The skill's SKILL.md body was null in the database, meaning the content crawl missed or failed to store it. The actual validation logic (validate-plugin.js) is reasonable — uses local fs module, no network calls, no destructive operations. However, this is really a command/agent within the Groundwork ecosystem rather than a standalone skill. Its usefulness is narrow: only helpful to Groundwork plugin developers running Claude Code. The architecture score reflects poor separation — it was ingested as a skill but is structured as a command with a separate JS library file.
