system-check
Skill8 starsChanged 35 days agoMITView on GitHub
Verify the Claude Agent Pack installation and current project scaffolding in one pass. Runs check-readiness.sh and check-updates.sh, reports all failures and outdated items together, and offers to run remediation. Use before starting work on a project or when something seems off after a git pull. Trigger this when someone says: check my setup, is everything installed, something is not working, verify the pack, is my installation up to date, check if Claude Agent Pack is ready, run a health check. Do NOT use to initialize a new project — use /setup-project instead.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- wrg32786/aigent-ostheir own version, first seen Oct 13, 2026
- aribajahan/claude-skillstheir own version, first seen Sep 23, 2026
- Lucas-Grilli/context-os-plugintheir own version, first seen Aug 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- wrg32786/aigent-os★ 26same name
- Lucas-Grilli/context-os-plugin★ 1same name
- aribajahan/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- backlogSkill
- conventionsSkill
- debugSkill
- devops-azureSkill
- devops-githubSkill
- devopsSkill
- hotfixSkill
- implementSkill
- interview-meSkill
- lint-agentsSkill
- memory-auditSkill
- memory-querySkill
- obsidian-briefSkill
- obsidian-captureSkill
- obsidian-dailySkill
- obsidian-recapSkill
- obsidian-searchSkill
- obsidianSkill
- onboardSkill
- pack-reviewSkill
- planSkill
- refactorSkill
- repo-mapSkill
- review-prSkill
- scaffoldSkill
- setup-projectSkill
- smellSkill
- spec-intakeSkill
- whatSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Verify the Claude Agent Pack installation and current project scaffolding in a single pass.
- Distinctive: line 16
Run readiness and update checks, passing the current project directory to readiness:
- Distinctive: line 60
All readiness failures with their remediation commands
- Distinctive: line 61
All outdated or missing agents/skills
- Distinctive: line 62
If everything is clean, confirm the pack and project are fully set up and ready
- Very specific: line 68
Pack directory not found: If scripts/check-readiness.sh cannot be located, ask the user where they cloned the agent pack before doing …
- Very specific: line 70
Multiple project-scaffolding failures: If CLAUDE.md, docs/CONVENTIONS.md, docs/MEMORY-WRITING.md, and memory/ subdirectories are all …
- Distinctive: line 72
User declines remediation: If the user does not want to run remediation, report the failures clearly and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
System Check
Verify the Claude Agent Pack installation and current project scaffolding in a single pass.
1. Locate the pack
Find the pack directory by locating scripts/check-readiness.sh. The pack is typically cloned to a fixed location (e.g., ~/claude-agent-pack). If you cannot locate it, ask the user where they cloned the pack.
2. Run both checks
Run readiness and update checks, passing the current project directory to readiness:
bash <pack-dir>/scripts/check-readiness.sh <project-dir>
bash <pack-dir>/scripts/check-updates.shCapture the full output of both.
3. Interpret readiness results
For each [!!] failure in check-readiness output:
| Failure | Remediation |
~/.claude directory | Claude Code is not installed — direct the user to install it |
| Agents not installed | bash <pack-dir>/install.sh |
| Skills not installed | bash <pack-dir>/install.sh |
CLAUDE.md missing | bash <pack-dir>/scripts/setup-project.sh <project-dir> |
docs/CONVENTIONS.md missing | bash <pack-dir>/scripts/setup-project.sh <project-dir> |
docs/MEMORY-WRITING.md missing | bash <pack-dir>/scripts/setup-project.sh <project-dir> |
memory/<subdir>/ missing | bash <pack-dir>/scripts/setup-project.sh <project-dir> |
Group multiple project-scaffolding failures under a single setup-project.sh invocation.
4. Interpret update results
The update check reports three states for each agent and skill:
| State | Meaning |
[ok] | Installed and matches the pack source |
[!!] (outdated) | Installed but differs from the pack source |
[--] (not installed) | Not installed at all |
List any outdated or missing agents and skills. If anything is outdated or missing, the fix is:
bash <pack-dir>/install.sh5. Report and offer to remediate
Present a unified summary:
- All readiness failures with their remediation commands
- All outdated or missing agents/skills
- If everything is clean, confirm the pack and project are fully set up and ready
Offer to run the remediation commands on the user's behalf if they confirm.
Gotchas
- Pack directory not found: If
scripts/check-readiness.shcannot be located, ask the user where they cloned the agent pack before doing anything else. Do not guess at common locations — the path varies by machine. - check-readiness.sh fails with a permission error: The script must be executable. If it fails with
Permission denied, ask the user to runchmod +x <pack-dir>/scripts/*.shand retry. - Multiple project-scaffolding failures: If
CLAUDE.md,docs/CONVENTIONS.md,docs/MEMORY-WRITING.md, andmemory/subdirectories are all missing, a singlesetup-project.shcall fixes all of them. Group these under one remediation command rather than listing them separately. - Outdated agents/skills vs. missing agents/skills: Both are fixed by
install.sh, but the distinction matters for the user's awareness. Report them separately so the user understands whether this is a fresh install or an update. - User declines remediation: If the user does not want to run remediation, report the failures clearly and stop. Do not attempt workarounds or partial fixes.
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.

