ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Search patent databases and academic literature for prior art relevant to an invention. Use when user says \"现有技术检索\", \"prior art search\", \"专利检索\", \"check patents\", or wants to find relevant prior art.
Claude Code
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search --agent claude-code
Codex
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a codex -y
Cursor
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a cursor -y
Gemini CLI
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a gemini-cli -y
GitHub Copilot
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a github-copilot -y
OpenCode
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a opencode -y
Windsurf
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill prior-art-search -a windsurf -y
name: prior-art-search description: "Search patent databases and academic literature for prior art relevant to an invention. Use when user says \"现有技术检索\", \"prior art search\", \"专利检索\", \"check patents\", or wants to find relevant prior art." argument-hint: "[invention-description-or-path]" allowed-tools: Bash(*), Read, Glob, Grep, WebSearch, WebFetch, Write
Search patents and literature for prior art relevant to: **$ARGUMENTS**
Adapted from `/research-lit` for patent-specific searching.
Read the invention description from: 1. `$ARGUMENTS` if it contains technical details 2. `patent/INVENTION_BRIEF.md` if it exists 3. `INVENTION_BRIEF.md` if it exists at project root
Load `../shared-references/prior-art-databases.md` for search strategy templates and IPC/CPC classification guidance.
From the invention description, identify: 1. **Core inventive concept**: The primary technical contribution (1-2 sentences) 2. **Technical problem**: What problem it solves 3. **Key technical features**: 4-6 specific technical elements that define the invention 4. **IPC/CPC classes**: Predict relevant classification codes (e.g., G06N, G06F)
For EACH search concept, search via:
**Google Patents** (via WebSearch):
WebSearch: "site:patents.google.com [keywords]" WebSearch: "[keywords] patent"
**Espacenet** (via WebFetch):
**Assignee/Inventor Search**:
For each potentially relevant patent found:
Search the same concepts in academic databases:
1. **Google Scholar** (via WebSearch): `WebSearch "[keywords] site:scholar.google.com"` 2. **arXiv** (via `/arxiv` if available, or WebSearch): Search for preprints 3. **Semantic Scholar** (via `/semantic-scholar` if API key set, or WebSearch)
For each relevant paper found:
For each reference found, assess:
1. **Relevance**: How closely does it relate to the invention? 2. **Overlap Risk**: Does it disclose the same or similar technical solution?
3. **Relationship**: Is it anticipating, relevant, or merely background?
Organize results by IPC/CPC classification to see the technical landscape.
Based on the search results:
**Disclaimer**: This is a preliminary assessment only. A professional freedom-to-operate analysis by a patent attorney is recommended before filing.
Write `patent/PRIOR_ART_REPORT.md` with:
## Prior Art Search Report ### Invention Summary [1-2 sentence description of the searched invention] ### Search Strategy - Keywords used: [...] - IPC/CPC classes searched: [...] - Databases searched: Google Patents, Espacenet, Google Scholar, arXiv - Date range: [year] to present ### Patent References Found | # | Patent No. | Title | Date | Assignee | IPC/CPC | Key Teaching | Overlap Risk | |---|-----------|-------|------|----------|---------|-------------|-------------| | 1 | CN... / US... | [title] | [date] | [assignee] | [codes] | [2-3 sentences] | HIGH/MEDIUM/LOW | ### Non-Patent Literature Found | # | Reference | Title | Authors/Venue | Year | Key Contribution | Relevance | |---|-----------|-------|--------------|------|-----------------|-----------| | 1 | [DOI/link] | [title] | [authors] | [year] | [1-2 sentences] | HIGH/MEDIUM/LOW | ### Prior Art Landscape [Organized by technical approach or IPC class, not just chronological] ### Freedom-to-Operate Preliminary Assessment [Which existing patents might block the invention? What is the risk level?] ### Recommendations - Suggested claim scope adjustments based on prior art - Areas where novelty appears strongest - References to watch during prosecution
· · · · · · · · 💬 Join Community · 🌱 ARIS is a methodology, not a platform. What matters is the research workflow — take it wherever you go.
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this…
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results",…
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv",…
Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user…
Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables.…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…