MCP Local RAG
shinpr/mcp-local-rag
Searches, saves, and maintains a local document index through a local RAG MCP server.
Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy…
Install Legal Search Engine
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills legal-search-engine --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .claude/skills/legal-search-engine && rm -rf skills-srcUse ~/.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/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .claude/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills legal-search-engine --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .agents/skills/legal-search-engine && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .agents/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills legal-search-engine --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .cursor/skills/legal-search-engine && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .cursor/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/infometa/workbuddyskills.git --path experts/legal-search-pro/skills/legal-search-engine--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills legal-search-engine --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .gemini/skills/legal-search-engine && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .gemini/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install infometa/workbuddyskills legal-search-engineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .github/skills/legal-search-engine && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .github/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill legal-search-engine -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills legal-search-engine --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/legal-search-pro/skills/legal-search-engine .opencode/skills/legal-search-engine && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "legal-search-engine" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/legal-search-pro/skills/legal-search-engine into .opencode/skills/legal-search-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "legal-search-engine", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
legal-search-engine- GitHub stars
- 348
- Token cost
- ~2.2k tokens
- SKILL.md length
- 426 words
- Files
- 3 (incl. references)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- None found
At a glance
Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy…
- Works in 6 steps: 重量级任务先建核验任务目录：若任务单写【输出档位：重量】或【核验工作台：必用】，在… → 前置知识推荐：先凭专业知识推荐最可能命中的核心法律文件及条款（给用户一个快速锚点）。 → 构造检索式：核心词 + 法律术语组合、同义词扩展、时间/地域限定、案由筛选。 → …
- Perform actual statute retrieval through available legal databases
- SKILL.md covers 执行流水线（务必按序）, 检索能力选择（内部规则，不向用户透传）, 公开来源与专业来源隔离（强制） and 行政执法类检索的特殊路径, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Legal Search Engine is an agent skill from infometa/workbuddyskills. Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy with statutory hierarchy scanning and comprehensive retrieval methodology, then filter and rank results with effectiveness verification and applicability validation in a feedback loop. Use this skill to perform actual statute retrieval through available legal databases, MCP/skills, official sources, or public web…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/effectiveness-hierarchy.md` and `references/retrieval-capability-chain.md`).
It sits in AI & LLM Engineering, covering Retrieval-augmented generation. It works with Model Context Protocol. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- Perform actual statute retrieval through available legal databases
- Official sources
- Public web sources without exposing tool selection to users
Example prompts
- “/legal-search-engine”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- 重量级任务先建核验任务目录：若任务单写【输出档位：重量】或【核验工作台：必用】，在第一轮检索前先运行 legal-verify init --query "用户原始问题" --title "报告标题" --out "output/报告.html"，记录返回的…
- 前置知识推荐：先凭专业知识推荐最可能命中的核心法律文件及条款（给用户一个快速锚点）。
- 构造检索式：核心词 + 法律术语组合、同义词扩展、时间/地域限定、案由筛选。
- 调用检索工具实际检索（见下方「检索工具调用」）。
- 检索即持久化（强制）：每调用一批检索/读取工具后，立即把该批结果整理成 retrieval-batch-XXX.json，运行 legal-verify capture --task --input retrieval-batch-XXX.json --provider…
- 全文完整性验收（强制）：每轮 capture 后运行 legal-verify audit-sources --task 。如果生成的 source-fulltext-queue.json 有 blocker，说明可能只保存了搜索工具 observation…
What it can do on your machine
Read from SKILL.md and the folder at commit 91b77ea. 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.
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
Legal Search Engine loads about 2.2k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 426 words of instructions outside code blocks.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 426 words (~2,203 tokens).
- name
- legal-search-engine
Files
SKILL.md and 2 other files (references) in experts/legal-search-pro/skills/legal-search-engine of infometa/workbuddyskills.
- SKILL.md
- references/effectiveness-hierarchy.md
- references/retrieval-capability-chain.md
Open the folder on GitHubat commit 91b77ea
Compare with similar skills
Legal Search Engine 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Legal Search Engine this skillinfometa/workbuddyskills | 348 | — | ~2.2k | Automated safety check: Pass | None | |
| MCP Local RAGshinpr/mcp-local-rag | 412 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Local RAG Searchnkapila6/mcp-local-rag | 134 | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| AutoRAG Setup and RepairMarker-Inc-Korea/AutoRAG | 5.1k | — | ~5.6k | Automated safety check: Pass | MIT | |
| RAG Check Firstlyonzin/knowledge-rag | 292 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Sciverseopendatalab/Sciverse-Agent-Tools | 120 | — | ~3k | Automated safety check: Pass | Custom licence |
Similar skills
Local RAG Search
nkapila6/mcp-local-rag
Efficiently perform web searches using the mcp-local-rag server with semantic similarity ranking.
AutoRAG Setup and Repair
Marker-Inc-Korea/AutoRAG
Installs, configures, and repairs AutoRAG's search model, approved folders, indexes, and datasources, and registers its Lite MCP server.
RAG Check First
lyonzin/knowledge-rag
Before answering any technical question, code request, architecture decision, or factual claim, call searchknowledge to check the local corpus.
Sciverse
opendatalab/Sciverse-Agent-Tools
A skill your agent uses when the user needs academic paper retrieval — searching scientific literature by author/year/journal, finding paper chunks for RAG-style citations, or expanding original…
Pgvector Semantic Search
timescale/pg-aiguide
A skill your agent uses for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search.
More from infometa/workbuddyskills
All 218 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Related
Works with
Categories
Questions about Legal Search Engine
What does Legal Search Engine do?
Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy…. Legal Search Engine is an agent skill from infometa/workbuddyskills. Execute the multi-layer legal retrieval pipeline once a scenario is identified - extract legal facts, locate the legal issue, judge source effectiveness hierarchy, generate dynamic search strategy with statutory hierarchy scanning and comprehensive retrieval methodology, then filter and rank results with effectiveness verification and applicability validation in a feedback loop.
When should I use Legal Search Engine?
Legal Search Engine fits situations like: perform actual statute retrieval through available legal databases; official sources; public web sources without exposing tool selection to users.
How do I install Legal Search Engine in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill legal-search-engine -a claude-code`. Or copy the skill folder (experts/legal-search-pro/skills/legal-search-engine in infometa/workbuddyskills) into .claude/skills/legal-search-engine in your project. Claude Code loads it when a task matches its description.
How do I install Legal Search Engine in Codex?
Run `npx skills add infometa/workbuddyskills --skill legal-search-engine -a codex`. Or copy the skill folder (experts/legal-search-pro/skills/legal-search-engine in infometa/workbuddyskills) into .agents/skills/legal-search-engine in your project. Codex loads it when a task matches its description.
Can I use Legal Search Engine 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 infometa/workbuddyskills --skill legal-search-engine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/legal-search-engine, .gemini/skills/legal-search-engine, .github/skills/legal-search-engine and .opencode/skills/legal-search-engine in your project.
What does Legal Search Engine need to run?
SKILL.md names no scripts, command-line tools or credentials: Legal Search Engine is instructions for the agent only.
Does Legal Search Engine 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 Legal Search Engine 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 Legal Search Engine use?
No licence was found for Legal Search Engine or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Legal Search Engine use?
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Legal Search Engine?
Skills that share tags, products or a category with Legal Search Engine: MCP Local RAG (shinpr/mcp-local-rag, 412 stars), Local RAG Search (nkapila6/mcp-local-rag, 134 stars), AutoRAG Setup and Repair (Marker-Inc-Korea/AutoRAG, 5.1k stars) and RAG Check First (lyonzin/knowledge-rag, 292 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Legal Search Engine?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 348 GitHub stars. The repository holds 218 skills in this directory. The repository was last updated on October 9, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.