orama-cidf

Resolves and loads the canonical Content Insertion Decision Framework skill from the orama-system repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across multiple projects, agents need a reliable way to locate and load the canonical Content Insertion Decision Framework (CIDF) skill without duplicating it or accidentally fetching from the wrong repository. This wrapper resolves the correct orama-system checkout and delegates all behavior to it. ## Core Features & Use Cases - Marker-Verified Resolution: Locates the canonical repo via environment variables, git toplevel detection, or a bounded sibling-directory search, verifying the marker file bin/orama-system/cidf/SKILL.md exists. - Read-Only Loading: Loads the canonical skill without fetching, pulling, installing, or modifying anything, preventing unintended side effects during activation. - Explicit Refresh Workflow: Provides a guarded git fetch/pull procedure for maintenance that refuses to overwrite dirty worktrees or non-tracking branches. - Use Case: An agent in a sibling project needs to make a content insertion decision; it uses this wrapper to find the orama-system checkout and load the canonical CIDF skill's decide(), lint_strict(), and execute_with_fallback() API. ## Quick Start Ask the agent to load the orama-cidf skill and apply the Content Insertion Decision Framework to decide where new content should be inserted in your project.

Frequently Asked Questions about orama-cidf

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

FAQPage Schema
How do I load the canonical CIDF skill from the orama-system repo?

Set ORAMA_SYSTEM_ROOT or ORAMA_SYSTEM_PATH to the repo root, or run from inside the canonical repo so git rev-parse resolves it. The wrapper verifies bin/orama-system/cidf/SKILL.md exists, then reads and follows that file.

How does the wrapper find the orama-system repository?

It checks ORAMA_SYSTEM_ROOT and ORAMA_SYSTEM_PATH first, then the current git toplevel, then a bounded depth-2 search of parent and grandparent directories for a sibling checkout containing the marker file bin/orama-system/cidf/SKILL.md.

Does loading the skill modify or update the canonical repository?

No. Loading is strictly read-only and marker-verified; it never fetches, pulls, installs, or modifies anything. Refreshing the repo is a separate, explicitly authorized action using git fetch and fast-forward pull only.

What happens if the canonical orama-system repo 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.

Why does the refresh procedure refuse to pull sometimes?

The pull only runs when the worktree is clean, the branch tracks origin, and a fast-forward is possible. If the worktree is dirty or fast-forward fails, it reports the drift instead of overwriting local work.