host-check
Skill0 starsChanged 3 months agoMITView on GitHub
Run every report-only script in the base layer and host profile (scripts/install-flatpaks.sh, install-gnome-extensions.sh, layer-packages.sh, tpm2-luks-unlock.sh, hosts/<slug>/quirks.sh) and summarize ok/missing across all of them. Use when the user asks for a general status sweep of the machine, "what's missing", or a health check that isn't specifically about updates.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- end-sessionSkill
- etc-driftSkill
- handoverSkill
- incidentSkill
- reset-triageSkill
- security-privacy-checkSkill
- update-checkSkill
- vendor-updateSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Run scripts/host-check.sh from the repo root and show its output as-is.
- Distinctive: line 20
After showing the output, for anything reported missing, point at the exact command the script already printed rather than improvising one …
≈ “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
Run scripts/host-check.sh from the repo root and show its output as-is.
It's read-only and freely agent-runnable — every script it wraps is already
guaranteed idempotent and side-effect-free by its own header comment, same
contract as install-flatpaks.sh. host-check.sh uses an explicit include
list, not a blind glob over scripts/*.sh — it deliberately skips
install-hooks.sh (mutates git config directly) and
build-bitwarden-polkit-policy.sh (builds a local RPM), since running those
would be a side effect disguised as a status check.
This is a different question from /update-check: host-check answers "is
X installed / present," update-check answers "is X out of date." They're
complementary, not overlapping — run both for a full picture.
After showing the output, for anything reported missing, point at the exact
command the script already printed rather than improvising one — same rule
as every report-only script in this repo. Some entries (like
tpm2-luks-unlock.sh's enrollment step) explicitly require an interactive
terminal and can't be run non-interactively; say so rather than attempting
it as a background command.
quirks.sh's two purely-/etc-write remediations (crash-forensics
baseline, fprintd crash-loop mitigation) are directly runnable via
hosts/thinkpad-e14-gen5/quirks.sh fix — by the agent or the user standalone,
same trust level as gpu-toggle.sh. Everything else it reports missing
(fingerprint reader, NVIDIA, xpadneo, the s2idle kargs escalation) stays
print-only since those need rpm-ostree/toolbox builds or a reboot.
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.