Stats
Actions
Tags
From grep-research-skills
Route research to the right Grep public domain expert (legal, medical, patent, financial, real estate, supply chain, maritime, etc.). Use when the user mentions a specialised domain ("legal research", "patent landscape", "biotech clinical trials", "real estate due diligence", "supply chain mapping") OR says "use the X expert". The skill reads resources/experts.md (snapshot of GET /api/v2/experts), picks the best match by keyword + sample-question similarity, and submits a research job with explicit expert_id.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grep-research-skills:grep-domain-expertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Routes a research question to one of Grep's 27 public domain experts. Each expert is tuned for a specific vertical (legal case law, clinical trials, patent prior art, vessel tracking, etc.) and returns sharper results than the generalist tier when the question fits.
Routes a research question to one of Grep's 27 public domain experts. Each expert is tuned for a specific vertical (legal case law, clinical trials, patent prior art, vessel tracking, etc.) and returns sharper results than the generalist tier when the question fits.
| Trigger | Skill |
|---|---|
| Generalist research (no specific domain) | /research or /quick-research |
| User names a domain ("legal research on X", "patent landscape for Y") | /grep-domain-expert |
| User asks for a deliverable (slidedeck, spreadsheet, app) | /grep-build-slidedeck, /grep-build-spreadsheet, /grep-build-app |
| Multi-step: investigate then build | /grep-research-workflow |
If the user's intent is genuinely general ("what is Anthropic?", "summarise this paper"), fall back to /research — don't force an expert match.
On first use per session, silently check for updates (throttled to once per hour):
node "$SCRIPTS_DIR/update-check.js" 2>/dev/null &
Run in background — must never delay the research.
The user must be authenticated. Before running any API call, check auth status:
node "$SCRIPTS_DIR/auth.js" status
If "authenticated": false, automatically invoke /grep-login — don't just tell the user to do it. Run the login flow, then continue once authenticated.
The skill dir is usually symlinked, so always resolve via the canonical SKILL.md location. scripts/ and resources/ sit next to skills/ in the install layout:
SCRIPTS_DIR="$(dirname "$(dirname "$(dirname "$(readlink -f "${CLAUDE_SKILL_DIR}/SKILL.md")")")")/scripts"
RESOURCES_DIR="$(dirname "$SCRIPTS_DIR")/resources"
Read $RESOURCES_DIR/experts.md to get the 27 expert IDs, their domains, and sample questions. The agent reads it directly — there's no script wrapper.
cat "$RESOURCES_DIR/experts.md"
This is the source of truth. The live GET /api/v2/experts endpoint is the canonical version; the markdown is a hand-maintained snapshot kept in drift-tracked sync (see .github/workflows/sync-experts.yml, lands in PR 10).
Two-step process:
domain and the sample question. Top 1-3 candidates.patent-research-ip-expert): proceed silently.people-due-diligence-expert or corporate-due-diligence-expert if Sam wears multiple hats): use AskUserQuestion with the candidates as options. Each option's description should be the expert's sample question so the user can recognise the right fit./research for this — none of the domain experts fit cleanly." Don't force general-expert unless the user explicitly asked for it.Heuristics for ambiguous cases:
corporate-due-diligence-expertpeople-due-diligence-expertbusiness-aml-compliance-expertindividual-aml-compliance-expertreal-time-intelligence-expertmedia-producer (with --output-type=podcast|video|news_broadcast)Before submitting, refine the raw user question to match the chosen expert's sample-question style. Don't just pass $ARGUMENTS verbatim — make it specific.
Example:
The refined query should include:
Default by user signal:
--effort=low (~25s, $0.40 PAYG)--effort=medium (~5min, $2.00 PAYG)--effort=high (up to 1hr, $10.00 PAYG)Note that effort=high runs up to an hour and cannot be block-waited via run — use the async pattern in the subsection below ("effort=high requires the async pattern"). Do NOT delegate to /ultra-research for high-effort domain-expert routing — that skill quotes the entire argument string into the query, so --expert-id=... would be silently swallowed.
node "$SCRIPTS_DIR/grep-api.js" run "<refined_query>" \
--expert-id=<chosen-id> --effort=<low|medium> --max-wait=540 \
[--output-type=<podcast|video|news_broadcast|slidedeck|spreadsheet|html_app>] 2>&1
--output-type= is required when routing to media-producer (the expert needs to know whether to produce a podcast, video, or news broadcast) and also valid when routing to app-builder (slidedeck / spreadsheet / html_app). For all other experts, omit the flag — they default to a written report.
Run with Monitor (timeout_ms: 560000, persistent: false). With 2>&1, status updates and the final report stream as events.
Tell the user: "Routing to the expert. This takes about ."
effort=high requires the async pattern, not /ultra-research delegationeffort=high jobs run up to an hour and must use the same submit-then-poll pattern /ultra-research uses. Do not invoke /ultra-research with $ARGUMENTS containing --expert-id=... — that skill quotes the entire argument string into the query and the flag is silently swallowed.
Instead, run the same two steps /ultra-research runs, but with --expert-id on the research call. Slug extraction uses Node (no jq dependency, matching the rest of the repo):
# 1. Submit non-blocking with the expert-id flag
SUBMIT=$(node "$SCRIPTS_DIR/grep-api.js" research "<refined>" \
--expert-id=<chosen-id> --effort=high \
[--output-type=<podcast|video|news_broadcast|slidedeck|spreadsheet|html_app>])
SLUG=$(echo "$SUBMIT" | node -e "let d='';process.stdin.on('data',c=>d+=c).on('end',()=>{const j=JSON.parse(d);process.stdout.write(j.slug||j.job_id||j.id||'')}")
[ -z "$SLUG" ] && { echo "Submit failed: $SUBMIT"; exit 1; }
# 2. Schedule a /loop cron (5-minute interval) that polls and self-terminates
# on completion — mirrors the /ultra-research pattern verbatim.
Pass the captured $SLUG into the same /loop cron prompt /ultra-research uses (see skills/ultra-research/SKILL.md Step 3). The polling loop, presentation, and CronDelete-on-complete logic are identical — only the submit command differs.
When the Monitor notification arrives:
/grep-continue instead of a fresh job (cheaper, builds on context)/research and let v2 auto-select. Forcing general-expert when /research would do is wasted UX.--effort=high to run (the blocking command). High effort can take an hour and will hit the bash 10-min cap. Use the async submit + /loop pattern in Step 5's "effort=high requires the async pattern" subsection — NOT /ultra-research delegation, which silently drops --expert-id.$ARGUMENTS raw is the difference between a generic answer and an actionable one.general-expert when matching is ambiguous — ask the user.experts.md from CWD or a hardcoded path. Always resolve via $RESOURCES_DIR because the skill is symlinked.If a curl against $GREP_API_BASE/api/v2/experts (defaults to https://api.grep.ai/api/v2/experts) returns an ID that's not in resources/experts.md (or vice versa), the snapshot has drifted. Open an issue or PR to refresh — the .github/workflows/sync-experts.yml workflow automates this nightly.
npx claudepluginhub parcha-ai/grep-research-skills --plugin grep-research-skillsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.