Agent skill

Orchata RAG

by LeoYeAI in LeoYeAI/openclaw-master-skills

Knowledge management and RAG platform with tree-based document indexing.

MITAuto-check passedAI & LLM Engineering

Install Orchata RAG

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill orchata-rag -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills orchata-rag --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchata .claude/skills/orchata-rag && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
orchata-rag
GitHub stars
2.2k
Token cost
~4.7k tokens
SKILL.md length
1,778 words
Files
2
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Knowledge management and RAG platform with tree-based document indexing.

  • Works in 2 steps: query_spaces - Search document content… → smart_query - Discover which spaces are…
  • Manage Orchata knowledge bases via MCP tools
  • SKILL.md covers What is Orchata?, Core Concepts, MCP Tools Reference and Workflow Patterns, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Orchata RAG is an agent skill from LeoYeAI/openclaw-master-skills. Knowledge management and RAG platform with tree-based document indexing. Use this skill to search, browse, and manage Orchata knowledge bases via MCP tools.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in AI & LLM Engineering, covering Retrieval-augmented generation, Knowledge bases and MCP servers. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Manage Orchata knowledge bases via MCP tools
  • Tasks that involve Retrieval-augmented generation
  • Tasks that involve Knowledge bases

Example prompts

  • “/orchata-rag”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. query_spaces - Search document content using tree-based reasoning
  2. smart_query - Discover which spaces are relevant for a query

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Orchata RAG loads about 4.7k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 1,778 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,778 words, ~4,697 tokens.

Download SKILL.mdSave it as .claude/skills/orchata-rag/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
orchata-rag
description
Knowledge management and RAG platform with tree-based document indexing. Use this skill to search, browse, and manage Orchata knowledge bases via MCP tools.
metadata.version
1.0.0
metadata.author
Orchata AI

Orchata Skills

This document describes how to effectively use Orchata, a RAG (Retrieval-Augmented Generation) platform with tree-based document indexing. Load this into your context to interact with Orchata knowledge bases.

What is Orchata?

Orchata is a knowledge management platform that:

  • Organizes documents into Spaces - Logical containers for related content
  • Uses tree-based indexing - Documents are parsed into hierarchical structures with sections, summaries, and page ranges
  • Provides semantic search - Find relevant content using natural language queries
  • Exposes MCP tools - AI assistants can directly manage and query knowledge bases

Core Concepts

Spaces

A Space is a container for related documents. Think of it as a folder with semantic search capabilities.

  • Each space has a name, description, and optional icon
  • Descriptions are used by smart_query to recommend relevant spaces
  • Spaces can be archived (soft-deleted)
Documents

A Document is content within a space. Supported formats include:

  • PDF (text-based and scanned with OCR)
  • Word documents (.docx)
  • Excel spreadsheets (.xlsx)
  • PowerPoint presentations (.pptx)
  • Markdown files (.md)
  • Plain text files (.txt)
  • Images (PNG, JPG, etc.)

Document Status:

StatusDescription
PENDINGUploaded, waiting for processing
PROCESSINGBeing parsed and indexed
COMPLETEDReady for queries
FAILEDProcessing error occurred

Important: Only query documents with status: "COMPLETED". Other statuses won't return results.

Document Trees

Documents are indexed into hierarchical tree structures:

  • Each tree has nodes representing sections/chapters
  • Nodes contain: title, summary, startPage, endPage, textContent
  • Trees enable precise navigation of large documents
Queries

Two types of queries are available:

  1. query_spaces - Search document content using tree-based reasoning
  2. smart_query - Discover which spaces are relevant for a query

MCP Tools Reference

Space Management
list_spaces

List all knowledge spaces in the organization.

text
list_spaces
list_spaces with status="active"
list_spaces with page=1 pageSize=20

Parameters:

  • page (number, optional): Page number (default: 1)
  • pageSize (number, optional): Items per page (default: 10)
  • status (string, optional): Filter by active, archived, or all

manage_space

Create, get, update, or delete a space.

text
manage_space with action="create" name="Product Docs" description="Technical documentation"
manage_space with action="create" name="Legal" description="Case files" icon="briefcase"
manage_space with action="get" id="space_abc123"
manage_space with action="update" id="space_abc123" description="Updated description"
manage_space with action="delete" id="space_abc123"

