orama-gstack

Resolves and loads the canonical gstack-gbrain skill from the orama-system repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It locates the canonical gstack-gbrain skill inside the orama-system repository without hardcoding workstation paths, ensuring agents always load the authoritative version instead of stale or duplicated copies. ## Core Features & Use Cases - Marker-Verified Resolution: Searches environment variables, the current git repository root, and sibling checkouts for the canonical SKILL.md file. - Read-Only Loading: Loads the canonical skill without fetching, pulling, installing, or modifying anything during resolution. - Explicit Refresh Workflow: Supports a separate, explicitly authorized git fetch and fast-forward pull when the user requests a sync. - Use Case: An agent working across multiple clones of the orama-system repo uses this wrapper to reliably find and follow the single canonical gstack-gbrain skill card. ## Quick Start Ask the agent to load the orama-gstack skill so it resolves the canonical gstack-gbrain SKILL.md from the orama-system repository and follows its instructions.

Frequently Asked Questions about orama-gstack

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

FAQPage Schema
How do I load the canonical gstack-gbrain skill?

Invoke this wrapper skill, which searches for bin/orama-system/gstack-gbrain/SKILL.md using environment variables, the current git root, and sibling checkouts, then reads and follows that canonical file.

How does the skill resolve the orama-system repository path?

It checks ORAMA_SYSTEM_ROOT and ORAMA_SYSTEM_PATH first, then the current git repository toplevel, then a bounded depth-2 search of parent and grandparent directories for a sibling checkout containing the marker file.

Does loading the skill modify the canonical repository?

No. Resolution is strictly read-only and never fetches, pulls, installs, or modifies anything. Synchronization via git fetch and fast-forward pull only happens as a separate, explicitly authorized refresh action.

What happens if the canonical skill cannot be found?

The wrapper 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.

When should I run the refresh workflow?

Run refresh only when explicitly asked to synchronize the canonical repo. It performs git fetch and a fast-forward pull only if the worktree is clean and the branch tracks origin; otherwise it reports drift without overwriting local work.