ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Draft patent claims for an invention. Use when user says \"撰写权利要求\", \"draft claims\", \"写权利要求书\", \"claim drafting\", or wants to create patent claims. The core skill of the patent pipeline.
Claude Code
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting --agent claude-code
Codex
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a codex -y
Cursor
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a cursor -y
Gemini CLI
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a gemini-cli -y
GitHub Copilot
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a github-copilot -y
OpenCode
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a opencode -y
Windsurf
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -a windsurf -y
name: claims-drafting description: "Draft patent claims for an invention. Use when user says \"撰写权利要求\", \"draft claims\", \"写权利要求书\", \"claim drafting\", or wants to create patent claims. The core skill of the patent pipeline." argument-hint: "[invention-disclosure-path]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply, mcp__antigravity__antigravity, mcp__antigravity__antigravity-reply, mcp__grok__grok, mcp__grok__grok-reply, mcp__claude-review__review, mcp__claude-review__review_reply, mcp__claude-review__review_start, mcp__claude-review__review_reply_start, mcp__claude-review__review_status
> **Before each reviewer slot**, follow [Selectable Reviewers](../shared-references/reviewer-backends.md): > resolve invocation → `.aris/reviewer.json` → Claude Code default (Codex MCP) > with `reviewer_route.py` through the canonical helper resolver, preserving this > slot's tier, fresh contexts, source/image inputs and deterministic gates. > Codex examples/pins below apply only to `backend=codex`; other routes use their > own first-call/reply contract. Save the route and actual returned identity; > unavailable selections are `REVIEW_UNAVAILABLE`. Classify acceptance from actual > families/completion/scope. Forward invocation reviewer/model/effort overrides > to reviewer-bearing children. Generation workers are unchanged.
Draft patent claims based on: **$ARGUMENTS**
This is the most critical skill in the patent pipeline. Claims define the legal scope of protection -- everything else (specification, figures, abstract) exists to support and enable the claims.
1. `patent/INVENTION_DISCLOSURE.md` — structured invention with core/supporting/optional features 2. `patent/PRIOR_ART_REPORT.md` — prior art to avoid 3. `patent/NOVELTY_ASSESSMENT.md` — novelty analysis with suggested amendments 4. Target jurisdiction from invention disclosure or `$ARGUMENTS`
Load `../shared-references/patent-writing-principles.md` for claim drafting principles, antecedent basis rules, and common pitfalls. Load `../shared-references/patent-format-cn.md` for CN claim format (其特征在于). Load `../shared-references/patent-format-us.md` for US claim format (comprising, means-plus-function). Load `../shared-references/patent-format-ep.md` for EP two-part form (characterised in that).
Based on patent type and jurisdiction:
**If `PATENT_TYPE = utility_model` (实用新型)**:
Based on target jurisdiction:
| Jurisdiction | Claim Style | Characterising Phrase | Preamble Format | |-------------|------------|----------------------|-----------------| | CN | Two-part (两部式) | 其特征在于 | 一种...的方法/装置,包括: | | US | Open (preferred) | comprising | A method for..., comprising: | | EP | Two-part (mandatory) | characterised in that | A method for..., comprising [known], characterised in that [inventive] | | ALL | Draft CN + US + EP | All of the above | All of the above |
**CRITICAL — Claims numbering (CN format):**
**CRITICAL — No empirical content in claims:**
For each claim category identified in INVENTION_DISCLOSURE.md:
**Method Claim (broadest)**: 1. Start with preamble identifying the category and purpose 2. List the core inventive features (from the "Core Inventive Concept" section) 3. Include enough known features for context (but not more than necessary) 4. Use open transition ("comprising" / "包括") 5. Each element should be separated by semicolons or on separate lines 6. Apply jurisdiction-specific format:
**System/Apparatus Claim**: 1. Mirror the method claim in structural form 2. Each method step becomes a "module configured to..." or "component for..." 3. Same hierarchy of known vs. inventive features
**Quality checks for each independent claim**:
· · · · · · · · 💬 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…