perpetua-tools

Redirects agents to the canonical Perpetua-Tools orchestration skill after validating a synced local checkout.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents agents from using stale or divergent copies of the Perpetua-Tools orchestration skill by enforcing a fail-closed sync procedure before loading the canonical SKILL.md from the Perpetua-Tools repository. ## Core Features & Use Cases - Cross-Repo Redirect: Points agents to the canonical Perpetua-Tools SKILL.md on GitHub covering ModelRegistry, config/models.yml, routing.yml, and the FastAPI /orchestrate endpoint. - Fail-Closed Sync Validation: Resolves a local Perpetua-Tools checkout via environment variables or sibling discovery, then validates branch, cleanliness, and fast-forward pull before use. - Safe Fallback: On any resolver, fetch, or pull failure, agents stop and use the canonical GitHub version instead of a dirty local copy. - Use Case: When routing or selecting models for agent tasks, an agent first runs the sync procedure; if the local checkout is dirty, it falls back to the GitHub canonical skill rather than risking inconsistent orchestration behavior. ## Quick Start Ask the agent to load the canonical Perpetua-Tools SKILL.md from GitHub after running the fail-closed sync procedure for your local checkout.

Frequently Asked Questions about perpetua-tools

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

FAQPage Schema
How do I use the Perpetua-Tools skill from another repository?

Run the fail-closed sync procedure in sync-local-pt-checkout.md to resolve and validate your local Perpetua-Tools checkout. If validation succeeds, load the local SKILL.md; otherwise use the canonical version on GitHub main.

What does Perpetua-Tools orchestrate for agent tasks?

Perpetua-Tools handles agent lifecycle and model selection through ModelRegistry, config/models.yml, routing.yml, and a FastAPI /orchestrate endpoint. It also manages file-based agent-instance, budget, and queue state for dispatch.

What happens if my local Perpetua-Tools checkout is dirty?

The sync procedure fails closed: you stop and use the canonical GitHub SKILL.md instead. Never run git reset --hard or force-push main; use the safe-cross-host-sync reference card only with explicit operator approval.

When should I not use the perpetua-tools skill?

Do not use it for reasoning methodology or AFRP/CIDF process questions, which belong to the orama-system skill. This skill only covers orchestration, model routing, and the dispatch layer.

How is the local Perpetua-Tools checkout path resolved?

Resolution checks environment variables such as $PERPETUATOOLSROOT, $PERPETUA_TOOLS_ROOT, $PERPETUA_TOOLS_PATH, and $PT_HOME, plus .paths files or sibling directory discovery, as documented in sync-local-pt-checkout.md.