Paper to Chinese Patent Drafter
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
Write the full patent specification from claims and invention disclosure.
Install Specification Writing
$ npx skills add AI4Scientist/nano-scientist --skill specification-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AI4Scientist/nano-scientist specification-writing --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/AI4Scientist/nano-scientist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specification-writing .claude/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .claude/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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/AI4Scientist/nano-scientist/tree/main/skills/specification-writingType 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 AI4Scientist/nano-scientist --skill specification-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AI4Scientist/nano-scientist specification-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI4Scientist/nano-scientist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specification-writing .agents/skills/specification-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .agents/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 AI4Scientist/nano-scientist --skill specification-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AI4Scientist/nano-scientist specification-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI4Scientist/nano-scientist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specification-writing .cursor/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .cursor/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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/AI4Scientist/nano-scientist.git --path skills/specification-writing--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 AI4Scientist/nano-scientist --skill specification-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AI4Scientist/nano-scientist specification-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI4Scientist/nano-scientist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specification-writing .gemini/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .gemini/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 AI4Scientist/nano-scientist specification-writingInstalls 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 AI4Scientist/nano-scientist --skill specification-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AI4Scientist/nano-scientist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specification-writing .github/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .github/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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 AI4Scientist/nano-scientist --skill specification-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AI4Scientist/nano-scientist specification-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI4Scientist/nano-scientist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specification-writing .opencode/skills/specification-writing && 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 "specification-writing" agent skill from https://github.com/AI4Scientist/nano-scientist/tree/main/skills/specification-writing into .opencode/skills/specification-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-writing", 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
specification-writing- GitHub stars
- 128
- Used in
- 2 other repos
- Token cost
- ~2k tokens
- SKILL.md length
- 729 words
- Files
- 1
- Skills in repo
- 74
- Repo updated
- First seen
- Licence
- None found
At a glance
Write the full patent specification from claims and invention disclosure.
- Works in 11 steps: Initialize Specification Structure → Write Title (发明名称) → Write Technical Field (技术领域) → …
- User says 撰写说明书
- SKILL.md covers Constants, Inputs, Shared References and Workflow, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Specification Writing is an agent skill from AI4Scientist/nano-scientist. Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Intellectual property. The repository describes itself as: An autonomous research agent that turns a topic into a peer-reviewed technical report.
When your agent uses it
- User says 撰写说明书
- Write specification
- Patent description
- Wants to draft the complete patent specification
Example prompts
- “write specification”
- “patent description”
- “/specification-writing”
Requirements
- Pre-approved tools (allowed-tools): Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply
Workflow steps
11 steps, taken from the step headings in SKILL.md.
- Initialize Specification Structure
- Write Title (发明名称)
- Write Technical Field (技术领域)
- Write Background (背景技术)
- Write Summary (发明内容)
- Write Brief Description of Drawings (附图说明)
- Write Detailed Description (具体实施方式)
- Write Abstract (摘要)
- Claim Support Verification
- Cross-Model Review
- Output
What it can do on your machine
Read from SKILL.md and the folder at commit 7132192. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(*)ReadWriteEditGrepGlobAgentSkillWebSearchWebFetch
…and 2 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Specification Writing loads about 2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 729 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, WebSearch, WebFetch, mcp__codex__codex, mcp__c
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 729 words (~2,032 tokens).
“Write the patent specification based on: $ARGUMENTS”
- name
- specification-writing
- allowed-tools
- Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply
- argument-hint
- claims-path
Files
Just SKILL.md in skills/specification-writing of AI4Scientist/nano-scientist.
Open the folder on GitHubat commit 7132192
Used in 2 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in AI4Scientist/nano-scientist, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Specification Writing 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 |
|---|---|---|---|---|---|---|
| Specification Writing this skillAI4Scientist/nano-scientist | 128 | 2 repos | ~2k | Automated safety check: Notes | None | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 106 | 1 repos | ~959 | Automated safety check: Pass | None | |
| Patent Examinegfodor/legal-skills | 393 | — | ~4.8k | Automated safety check: Pass | GPL-3.0 | |
| Patent Auditgfodor/legal-skills | 393 | — | ~2.9k | Automated safety check: Pass | GPL-3.0 | |
| Replica BrandJakeschincariol/replica-skill | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Paper To Cn Patent
snipp-zha/Paper-to-patent-Skill
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.
Patent Examine
gfodor/legal-skills
Iteratively examine and revise a draft U.S. An agent skill from gfodor/legal-skills.
Patent Audit
gfodor/legal-skills
Audit a draft U.S. An agent skill from gfodor/legal-skills.
Replica Brand
Jakeschincariol/replica-skill
Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide…
Patent Workaround
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
More from AI4Scientist/nano-scientist
All 74 skills in this repoFormula Derivation
AI4Scientist/nano-scientist
Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a…
Paper Compile
AI4Scientist/nano-scientist
Compile LaTeX paper to PDF, fix errors, and verify output. An agent skill from AI4Scientist/nano-scientist.
Paper Figure
AI4Scientist/nano-scientist
Generate publication-quality figures and tables from experiment results.
Paper Navigator
AI4Scientist/nano-scientist
Find and read academic papers: disambiguate queries, discover papers (search, citation traversal, recommendations, arXiv monitoring, trending, GitHub search), evaluate (TLDR, citations, code, SOTA)…
Proof Writer
AI4Scientist/nano-scientist
Writes rigorous mathematical proofs for ML/AI theory. An agent skill from AI4Scientist/nano-scientist.
Ablation Planner
AI4Scientist/nano-scientist
A skill your agent uses when main results pass result-to-claim (claimsupported=yes or partial) and ablation studies are needed for paper submission.
Related
Categories
Questions about Specification Writing
What does Specification Writing do?
Write the full patent specification from claims and invention disclosure. Specification Writing is an agent skill from AI4Scientist/nano-scientist. Write the full patent specification from claims and invention disclosure.
When should I use Specification Writing?
Specification Writing fits situations like: user says 撰写说明书; write specification; patent description; wants to draft the complete patent specification.
How do I install Specification Writing in Claude Code?
Run `npx skills add AI4Scientist/nano-scientist --skill specification-writing -a claude-code`. Or copy the skill folder (skills/specification-writing in AI4Scientist/nano-scientist) into .claude/skills/specification-writing in your project. Claude Code loads it when a task matches its description.
How do I install Specification Writing in Codex?
Run `npx skills add AI4Scientist/nano-scientist --skill specification-writing -a codex`. Or copy the skill folder (skills/specification-writing in AI4Scientist/nano-scientist) into .agents/skills/specification-writing in your project. Codex loads it when a task matches its description.
Can I use Specification Writing 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 AI4Scientist/nano-scientist --skill specification-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specification-writing, .gemini/skills/specification-writing, .github/skills/specification-writing and .opencode/skills/specification-writing in your project.
What does Specification Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Specification Writing is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply.
Does Specification Writing 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 Specification Writing safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Specification Writing use?
No licence was found for Specification Writing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Specification Writing use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Specification Writing?
Skills that share tags, products or a category with Specification Writing: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 106 stars), Patent Examine (gfodor/legal-skills, 393 stars) and Patent Audit (gfodor/legal-skills, 393 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specification Writing?
AI4Scientist (a GitHub organization) maintains it in AI4Scientist/nano-scientist, which has 128 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on June 3, 2026.
Source: AI4Scientist/nano-scientist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.