groundwork-check
Skill45 starsChanged 4 days agoMITView on GitHub
Validate the Groundwork plugin for common issues. Usage /groundwork:groundwork-check
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- build-unplannedSkill
- check-specs-alignmentSkill
- create-tasksSkill
- debugSkill
- design-architectureSkill
- design-it-twiceSkill
- design-productSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- finalize-taskSkill
- groundwork-helpSkill
- handoffSkill
- implement-taskSkill
- instrument-observabilitySkill
- just-do-itSkill
- just-do-it-swarmingSkill
- plan-taskSkill
- review-prSkill
- select-projectSkill
- setup-repoSkill
- shipSkill
- skillsSkill
- source-architecture-from-codeSkill
- source-product-specs-from-codeSkill
- source-ux-design-from-codeSkill
- split-architectureSkill
- split-specsSkill
- staged-rolloutSkill
- statuslineSkill
- swarm-debugSkill
- swarm-design-architectureSkill
- task-validation-loopSkill
- test-driven-developmentSkill
- understanding-feature-requestsSkill
- use-git-worktreeSkill
- using-groundworkSkill
- ux-designSkill
- validateSkill
- vertical-sliceSkill
- work-on-next-taskSkill
- work-onSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run the plugin validation script:
- Distinctive: line 45
If issues are found, offer to automatically fix simple issues:
- Distinctive: line 49
Ask user before making any changes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Groundwork Plugin Health Check
Validates the Groundwork plugin installation and reports any issues.
Workflow
Step 1: Run Validation Script
Run the plugin validation script:
node "${CLAUDE_PLUGIN_ROOT}/lib/validate-plugin.js"Step 2: Report Results
Present the validation results to the user:
- If all checks pass: Confirm plugin is healthy
- If errors found: List each error with file path and description
- If warnings found: List warnings as recommendations
Step 3: Suggest Fixes
For any issues found, suggest specific fixes:
| Issue Type | Suggested Fix |
| Missing frontmatter | Add --- delimited YAML at file start |
Literal \n in description | Use YAML block scalar (|) |
| Non-standard field | Remove field or document exception |
| allowed_tools | Change to allowed-tools (hyphen) |
| @ syntax | Use explicit file paths |
| Missing execute permission | Run chmod 755 on script |
Step 4: Offer to Fix
If issues are found, offer to automatically fix simple issues:
- Permissions can be fixed with chmod
- YAML key names can be updated
Ask user before making any changes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.