agentleFS
ubik-dshubik-dsh/deepseek-harness-skills/skills/check-hardware/SKILL.md

check-hardware

Skill0 starsChanged 50 days agoLicence not identifiedView on GitHub

Read what a Windows machine's hardware actually reports, and tell a healthy component from an unreadable one. Covers the commands that work and the ones that quietly return nothing, why a disk reporting Healthy may not have been checked at all, how to read memory slots rather than memory size, where WHEA and disk errors are logged, what the battery report's two capacities mean, and the order that keeps a diagnosis read-only until there is evidence. Ships a collector that gathers the readings and marks every one it could not take. Use when the user asks what is in their PC, whether a drive or a stick of memory is failing, why a machine reboots or throttles, how hot something runs, how old a battery is, or when a machine behaves badly and the cause is not in the software.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.