
Rag Cli Operator
- 1 installs
- Updated April 24, 2026
- wedsamuel1230/rag-cli-tool
Operates the repository's rag-cli workflow with uv for workspace init, document ingestion, querying, and index inspection, including JSON output for agents.
About
This skill runs the project's local RAG workflow via uv run rag-cli for init, ingest, query, and docs inspection. A developer uses it to index and search documents in the repo, troubleshoot command exits, or produce agent-friendly JSON output.
- Runs init, ingest, query, and docs commands in the right order
- Supports --format json output for agent integration
Rag Cli Operator by the numbers
- 1 all-time installs (skills.sh)
- Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/wedsamuel1230/rag-cli-tool --skill rag-cli-operatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | April 24, 2026 |
| Repository | wedsamuel1230/rag-cli-tool ↗ |
What it does
Operates the repository's rag-cli workflow with uv for workspace init, document ingestion, querying, and index inspection, including JSON output for agents.
Files
rag-cli Operator
Purpose
Run this project's local RAG workflow safely and consistently using uv run rag-cli ....
When To Use
Use this skill when requests mention:
rag-cliuvinit,ingest,query, ordocs- document indexing/search in this repo
- tool-friendly JSON outputs (
--format json)
Command Order
Follow this order unless the user asks otherwise:
1. uv sync 2. uv run rag-cli init --workspace <path> 3. uv run rag-cli ingest --workspace <path> --src <path> [--recursive] [--ext ...] --format json 4. uv run rag-cli query --workspace <path> --question "<question>" --mode hybrid --top-k 3 --format json 5. uv run rag-cli docs --workspace <path> --format json
Standard Command Templates
uv sync
uv run rag-cli --help
uv run rag-cli init --workspace .
uv run rag-cli ingest --workspace . --src ./docs --recursive --ext "pdf,docx,md" --format json
uv run rag-cli query --workspace . --question "What is SPI timing?" --mode hybrid --top-k 3 --format json
uv run rag-cli docs --workspace . --format jsonOutput Contract
Default to --format json when output will be consumed by an agent/tool.
Expected success shape:
answer: stringsnippets: [{ doc, section, text }]meta: object
Expected error shape:
error: { code, message, details }
If command output is for humans only, --format text is acceptable.
Workspace And Config Rules
- Always pass
--workspaceexplicitly when not operating in repo root. initcreates.rag/and baseline config/index state.- Required environment/config keys:
POE_API_KEY(preferred)OPENAI_BASE_URL(default:https://api.poe.com/v1)LLM_MODEL(default:gemini-3.1-flash-lite)EMBEDDING_MODEL(optional)- Backward compatibility:
OPENAI_API_KEYis accepted ifPOE_API_KEYis not set.
PowerShell Machine-Level Env Setup
[Environment]::SetEnvironmentVariable("POE_API_KEY", "your-key", "Machine")
[Environment]::SetEnvironmentVariable("OPENAI_BASE_URL", "https://api.poe.com/v1", "Machine")
[Environment]::SetEnvironmentVariable("LLM_MODEL", "gemini-3.1-flash-lite", "Machine")
# Optional if your provider supports embeddings:
[Environment]::SetEnvironmentVariable("EMBEDDING_MODEL", "", "Machine")Agent Integration Notes
Keep parameter naming aligned with:
skills/search_docs_cli.jsonworkspace,question,mode,top_kskills/index_files_cli.jsonworkspace,path,recursive,ext
When mapping tool calls, preserve these names to avoid wrapper drift.
Troubleshooting
Missing .rag index
Symptoms:
docsorqueryfails with missing index messages.
Action:
1. Run uv run rag-cli init --workspace <path> 2. Re-run ingest 3. Retry query or docs
Empty ingest results
Symptoms:
ingestreports no files found or indexed count is zero.
Action:
1. Check --src path exists. 2. Confirm extension filter via --ext. 3. Add --recursive for nested folders. 4. Re-run ingest with --format json and inspect meta.
Missing API/env values
Symptoms:
- model/provider errors when running query pipelines that require remote backends.
Action:
1. Set required env keys. 2. Re-run from same shell/session. 3. Verify with a simple query call.
Non-zero exit code
Action sequence:
1. Re-run same command with --format json. 2. Parse error.code and error.message. 3. Apply minimal fix. 4. Re-run only the failed step, then continue command order.