infra-status
Skill2 starsChanged 27 days agoMITView on GitHub
Read-only health check: runs every step's check across the whole manifest and reports what is green, which step is the first red, and which skill fixes it. Changes nothing. Use when the question is where infra stands rather than a request to change it.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- hasansezertasan/infra-skillsword for word, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 1
- hasansezertasan/infra-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- infra-addSkill
- infra-importSkill
- infra-pruneSkill
- infra-setupSkill
- infraSkill
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 28
Keep this entry point read-only.
- Distinctive: line 32
Use the report contract in the shared runbook.
- Distinctive: line 36
Use this skill when the user asks for current infrastructure status without 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
<!--
AI-RULEZ :: GENERATED FILE — DO NOT EDIT
Content-Hash: blake3:fca82bd7ad6ee79306f280de29852bed13dcc9e5f9a2258668b4bb2b17e281c7
Source-Hash: blake3:68a46b64e70180566a5d1ebf9d0d4a9e0e15ab0076377348ec74a1267ef0ecb1
Schema-Version: v1
-->infra-status
Workflow
Route the health check through the shared status runbook:
../infra/references/status.md. It loads
the Config block from the root README.md, and stops with an "unsupported" message when a
legacy .infra-copilot/ directory or .claude/infra-copilot.local.md
file is still present.
That reference owns the scan, safety classification, reporting rules, and validation.
Guardrails
Keep this entry point read-only. Follow the shared runbook's actor and mutation rules.
Validation
Use the report contract in the shared runbook; do not define another result model here.
Example
Use this skill when the user asks for current infrastructure status without 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.