hardware-evidence-capture
Skill23 starsChanged 40 days agoMITView on GitHub
Inspect controlled simulated hardware and retain explicit command and observation provenance.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- av-eventsSkill
- creative-concept-designSkill
- educational-explainerSkill
- ffmpeg-productionSkill
- footage-editSkill
- gemini-visualizeSkill
- gr-advisorSkill
- image-generationSkill
- mlflow-tracesSkill
- movie-commentarySkill
- plugin-maintenanceSkill
- qwen-image-integrationSkill
- qwen-video-integrationSkill
- research-brief-builderSkill
- research-visualization-blenderSkill
- research-visualization-freecadSkill
- reverse-search-video-frameSkill
- spatial-video-analysisSkill
- tts-productionSkill
- video-explainerSkill
- video-generationSkill
- video-productionSkill
- video-researchSkill
- video-to-skillSkill
- video-translationSkill
- weaviate-setupSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use mhs_discover and mhs_meta_info to inspect the named device and current capabilities, directions and limits.
- Very specific: line 13
Read sensors or images with mhs_read and retain the returned original artifact path, byte count, SHA256, command/state identity, method and …
- Distinctive: line 16
Do not upload or publish observations without separate authority.
- Distinctive: line 22
Do not write that file on the operator's behalf without an explicit instruction.
- Very specific: line 26
After a failed write, inspect mhs_health_check before any new write.
≈ “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
Hardware evidence capture
Use mhs_discover and mhs_meta_info to inspect the named device and current
capabilities, directions and limits. All currently supported devices are
simulated. Preserve that label in every result; never infer physical state,
calibration, safety or camera coverage.
Read sensors or images with mhs_read and retain the returned original artifact
path, byte count, SHA256, command/state identity, method and units. Generated
simulator images are synthetic data and cannot become factual original evidence.
Do not upload or publish observations without separate authority.
For a write, provide one explicit command ID and exact parameters. Hard limits
cannot be overridden. confirm=true cannot approve a soft override or a
confirmation-required operation. Return the full approval proposal for an
operator's review; only the separately configured host file can authorize it.
Do not write that file on the operator's behalf without an explicit instruction.
An awaiting proposal has not attempted its action. A terminal command ID replays
its receipt and never re-executes.
After a failed write, inspect mhs_health_check before any new write. Inspect
the executed command, effective limits and resulting state in its receipt.
Emergency stop latches the simulator off. Soft recovery needs its own exact host
approval. Neither outcome proves physical stop or recovery effectiveness.
Physical adapters are unavailable pending named owner qualification. Stop on missing authority or an unknown result; preserve the error and receipt rather than inventing a device observation or automatically retrying.
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.

