perpetua-hardware

Resolves and loads the canonical hardware configuration skill from the orama-system repository.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill perpetua-hardware-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perpetua-hardware
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.agents/skills/perpetua-hardware
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill perpetua-hardware-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hardware-specific configuration for the ModelRegistry lives in a separate canonical repository, and this Skill provides a safe, read-only way to locate and load that canonical hardware/SKILL.md file without hardcoding workstation paths or accidentally modifying the source repo. ## Core Features & Use Cases - Marker-Based Repository Resolution: Searches environment variables (ORAMA_SYSTEM_ROOT, ORAMA_SYSTEM_PATH), the current git toplevel, and sibling checkouts at bounded depth to find the canonical hardware/SKILL.md file. - Read-Only Loading Guarantee: Explicitly forbids fetching, pulling, pruning, installing, or modifying anything while loading a skill, preventing accidental side effects. - Explicit Refresh Workflow: Provides a separate, user-authorized git fetch and fast-forward pull procedure for synchronizing the canonical repo, with drift reporting when the worktree is dirty. - Use Case: An agent on a new machine needs the hardware configuration that ModelRegistry reads; this Skill locates the canonical orama-system checkout and loads hardware/SKILL.md without guessing paths or touching the repo state. ## Quick Start Ask the agent to load the perpetua-hardware skill so it resolves the canonical repository root and reads the hardware configuration from hardware/SKILL.md.

Frequently Asked Questions about perpetua-hardware

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load the canonical hardware skill from another repository?

Set ORAMA_SYSTEM_ROOT or ORAMA_SYSTEM_PATH to the canonical repo, or run from inside it so git rev-parse resolves the toplevel. The skill then reads hardware/SKILL.md from that root in read-only mode.

How does the skill find the orama-system repository without a hardcoded path?

It checks ORAMA_SYSTEM_ROOT and ORAMA_SYSTEM_PATH first, then the current git toplevel, then a bounded depth-2 search of parent and grandparent directories for a sibling checkout containing hardware/SKILL.md.

Can loading this skill modify or update the canonical repository?

No. Loading is strictly read-only and marker-verified; fetching, pulling, pruning, installing, or modifying anything is forbidden. Refreshing the repo is a separate, explicitly authorized maintenance action.

What happens if the canonical hardware skill cannot be found?

The skill reports the canonical skill as unavailable and asks for its location only if the task genuinely needs it. It never guesses or falls back to a different repository's copy.

How do I refresh the canonical repo when the worktree is dirty?

Run git fetch origin --prune and git status to inspect drift. A fast-forward pull only proceeds on a clean tracking branch; otherwise local work is preserved and the drift is reported.