Health check
A cross-device synced catalog for Claude and Codex skills, agents, and workflows.
npx -y skills add ada-ggf25/AI-Tools --skill health-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Periodic Codex repo health check orchestrator. Runs CI status, AGENTS.md staleness audit, documentation accuracy audit, and Obsidian Vault sync if present, pausing for approval between steps and producing one consolidated report. Global and project-agnostic. Trigger when the user says "health check", "health-check", "repo health", "check repo health", "repo maintenance", "run a health check", "audit the repo", "check everything", "periodic maintenance", or "check if everything is up to date". SKIP when the user only wants one specific audit.
SKILL.md
2.7 KB, as published. Nobody here has run it
Repo Health Check
Run the maintenance sequence a Codex-supported repo needs: CI health, Codex instruction docs, user-facing docs, and knowledge base sync.
Sequence:
diagnose-ci -> audit-agent-docs -> audit-docs -> obsidian-vault-sync if a vault
exists.
Operating Principles
- Orchestrate, do not reimplement delegated skills.
- CI health comes first.
- Pause after each step and let the user skip any step.
- Accumulate one consolidated final report.
- Do not apply fixes automatically; each delegated skill owns its own approval gate.
Procedure
0. Orient
- Confirm the cwd is the intended repo root.
- Detect vault: check for
<repo>/.obsidian-vault/. - Show the planned sequence and let the user drop steps.
1. CI Health
- If GitHub Actions exists and
ghis available, check recent run status. - If failing, invoke
diagnose-cito fetch logs, classify, and propose fixes. - If
ghis unavailable, note the gap and continue.
2. Codex Instruction Docs
- Invoke
audit-agent-docsto scoreAGENTS.mdandAGENTS.override.mdfiles for staleness and coverage gaps. - Carry its findings into the consolidated report.
3. Project Documentation
- Invoke
audit-docsfor user-facing and developer-facing docs. - Carry its findings into the consolidated report.
4. Obsidian Vault
- If a vault exists, invoke
obsidian-vault-syncwith full scope unless the user narrows it. - If no vault exists, record "Skipped - no vault detected".
5. Consolidate
Return a table like:
Area | Status | Findings
CI | Clean | 0 failing jobs
AGENTS.md audit | Issues | N stale, M missing, P orphaned
Docs audit | Issues | N high, M medium, P low
Vault sync | Clean | 0 findings
Then list next actions that still need user approval. Offer to save the report to
.codex/health-check-<date>.md only after approval.
Guardrails
- Never fabricate findings; use only delegated skill output and observed local state.
- Do not silently skip unavailable skills; say what is missing.
- Do not auto-apply fixes from delegated steps.
- Keep the final report concise and actionable.