How do I install the Repo B Hardware First skill?

Run npx skillmds@latest add grtninja/repo-b-hardware-first 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 Repo B Hardware First safe to use?

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

Which AI agents work with Repo B Hardware First?

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 Repo B Hardware First free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo B Hardware First?

grtninja (@grtninja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo B Hardware First by grtninja — Agent Skill

Name: Repo B Hardware First
Rating: 4.666666666666667 (3 reviews)
Author: grtninja

Repo B Hardware First

Enforce hardware-first diagnosis and fixes in <PRIVATE_REPO_B>. Use for runtime probe, telemetry, inference, and integration failures where strict real-hardware behavior, no new stubs, deterministic diagnostics, and no unrequested driver/runtime mutation are required.

grtninja Updated Sep 10, 2026

File contents

REPO_B Shim Hardware First

Use this skill to troubleshoot and fix shim issues with real-hardware assumptions.

Operating Rules

Assume hardware exists and is the required path.
Do not add new stubs, fake fallbacks, or simulation shortcuts.
Do not modify or refresh driver/runtime/firmware unless explicitly requested.
Keep strict env modes explicit during diagnosis.

Strict-Diagnosis Workflow

Set strict environment flags.
Run doctor and probe checks.
Run strict preflight profiles.
Verify host/runtime versions against config/mx3_runtime_baseline.json before any host mutation.
Fix root cause in real execution path first (routing, preload, lifecycle, endpoint readiness).
Re-run checks and capture evidence.

Scope Boundary

Use this skill only for real-hardware diagnosis and fix verification.

Do not use this skill for:

PR governance/doc lockstep only workflows.
Control Center process/restart UX operations.
Agent Bridge safety-mode configuration.

Commands

$env:REPO_B_ONLY = "1"
$env:REPO_B_FORCE_REAL = "1"
$env:REPO_B_INFERENCE_PROVIDER = "repo_b_only"
python -m memryx_mx3_python_shim --doctor
python shim_hw_test.py --json --require-hardware

pwsh -File tools/preflight.ps1 -Fast
pwsh -File tools/preflight.ps1 -Hardware -ForceReal -MemryxOnly -VerboseOutput

References

Strict command matrix: references/strict-commands.md

Loopback

If this lane is unresolved, blocked, or ambiguous:

Capture current evidence and failure context.
Route back through $skill-hub for chain recalculation.
Resume only after the updated chain returns a deterministic next step.

---name: repo-b-hardware-firstdescription: Enforce hardware-first diagnosis and fixes in <PRIVATE_REPO_B>. Use for runtime probe, telemetry, inference, and integration failures where strict real-hardware behavior, no new stubs, deterministic diagnostics, and no unrequested driver/runtime mutation are required.---# REPO_B Shim Hardware FirstUse this skill to troubleshoot and fix shim issues with real-hardware assumptions.## Operating Rules1. Assume hardware exists and is the required path.2. Do not add new stubs, fake fallbacks, or simulation shortcuts.3. Do not modify or refresh driver/runtime/firmware unless explicitly requested.4. Keep strict env modes explicit during diagnosis.## Strict-Diagnosis Workflow1. Set strict environment flags.2. Run doctor and probe checks.3. Run strict preflight profiles.4. Verify host/runtime versions against `config/mx3_runtime_baseline.json` before any host mutation.5. Fix root cause in real execution path first (routing, preload, lifecycle, endpoint readiness).6. Re-run checks and capture evidence.## Scope BoundaryUse this skill only for real-hardware diagnosis and fix verification.Do not use this skill for:1. PR governance/doc lockstep only workflows.2. Control Center process/restart UX operations.3. Agent Bridge safety-mode configuration.## Commands```bash$env:REPO_B_ONLY = "1"$env:REPO_B_FORCE_REAL = "1"$env:REPO_B_INFERENCE_PROVIDER = "repo_b_only"python -m memryx_mx3_python_shim --doctorpython shim_hw_test.py --json --require-hardware``````powershellpwsh -File tools/preflight.ps1 -Fastpwsh -File tools/preflight.ps1 -Hardware -ForceReal -MemryxOnly -VerboseOutput```## References- Strict command matrix: `references/strict-commands.md`## LoopbackIf this lane is unresolved, blocked, or ambiguous:1. Capture current evidence and failure context.2. Route back through `$skill-hub` for chain recalculation.3. Resume only after the updated chain returns a deterministic next step.

Frequently asked questions