Parameters:

  • action (string, required): create, get, update, or delete
  • id (string): Space ID (required for get/update/delete)
  • name (string): Space name (required for create)
  • description (string, optional): Space description
  • icon (string, optional): Icon name. Defaults to "folder"
  • slug (string, optional): URL-friendly identifier
  • isArchived (boolean, optional): Archive status (for update)

Valid Icons: folder, book, file-text, database, package, archive, briefcase, inbox, layers, box

If an invalid icon is provided, the tool returns an error with the list of valid options.


Document Management
list_documents

List documents in a space.

text
list_documents with spaceId="space_abc123"
list_documents with spaceId="space_abc123" status="completed"
list_documents with spaceId="space_abc123" status="all"

Parameters:

  • spaceId (string, required): Space ID
  • page (number, optional): Page number
  • pageSize (number, optional): Items per page (max: 100)
  • status (string, optional): Filter by status. Values: pending, processing, completed, failed, or all. Omitting returns all documents.

Note: Status values are case-insensitive (completed and COMPLETED both work).


save_document

Upload or upsert documents (single or batch).

Single document:

text
save_document with spaceId="space_abc123" filename="guide.md" content="# Guide\n\nContent here..."

Batch upload:

text
save_document with spaceId="space_abc123" documents=[{"filename": "doc1.md", "content": "..."}, {"filename": "doc2.md", "content": "..."}]

Parameters:

  • spaceId (string, required): Space ID
  • filename (string): Filename (required for single)
  • content (string): Content (required for single)
  • documents (array, optional): Array of {filename, content, metadata} for batch
  • metadata (object, optional): Custom key-value pairs

get_document

Get document content by ID or filename. Returns processed markdown text.

text
get_document with spaceId="space_abc123" id="doc_xyz789"
get_document with spaceId="space_abc123" filename="guide.md"
get_document with spaceId="*" filename="guide.md"

Parameters:

  • spaceId (string, required): Space ID, or * to search all spaces (requires filename)
  • id (string, optional): Document ID
  • filename (string, optional): Filename

Notes:

  • Either id or filename is required
  • Use spaceId="*" to search all spaces when you know the filename but not the space
  • For completed documents, returns the extracted markdown text (not raw PDF binary)
  • When using *, the response includes the spaceId where the document was found

update_document

Update document content or metadata.

text
update_document with spaceId="space_abc123" id="doc_xyz789" content="New content..."
update_document with spaceId="space_abc123" id="doc_xyz789" append=true content="Additional content"

Parameters:

  • spaceId (string, required): Space ID
  • id (string, required): Document ID
  • content (string, optional): New content
  • metadata (object, optional): New metadata
  • append (boolean, optional): Append instead of replace
  • separator (string, optional): Separator for append mode

delete_document

Permanently delete a document.

text
delete_document with spaceId="space_abc123" id="doc_xyz789"

Parameters:

  • spaceId (string, required): Space ID
  • id (string, required): Document ID

Query Tools
query_spaces

Search documents across one or more spaces using tree-based reasoning.

text
query_spaces with query="How do I authenticate API requests?"
query_spaces with query="installation guide" spaceIds="space_abc123"
query_spaces with query="error handling" spaceIds=["space_abc", "space_def"] topK=10

Parameters:

  • query (string, required): Natural language search query
  • spaceIds (string or array, optional): Space ID(s) to search. Omit or use * for all spaces
  • topK (number, optional): Maximum results (default: 10)
  • compact (boolean, optional): Use compact format (default: false). See When to Use Compact below.

When to Use Compact:

ModeWhen to useWhat you get
compact=false (default)Most queries. Any time you need actual data, facts, numbers, dates, or details from documents.Full results with document metadata, tree context, page ranges, and complete content.
compact=trueBroad discovery queries where you only need to know which documents are relevant, not their content.Minimal results: just content snippet, source filename, and score.

Rule of thumb: Default to compact=false. Only use compact=true when you're browsing/surveying and don't need the actual content yet.

Response (compact=true format):

json
{
  "results": [
    {
      "content": "Relevant text content...",
      "source": "filename.pdf",
      "score": 0.95
    }
  ],
  "total": 5
}

