pt-orama-harness-integration

Redirects cross-harness integration requests to the canonical hermes-harness skill definition.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents stale or duplicated integration logic by acting as a thin wrapper that always points to the canonical hermes-harness skill, ensuring agents load the single authoritative source before acting. ## Core Features & Use Cases - Canonical Redirection: Resolves the repository root at runtime and loads the canonical hermes-harness SKILL.md instead of duplicating behavior. - Drift Detection: Runs git fetch and status checks to verify the canonical skill is up to date, reporting drift when the worktree is dirty or untracked. - Windows UTF-8 Support: Provides PowerShell encoding commands to avoid character corruption on Windows terminals. - Use Case: When an agent encounters the legacy pt-orama harness integration entry point, it follows this wrapper to pull the latest canonical hermes-harness card and operates from that authoritative definition. ## Quick Start Load the canonical hermes-harness skill by resolving the repo root and following bin/orama-system/skills/hermes-harness/SKILL.md before performing any integration action.

Frequently Asked Questions about pt-orama-harness-integration

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

FAQPage Schema
How do I use the pt-orama harness integration skill?

Do not copy behavior from this wrapper. Resolve the repository root at runtime, then open and follow the canonical card at bin/orama-system/skills/hermes-harness/SKILL.md, which contains the actual integration logic.

What is a thin wrapper skill in a SKILL.md architecture?

A thin wrapper is a minimal SKILL.md that contains no operational logic itself and instead points to a canonical skill path. It exists so legacy entry points remain valid while behavior lives in one authoritative location.

How do I check if the canonical hermes-harness skill is up to date?

Run git fetch origin --prune and git status --short --branch from the canonical skill directory. If the branch tracks a remote and the worktree is clean, run git pull --ff-only; otherwise report drift before proceeding.

Why does the skill include Windows UTF-8 PowerShell commands?

Windows consoles often default to non-UTF-8 encodings, which corrupt Unicode output when reading skill files. The provided PowerShell commands set input, output, and Python encoding to UTF-8 to prevent mojibake.

What happens if the git worktree is dirty when loading the canonical skill?

If the worktree is dirty or the branch is not tracking a remote, do not pull. Instead, report the drift and read the canonical card with the caveat that it may not reflect the latest upstream version.