From fbc13b035bc05f675c8103f8f9214e1376408624 Mon Sep 17 00:00:00 2001 From: Matt Chana Date: Wed, 18 Feb 2026 12:41:21 +0900 Subject: [PATCH] Add manual plugin validation fallback when CLI validator is unavailable When running inside Cowork, `claude plugin validate` may not be available. This adds a manual verification checklist covering plugin.json structure, naming conventions, component directories, and expected file formats. Co-Authored-By: Claude Opus 4.6 --- .../skills/create-cowork-plugin/SKILL.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/cowork-plugin-management/skills/create-cowork-plugin/SKILL.md b/cowork-plugin-management/skills/create-cowork-plugin/SKILL.md index 6f60833..6db3b87 100644 --- a/cowork-plugin-management/skills/create-cowork-plugin/SKILL.md +++ b/cowork-plugin-management/skills/create-cowork-plugin/SKILL.md @@ -233,7 +233,14 @@ If the user says "whatever you think is best," provide specific recommendations 1. Summarize what was created — list each component and its purpose 2. Ask if the user wants any adjustments -3. Run `claude plugin validate `; fix any errors and warnings +3. Run `claude plugin validate ` to check the plugin structure. If this command is unavailable (e.g., when running inside Cowork), verify the structure manually: + - `.claude-plugin/plugin.json` exists and contains valid JSON with at least a `name` field + - The `name` field is kebab-case (lowercase letters, numbers, and hyphens only) + - Any component directories referenced by the plugin (`commands/`, `skills/`, `agents/`, `hooks/`) actually exist and contain files in the expected formats — `.md` for commands/skills/agents, `.json` for hooks + - Each skill subdirectory contains a `SKILL.md` + - Report what passed and what didn't, the same way the CLI validator would + + Fix any errors before proceeding. 4. Package as a `.plugin` file: ```bash