smart_query

Discover which spaces are relevant for a query using LLM reasoning.

text
smart_query with query="How do I install the SDK?"
smart_query with query="billing questions" maxSpaces=3

Parameters:

  • query (string, required): Query to find relevant spaces for
  • maxSpaces (number, optional): Maximum spaces to return (default: 5)

Response:

json
{
  "query": "How do I install the SDK?",
  "relevantSpaces": [
    {"spaceId": "space_abc123", "relevance": "Contains SDK installation guides"},
    {"spaceId": "space_def456", "relevance": "Has developer tutorials"}
  ],
  "totalFound": 2
}

Use case: When you don't know which space to search, use smart_query first to discover relevant spaces, then use query_spaces with those space IDs.


Tree Visibility Tools

These tools let you explore the hierarchical structure of indexed documents.

get_document_tree

Get the tree structure of a document showing sections, summaries, and page ranges.

text
get_document_tree with spaceId="space_abc123" documentId="doc_xyz789"

Parameters:

  • spaceId (string, required): Space ID
  • documentId (string, required): Document ID

Response:

json
{
  "documentId": "doc_xyz789",
  "totalPages": 45,
  "totalNodes": 12,
  "nodes": [
    {
      "nodeId": "0001",
      "title": "Introduction",
      "summary": "Overview of the system architecture...",
      "pages": "1-5",
      "depth": 0
    },
    {
      "nodeId": "0002",
      "title": "Installation",
      "summary": "Step-by-step installation guide...",
      "pages": "6-12",
      "depth": 0
    }
  ]
}

Use case: Use this to understand a document's structure before drilling into specific sections.


get_tree_node

Get the full text content of a specific tree node/section.

text
get_tree_node with documentId="doc_xyz789" nodeId="0002"

Parameters:

  • documentId (string, required): Document ID
  • nodeId (string, required): Node ID from the tree structure

Response:

json
{
  "documentId": "doc_xyz789",
  "filename": "manual.pdf",
  "nodeId": "0002",
  "title": "Installation",
  "summary": "Step-by-step installation guide...",
  "pages": "6-12",
  "depth": 0,
  "content": "## Installation\n\nTo install the software, follow these steps:\n\n1. Download the installer...\n\n..."
}

Use case: After viewing the tree structure, use this to read the full content of a specific section.


Workflow Patterns

Pattern 1: Search for Information (Default Approach)

For most questions, a single query_spaces call is all you need. Start here before trying multi-step workflows.

text
query_spaces with query="your question"

This searches all spaces with full details (compact=false by default). One call, done.

If you want to narrow to specific spaces:

text
query_spaces with query="your question" spaceIds="known_space_id"

If you truly don't know which spaces exist:

text
smart_query with query="your question"
# Then use the returned spaceIds:
query_spaces with query="your question" spaceIds=["returned_space_id"]

Avoid over-searching. The multi-step workflow (smart_query -> query_spaces -> get_document_tree -> get_tree_node) is rarely necessary. For most questions, a single query_spaces call returns the answer directly. Only escalate to tree browsing if results are insufficient.

Pattern 2: Look Up Specific Data

When looking for specific facts, numbers, dates, names, or details:

Just query directly -- one call:

text
query_spaces with query="total amount on invoice #1234"

The default compact=false returns full content with document metadata, so you get the actual data you need in one step. Do not use compact=true for data lookups -- it strips the detail you need.

Pattern 3: Browse a Large Document

When you need to navigate a large document's structure:

  1. Get the document structure:

    text
    get_document_tree with spaceId="space_id" documentId="doc_id"
  2. Identify relevant sections from the node titles and summaries

  3. Read specific sections:

    text
    get_tree_node with documentId="doc_id" nodeId="relevant_node_id"
Show full SKILL.md (708 more words)Show less
Pattern 4: Add New Content

When adding documents to a knowledge base:

  1. Find or create the appropriate space:

    text
    list_spaces
    # or
    manage_space with action="create" name="New Space" description="..."
  2. Upload the content:

    text
    save_document with spaceId="space_id" filename="document.md" content="..."
  3. Wait for processing (status will change from PENDING -> PROCESSING -> COMPLETED)

  4. Verify it's ready:

    text
    list_documents with spaceId="space_id" status="COMPLETED"

