perpetua-config

Redirects to the canonical model registry and device configuration skill in Perpetua-Tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents configuration drift by acting as a fail-closed redirect stub that points to the canonical model registry and device configuration document maintained in the Perpetua-Tools repository, ensuring agents always load the authoritative version. ## Core Features & Use Cases - Canonical Redirect: Points to the authoritative config/SKILL.md in the Perpetua-Tools GitHub repository rather than duplicating content. - Fail-Closed Sync: Defines a validation procedure for resolving and syncing a local Perpetua-Tools checkout before use, stopping on any resolver, branch, or pull failure. - Cross-Repo Link Policy: References shared policies for cross-repository links and safe cross-host synchronization. - Use Case: When configuring which backends (ollama, mlx, lm-studio) and models run on each device in the ECC-tools ecosystem, this stub ensures you follow the synced canonical registry instead of a stale local copy. ## Quick Start Ask the agent to load the canonical perpetua-config skill from the Perpetua-Tools repository after running the documented local checkout sync procedure.

Frequently Asked Questions about perpetua-config

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

FAQPage Schema
How do I configure model backends across devices in the ECC-tools ecosystem?

Load the canonical config/SKILL.md from the Perpetua-Tools repository, which defines the model registry mapping each device to backends like ollama, mlx, and lm-studio with prioritized models. This stub only redirects to that document.

Why does this skill not contain the actual configuration content?

It is a thin cross-repo redirect stub. The canonical content lives in Perpetua-Tools on GitHub, and this wrapper exists to prevent stale copies and enforce a single source of truth.

What happens if the local Perpetua-Tools checkout sync fails?

The procedure is fail-closed: on any resolver, branch, cleanliness, fetch, or pull failure, stop and use the canonical SKILL.md directly from GitHub. Never run git reset --hard or force-push main.

Can I use a dirty Perpetua-Tools worktree with this skill?

Only with explicit operator approval, following the safe cross-host sync reference card in the git-history-surgery skill before any commit or push. Otherwise, fall back to the canonical GitHub version.

Does this skill work on Windows PowerShell?

Yes, but set UTF-8 encoding explicitly for console input, output, and PYTHONUTF8 before reading or writing skill files to avoid encoding issues.