perpetua-startup-intelligence

Redirects agents to the canonical startup-intelligence skill in the Perpetua-Tools repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When startup fails to reach backends, engineers need a single authoritative source for scenario classification, probe retry, adaptive timeouts, cloud fallback, and env-local override detection. This stub prevents stale or divergent copies by enforcing a fail-closed sync to the canonical skill hosted in the Perpetua-Tools GitHub repository. ## Core Features & Use Cases - Cross-Repo Redirect: Points agents to the canonical startup-intelligence SKILL.md on GitHub main, never assuming a sibling checkout layout. - Fail-Closed Local Sync: Resolves a local Perpetua-Tools checkout via environment variables ($PERPETUATOOLSROOT, $PERPETUA_TOOLS_ROOT, $PERPETUA_TOOLS_PATH, $PT_HOME) and validates branch, cleanliness, and fast-forward pull before use. - Dirty-Worktree Guardrails: Requires explicit operator approval before any commit or push when the worktree is dirty, and forbids git reset --hard or force-push on main. - Use Case: An agent troubleshooting a Perpetua-Tools startup failure loads this stub, syncs or falls back to the canonical GitHub skill, then applies its classification and retry guidance. ## Quick Start Ask the agent to load the canonical startup-intelligence skill from Perpetua-Tools and diagnose why startup cannot reach the backends.

Frequently Asked Questions about perpetua-startup-intelligence

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

FAQPage Schema
How do I use the startup-intelligence skill from orama-system?

Load the canonical startup-intelligence SKILL.md from the Perpetua-Tools GitHub repository main branch. Use a local checkout only after the fail-closed sync procedure succeeds; never copy behavior from the wrapper stub.

How do I resolve a local Perpetua-Tools checkout path?

Check the environment variables $PERPETUATOOLSROOT, $PERPETUA_TOOLS_ROOT, $PERPETUA_TOOLS_PATH, or $PT_HOME, or use .paths and sibling discovery. The resolution and validation block is documented in the sync-local-pt-checkout reference.

What happens if the local Perpetua-Tools sync fails?

On any resolver, branch, cleanliness, fetch, or pull failure, stop and use the canonical skill on GitHub instead. The procedure forbids git reset --hard and force-pushing main.

Can I commit changes when the Perpetua-Tools worktree is dirty?

Only with explicit operator approval, using the safe cross-host sync reference card from the git-history-surgery skill. Without approval, no commit or push should occur.

Why do skill files cause encoding issues on Windows PowerShell?

PowerShell defaults to non-UTF-8 encodings, which can corrupt skill file content. Set input, output, and $OutputEncoding to UTF8 and export PYTHONUTF8=1 before reading or writing skill files.