manage_space - Valid Icons

When creating or updating a space, use one of these icon values:

  • folder (default)
  • book
  • file-text
  • database
  • package
  • archive
  • briefcase
  • inbox
  • layers
  • box

Invalid icons will return a helpful error message with the list of valid options.


list_documents - Status Parameter

The status parameter accepts the following values (case-insensitive):

  • "all" - Returns documents in any status (COMPLETED, FAILED, PENDING, PROCESSING)
  • "completed" - Returns only successfully processed documents
  • "failed" - Returns only documents that failed processing (includes errorMessage field)
  • "pending" - Returns documents waiting to be processed
  • "processing" - Returns documents currently being processed

Documents with status="FAILED" will include an errorMessage field explaining what went wrong during processing.


save_document - Processing Workflow

Documents are processed asynchronously:

  1. save_document returns immediately with status="PROCESSING"
  2. Background job generates embeddings and indexes the document (typically 1-3 seconds)
  3. Status changes to "COMPLETED" when ready
  4. Document becomes searchable via query_spaces

To check completion status:

  • Use get_document to check a specific document's status
  • Use list_documents with status="processing" to see all processing documents
  • Use list_documents with status="failed" to see any failures

Example:

javascript
// Save document
const result = await save_document({...});
// result.document.status === "PROCESSING"

// Check status after a moment
const doc = await get_document({id: result.document.id});
// doc.status === "COMPLETED" (when ready)

get_tree_node - Content Availability

get_tree_node may return "(No text content cached for this node)" for certain nodes. This occurs for:

  • Structural/organizational nodes without associated text content
  • Nodes that serve as section headers in the tree hierarchy

This is expected behavior.

To read actual document content:

  • Use get_document to retrieve the full processed markdown
  • Use query_spaces to search and retrieve relevant content chunks

The tree structure (via get_document_tree) is always available and shows document organization, summaries, and page ranges.


Best Practices

DO
  • Start with a single query_spaces call - it usually has the answer in one step
  • Use compact=false (the default) for most queries - you get full content and context
  • Check document status before querying - only COMPLETED documents are searchable
  • Use descriptive queries - natural language works best
  • Use tree tools for large documents - navigate structure instead of reading everything
  • Write good space descriptions - they're used by smart_query for discovery
DON'T
  • Don't over-search - avoid multi-step workflows (smart_query -> query_spaces -> get_document_tree -> get_tree_node) when a single query_spaces call suffices
  • Don't use compact=true for data lookups - it strips the content you need; only use it for broad discovery
  • Don't query PENDING/PROCESSING documents - they won't return results
  • Don't use very short queries - more context = better results
  • Don't forget to check processing status after uploading new documents

Error Handling

Common errors and solutions:

ErrorCauseSolution
"Document not found"Wrong ID or no accessVerify the document ID with list_documents
"Space not found"Wrong ID or archivedUse list_spaces to find valid space IDs
Empty search resultsDocument not COMPLETED or no matchesCheck document status; try broader query
"Tree not found"Document uses vector indexing or not processedCheck if document status is COMPLETED
"Invalid icon"Icon name not in allowed listUse one of: folder, book, file-text, database, package, archive, briefcase, inbox, layers, box
"No text content cached"Tree node content not cachedThis is normal for structural nodes; use get_document for full content
Troubleshooting Tips

If save_document fails:

  1. Verify the space exists with manage_space with action="get" id="..."
  2. Ensure content is valid text/markdown
  3. Check that the space is not archived

If list_documents returns 0 results:

  1. Try status="all" or omit the status parameter entirely
  2. Verify the spaceId is correct with list_spaces
  3. Check if documents are still processing (status="processing")

If get_tree_node returns no content:

  • Some nodes are structural and don't have cached text content
  • Use get_document to get the full processed document text instead
  • Or use query_spaces to search for specific content

Quick Reference

