grep-research-skills

Deep research powered by GREP — investigate APIs, libraries, companies, markets, and any topic with sourced citations. Build interactive HTML apps, slidedecks, and spreadsheets backed by research. Route to one of 27 domain experts (legal, medical, patent, financial, real estate, supply chain, maritime, etc.). Use when you need to research something, fact-check a claim, plan an implementation with real docs, create a new skill, build a deliverable, install Grep as an MCP server, check GREP account status, or upgrade your plan. Trigger on: "research", "look up", "investigate", "fact check", "what's the best way to", "how does X work", "find out about", "build me a", "make a slidedeck/spreadsheet", "use the X expert", "follow up on", "research using these files", "install grep MCP", "GREP", or any task where knowing current facts would improve the outcome. Use proactively before writing code against unfamiliar APIs.

Authenticate with GREP deep research. Use when the user needs to log in to GREP, authenticate, set up GREP credentials, or when a GREP API call returns 401 unauthorized. Supports direct arguments for agent use — /grep-login EMAIL to login with OTP, /grep-login --api-key KEY to authenticate with an API key.

Attach a Grep MCP server to .mcp.json so Claude has 4 native research tools (research_create, research_get, research_files_list, research_file_read) without writing curl. Use when the user wants Grep available as MCP tools, says "install Grep MCP", "set up Grep MCP server", or wants to research via MCP instead of HTTP. Reads the existing .mcp.json (or creates one), merges the grep entry, and verifies the server responds to tools/list.

Create a high-quality SKILL.md for any AI agent skill, powered by GREP deep research. Use when the user wants to build a new skill, plugin, or tool integration for Claude Code, Cowork, or OpenClaw. Also use when the user says "create a skill", "make a skill for X", "turn this into a skill", "build a plugin", or when they've been working through a workflow and want to capture it as a reusable skill. Researches the target domain first, then generates a production-ready skill file.

Deep research via GREP (typically ~5 minutes) with sourced citations. Use for most research tasks — investigating APIs/libraries before writing code, company research, market analysis, verifying complex claims, comprehensive docs lookups, fact-checking with sources. ALSO use proactively when planning to write code against unfamiliar APIs, SDKs, protocols, or libraries — sourced research beats guessing from memory. Use /quick-research (~25s) for simple lookups, or /ultra-research (up to 1 hour) for exhaustive investigations.

Build interactive HTML web apps via Grep — websites, dashboards, data explorers, calculators, comparison tools, charts, custom UIs. Use when the user asks for an interactive app, "build me a tool that does X", "make an interactive Y", or anything requiring a runnable HTML/JS deliverable beyond a static report. Routes to the app-builder expert with effort=build (~$2.00, 10-15 min). Returns an index.html in the job workspace; the skill prints the file URL when ready.

Multi-step research workflow — chains a quick orientation pass, then a deep investigation, then optional ultra-research, then an optional build artifact (slidedeck / app / spreadsheet). Use when the user wants thorough end-to-end research with a deliverable, says "do a full investigation on X", "research and then make me a presentation about X", or "comprehensive analysis of Y with a writeup". Threads job_ids through reference_jobs so each step builds on the prior step's findings without re-running them.

Research using user-supplied files as context — uploads PDFs, CSVs, text files, or images to Grep before submitting the research job, so the agent can analyse the user's documents alongside web research. Use when the user attaches files to the conversation, says "research using these documents", "fact-check this PDF", "summarise this report and find related work", or "use this CSV as input for research".

Build comparison spreadsheets via Grep with structured tabular data — vendor comparisons, market data tables, financial models, dataset analyses, competitive matrices, pricing tables. Use when the user asks for a spreadsheet, table, CSV, comparison matrix, or comparative data. Returns an HTML spreadsheet (with copyable cells / export-CSV button) in the job workspace. Routes to the app-builder expert with output_type=spreadsheet — v2 translates to expert_id=app-builder + effort=build + a "Build a spreadsheet of: " prefix (~$2.00, 10-15 min).

Continue an existing Grep research job with a follow-up question, building on the prior job's findings without re-running the entire investigation. Use when the user says "follow up on that research", "continue the X investigation", "go deeper on the third finding", or references a previous job by id/slug ("continue grep.ai/research/foo-bar-baz with: ...").

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.

Create research-backed slidedecks via Grep. Use when the user asks for a presentation, pitch deck, slides, "deck about X", or "presentation on Y". Covers market research, competitive analysis, product pitches, technical overviews, sales enablement. Returns an HTML slidedeck (slides.html or deck.html) in the job workspace. Routes to the app-builder expert with output_type=slidedeck — v2 translates that to expert_id=app-builder + effort=build + a "Create a slidedeck about: " question prefix (~$2.00, 10-15 min).

Fast fact check via GREP (~25 seconds). Use for simple lookups where you need a sourced answer but don't need a deep investigation — API endpoint verification, version checks, "what's the current X" questions, quick pre-code sanity checks. Prefer this over /research when a 25-second answer beats a 2-minute answer. Use /research instead if you need comprehensive coverage, or /ultra-research for full investigations.

Exhaustive deep investigation via GREP (CAN TAKE UP TO 1 HOUR). Use for the most demanding research tasks — security audits, legal research, regulatory analysis, full ecosystem surveys, multi-source synthesis, adversarial threat modeling, or any query where completeness matters more than speed. Use sparingly; this tier is slow and cannot be block-waited in a single call. The skill submits the job then schedules a /loop cron that polls every 5 minutes until complete. Use /research (~5 min) for most tasks, or /quick-research (~25s) for simple lookups.

Research-informed planning. Uses GREP deep research to investigate best practices, API docs, and architectural patterns before you plan an implementation. Use when planning a new feature, API integration, refactoring, or any non-trivial implementation where research would improve the plan.

Check GREP authentication status, view recent research jobs, or check on a specific job. Use when the user asks about their GREP account, wants to see past research, or check on a running job.

Choose a GREP subscription plan or upgrade your account. Use when the user wants to subscribe, upgrade, check pricing, manage their GREP plan, or after /grep-login suggests choosing a plan. Also use when a user hits quota limits or gets a "quota exceeded" error.