odylith-query

Query the local Odylith projection store to locate relevant context using anchors.

34|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odylith-query
Source: https://github.com/odylith/odylith/tree/main/.agents/skills/odylith-query
Command: npx skills add https://github.com/odylith/odylith --skill odylith-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When concrete anchors exist, this skill enables fast, accurate search of the local Odylith projection store to locate relevant context and results.

Core Features & Use Cases

  • Optimized search over the local projection store using existing anchors.
  • Retrieve and surface matching context to inform agent decisions.
  • Use Case: You want to quickly find related components or past decisions tied to specific anchors without querying external services.

Quick Start

Search the local Odylith projection store using your existing anchors.

Frequently Asked Questions about odylith-query

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

FAQPage Schema
How do I search a local data store using existing anchors to find relevant context?

Anchor-based local store search queries the local Odylith projection store using existing anchors to retrieve deterministic, context-rich results. It surfaces matching context to inform agent planning without querying external services.

What is anchor-based retrieval and when do I need it for agent planning?

Anchor-based retrieval finds relevant context in the local Odylith projection store when concrete anchors exist. It is needed during agent planning when fast, deterministic results are required without external API calls.

Can I retrieve context from the local projection store without making external network calls?

Local projection store retrieval operates only on local data and avoids external calls entirely. It returns deterministic results by querying existing anchors within the local Odylith store to surface matching context.

What's the best way to find related components or past decisions tied to specific anchors?

The best way is querying the local Odylith projection store using existing anchors. This approach retrieves matching context quickly and deterministically, avoiding the latency of querying external services for related components.

Are there limitations to using local store retrieval for finding agent planning context?

Local store retrieval is constrained to operating only on local data and requires existing concrete anchors to function. It cannot fetch external data and returns deterministic results limited to the local Odylith projection store.