TaskToolExample
List all spaceslist_spaceslist_spaces with status="active"
Create a spacemanage_spacemanage_space with action="create" name="Docs"
List documentslist_documentslist_documents with spaceId="..."
Upload contentsave_documentsave_document with spaceId="..." content="..."
Get document textget_documentget_document with spaceId="..." id="..."
Search contentquery_spacesquery_spaces with query="..."
Find relevant spacessmart_querysmart_query with query="..."
View doc structureget_document_treeget_document_tree with spaceId="..." documentId="..."
Read a sectionget_tree_nodeget_tree_node with documentId="..." nodeId="..."

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/orchata of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Orchata RAG next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Orchata RAG compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Orchata RAG this skillLeoYeAI/openclaw-master-skills2.2k—~4.7kAutomated safety check: PassMIT
Blockify Integrationiternal-technologies-partners/blockify-agentic-data-optimization315—~6.2kAutomated safety check: NotesCustom licence
Agentsop Difyagentsope/SkillAlchemy436—~5.4kAutomated safety check: NotesMIT
Sc QAopen-edge-platform/edge-ai-suites140—~2.3kAutomated safety check: PassApache-2.0
RAG AssistantAtmosphere/atmosphere3.8k—~504Automated safety check: PassApache-2.0
Langchain4j RAG Implementation Patternsgiuseppe-trisciuoglio/developer-kit357—~3.3kAutomated safety check: NotesMIT

Similar skills

  • Blockify Integration

    iternal-technologies-partners/blockify-agentic-data-optimization

    Process documents with Blockify API to create optimized IdeaBlocks for RAG.

    315 GitHub stars~6.2k tokensUpdated 5 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Agentsop Dify

    agentsope/SkillAlchemy

    SOP for building LLM applications on Dify — visual workflow + chatflow + agent + RAG knowledge base + plugin marketplace + observability, self-hostable.

    436 GitHub stars~5.4k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check: notes
  • Sc QA

    open-edge-platform/edge-ai-suites

    Ask a natural-language question against indexed content via the Content Search RAG Q&A endpoint.

    140 GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • RAG Assistant

    Atmosphere/atmosphere

    Knowledge base assistant that retrieves and cites documents from a curated index.

    3.8k GitHub stars~504 tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Langchain4j RAG Implementation Patterns

    giuseppe-trisciuoglio/developer-kit

    Provides Retrieval-Augmented Generation (RAG) implementation patterns with LangChain4j for Java.

    357 GitHub stars~3.3k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes
  • RAG

    automateyournetwork/netclaw

    Ingest user-selected documents and retrieve cited procedures, standards, and design evidence from the local RAG knowledge base.

    676 GitHub stars~2.8k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Orchata RAG

What does Orchata RAG do?

Knowledge management and RAG platform with tree-based document indexing. Orchata RAG is an agent skill from LeoYeAI/openclaw-master-skills. Knowledge management and RAG platform with tree-based document indexing.

When should I use Orchata RAG?

Orchata RAG fits situations like: manage Orchata knowledge bases via MCP tools; tasks that involve Retrieval-augmented generation; tasks that involve Knowledge bases.

How do I install Orchata RAG in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill orchata-rag -a claude-code`. Or copy the skill folder (skills/orchata in LeoYeAI/openclaw-master-skills) into .claude/skills/orchata-rag in your project. Claude Code loads it when a task matches its description.

How do I install Orchata RAG in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill orchata-rag -a codex`. Or copy the skill folder (skills/orchata in LeoYeAI/openclaw-master-skills) into .agents/skills/orchata-rag in your project. Codex loads it when a task matches its description.

Can I use Orchata RAG in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill orchata-rag -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchata-rag, .gemini/skills/orchata-rag, .github/skills/orchata-rag and .opencode/skills/orchata-rag in your project.

What does Orchata RAG need to run?

SKILL.md names no scripts, command-line tools or credentials: Orchata RAG is instructions for the agent only.

Does Orchata RAG access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Orchata RAG safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Orchata RAG use?

Orchata RAG is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Orchata RAG use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Orchata RAG?

Skills that share tags, products or a category with Orchata RAG: Blockify Integration (iternal-technologies-partners/blockify-agentic-data-optimization, 315 stars), Agentsop Dify (agentsope/SkillAlchemy, 436 stars), Sc QA (open-edge-platform/edge-ai-suites, 140 stars) and RAG Assistant (Atmosphere/atmosphere, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Orchata RAG?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.