How do I install the Full Infra Health Check skill?

Run npx skillmds@latest add knuckles-team/full-infra-health-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Full Infra Health Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Full Infra Health Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Full Infra Health Check free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Full Infra Health Check?

Knuckles-Team (@knuckles-team) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Full Infra Health Check by knuckles-team

Name: Full Infra Health Check
Author: Knuckles-Team

Full Infra Health Check

Run every health-relevant atomic skill this catalog owns — hardware profile, current resource utilization, compose configuration drift, and TLS expiry — in parallel across the fleet, then consolidate the findings into one formatted report. Use when an operator wants a single point-in-time snapshot combining every owned infrastructure health signal; this workflow is read-only.

Knuckles-Team Updated Sep 17, 2026

File contents

Full Infrastructure Health Check Workflow

Compose the named atomic skills without adding new health-scoring logic here.

Inputs

Provide the fleet's host/stack/endpoint selection and the git configuration reference.

Steps

Step 0: hardware-profile-sweep [skill: hardware-profile-sweep]

Invoke $hardware-profile-sweep with the workflow inputs to collect hardware details across the fleet.

Expected: hardware_profile

Step 1: host-resource-sampler [skill: host-resource-sampler]

Invoke $host-resource-sampler with the workflow inputs to sample current utilization across the fleet.

Expected: resource_sample

Step 2: docker-compose-drift-detector [skill: docker-compose-drift-detector]

Invoke $docker-compose-drift-detector with the workflow inputs to compare running compose state against git configuration.

Expected: drift_report

Step 3: ssl-expiry-checker [skill: ssl-expiry-checker]

Invoke $ssl-expiry-checker with the workflow inputs to check TLS certificate expiry across the fleet's endpoints.

Expected: expiry_report

Step 4: document-converter [skill: document-converter] [depends_on: Step 0, Step 1, Step 2, Step 3]

Invoke $document-converter with hardware_profile, resource_sample, drift_report, and expiry_report to render one consolidated Markdown/PDF health-check report.

Expected: health_check_document

Output

Return hardware_profile, resource_sample, drift_report, expiry_report, and health_check_document.

Execution

Run first (in parallel): Step 0 — $hardware-profile-sweep, Step 1 — $host-resource-sampler, Step 2 — $docker-compose-drift-detector, Step 3 — $ssl-expiry-checker.
After level 0: Step 4 — $document-converter.

Execution: If graph-os is reachable, offload the whole DAG via graph_orchestrate action=execute_workflow (or the kg-delegate skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet depends_on in parallel, then their dependents.

---name: full-infra-health-checkdescription: Run every health-relevant atomic skill this catalog owns — hardware profile, current resource utilization, compose configuration drift, and TLS expiry — in parallel across the fleet, then consolidate the findings into one formatted report. Use when an operator wants a single point-in-time snapshot combining every owned infrastructure health signal; this workflow is read-only.license: MIT---# Full Infrastructure Health Check WorkflowCompose the named atomic skills without adding new health-scoring logic here.## InputsProvide the fleet's host/stack/endpoint selection and the git configurationreference.## Steps### Step 0: hardware-profile-sweep [skill: hardware-profile-sweep]Invoke `$hardware-profile-sweep` with the workflow inputs to collecthardware details across the fleet.Expected: `hardware_profile`### Step 1: host-resource-sampler [skill: host-resource-sampler]Invoke `$host-resource-sampler` with the workflow inputs to samplecurrent utilization across the fleet.Expected: `resource_sample`### Step 2: docker-compose-drift-detector [skill: docker-compose-drift-detector]Invoke `$docker-compose-drift-detector` with the workflow inputs tocompare running compose state against git configuration.Expected: `drift_report`### Step 3: ssl-expiry-checker [skill: ssl-expiry-checker]Invoke `$ssl-expiry-checker` with the workflow inputs to check TLScertificate expiry across the fleet's endpoints.Expected: `expiry_report`### Step 4: document-converter [skill: document-converter] [depends_on: Step 0, Step 1, Step 2, Step 3]Invoke `$document-converter` with `hardware_profile`,`resource_sample`, `drift_report`, and `expiry_report` to render one consolidatedMarkdown/PDF health-check report.Expected: `health_check_document`## OutputReturn `hardware_profile`, `resource_sample`, `drift_report`, `expiry_report`,and `health_check_document`.## Execution- **Run first (in parallel):** Step 0 — `$hardware-profile-sweep`, Step 1 — `$host-resource-sampler`, Step 2 — `$docker-compose-drift-detector`, Step 3 — `$ssl-expiry-checker`.- **After level 0:** Step 4 — `$document-converter`.**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.

Frequently asked questions