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.
Strategic drafting patterns and claim scope design guide for patent claims.
Install Claim Drafting Patterns
$ npx skills add revfactory/harness-100 --skill claim-drafting-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 claim-drafting-patterns --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/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .claude/skills/claim-drafting-patterns && 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 "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .claude/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patternsType 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 revfactory/harness-100 --skill claim-drafting-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 claim-drafting-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .agents/skills/claim-drafting-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .agents/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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 revfactory/harness-100 --skill claim-drafting-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 claim-drafting-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .cursor/skills/claim-drafting-patterns && 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 "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .cursor/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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/revfactory/harness-100.git --path en/68-patent-drafter/.claude/skills/claim-drafting-patterns--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 revfactory/harness-100 --skill claim-drafting-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 claim-drafting-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .gemini/skills/claim-drafting-patterns && 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 "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .gemini/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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 revfactory/harness-100 claim-drafting-patternsInstalls 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 revfactory/harness-100 --skill claim-drafting-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .github/skills/claim-drafting-patterns && 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 "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .github/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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 revfactory/harness-100 --skill claim-drafting-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 claim-drafting-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/68-patent-drafter/.claude/skills/claim-drafting-patterns .opencode/skills/claim-drafting-patterns && 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 "claim-drafting-patterns" agent skill from https://github.com/revfactory/harness-100/tree/main/en/68-patent-drafter/.claude/skills/claim-drafting-patterns into .opencode/skills/claim-drafting-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claim-drafting-patterns", 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
claim-drafting-patterns- GitHub stars
- 1.3k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 239 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Strategic drafting patterns and claim scope design guide for patent claims.
- Tasks that involve Intellectual property
- SKILL.md covers Drafting Patterns by Claim Type, Claim Scope Design Strategy, Terminology Rules and Rejection Response Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Claim Drafting Patterns is an agent skill from revfactory/harness-100. Strategic drafting patterns and claim scope design guide for patent claims. The 'claim-drafter' and 'patent-reviewer' agents must use this skill's drafting patterns, terminology rules, and dependent claim strategies when writing or verifying claims. Used for 'claim drafting', 'claim scope design', 'dependent claim strategy', etc. Note: Overall patent orchestration or prior art search is outside the scope of this skill.
Its SKILL.md is about 1.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 licence is Apache-2.0.
When your agent uses it
- Tasks that involve Intellectual property
Example prompts
- “claim-drafter”
- “patent-reviewer”
- “claim drafting”
- “/claim-drafting-patterns”
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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
Claim Drafting Patterns loads about 1.2k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 239 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 passed
The automated check found no risky patterns in SKILL.md.
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
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 239 words, ~1,200 tokens.
Download SKILL.mdSave it as
.claude/skills/claim-drafting-patterns/SKILL.md (or your agent's skills folder).- name
- claim-drafting-patterns
- description
- Strategic drafting patterns and claim scope design guide for patent claims. The 'claim-drafter' and 'patent-reviewer' agents must use this skill's drafting patterns, terminology rules, and dependent claim strategies when writing or verifying claims. Used for 'claim drafting', 'claim scope design', 'dependent claim strategy', etc. Note: Overall patent orchestration or prior art search is outside the scope of this skill.
Claim Drafting Patterns — Claim Drafting Pattern Guide
Strategic composition, terminology selection, and claim scope optimization methodology for patent claims.
Drafting Patterns by Claim Type
Apparatus (Article) Claim Structure
In a [title of invention],
[Component A];
[Component B] connected to said [Component A] and performing [Function 1]; and
[Component C] receiving [data/signal] from said [Component B] and performing [Function 2],
comprising [title of invention].Method (Process) Claim Structure
A method for [purpose], comprising:
(a) a step of [subject] performing [Action 1];
(b) a step of performing [Action 2] based on the result of step (a); and
(c) a step of performing [Action 3] according to [condition].Computer Program Claim
A non-transitory computer-readable recording medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising:
performing [Action 1];
performing [Action 2]; and
performing [Action 3].Claim Scope Design Strategy
Hierarchical Claim Structure (Claim Tree)
Independent Claim 1 (Apparatus — broadest)
+-- Dependent Claim 2: Component A elaboration
+-- Dependent Claim 3: Component B elaboration
+-- Dependent Claim 4: Connection method limitation
+-- Dependent Claim 5: Additional Component D inclusion
Independent Claim 6 (Method — broadest)
+-- Dependent Claim 7: Step subdivision
+-- Dependent Claim 8: Condition addition
+-- Dependent Claim 9: Additional step
Independent Claim 10 (Recording medium)Scope Adjustment Techniques
| Technique | Description | Example |
|---|---|---|
| Generalization | Use broader terms that encompass specific implementations | "sensor" -> "detection means" |
| Functional Expression | Define by function instead of structure | "means for storing data" |
| Open Transition | Use "comprising" | Allows additional elements beyond those listed |
| Optional Limitation | "Preferably" in dependent claims | Maintains independent claim scope |
| Numerical Range | Broad range -> Narrow range hierarchy | Independent "1-100", Dependent "10-50" |
Terminology Rules
Expressions to Avoid
| Prohibited Expression | Problem | Alternative |
|---|---|---|
| "about", "approximately" | Scope unclear (description deficiency) | Specify numerical range |
| "such as", "etc." | Range unspecified | Specific enumeration or broader concept |
| "optimal", "superior" | Subjective, no comparison basis | Present objective criteria |
| "conventional", "existing" | Unclear time reference | Specify particular technology |
| "as needed" | Arbitrary composition | Specify conditions |
Antecedent Rules
First appearance: "a [component]" or "[component]"
Re-appearance: "said [component]" or "the [component]" (same term)
Violation example: "sensor" -> "said detector" (name mismatch = description deficiency)Rejection Response Patterns
Novelty Rejection (Article 29, Paragraph 1)
Response strategy:
1. Identify differentiating elements from prior art
2. Add differentiating elements to independent claim (amendment)
3. Argue technical significance of differences in opinion statement
4. Merge dependent claims to narrow scope (fallback)Inventive Step Rejection (Article 29, Paragraph 2)
Response strategy:
1. Argue lack of combination motivation: "There is no motivation to combine the prior art references"
2. Argue unexpected effects: "The combination produces synergistic effects"
3. Argue technical prejudice: "A direction a person skilled in the art would not attempt"
4. Commercial success evidence: "Market success demonstrates inventive step"Claim Self-Check Checklist
- Does the independent claim cover the broadest scope
- Are all term antecedents clear
- Is the transition phrase open-ended ("comprising")
- Do dependent claims progressively narrow the scope
- Is there a 3-type claim set (apparatus + method + recording medium)
- Are all specification embodiments covered by claims
- Do reference numerals match specification and drawings
Notes
- Based on Patent Act and examination guidelines
- Detailed drafting examples: See
references/claim-examples.md
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/68-patent-drafter/.claude/skills/claim-drafting-patterns of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Claim Drafting Patterns 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 |
|---|---|---|---|---|---|---|
| Claim Drafting Patterns this skillrevfactory/harness-100 | 1.3k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 46k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 105 | 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 | |
| Patent Workaroundgfodor/legal-skills | 393 | — | ~5.7k | Automated safety check: Pass | GPL-3.0 |
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.
Patent Workaround
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
Design Information Prep
SeanJ1ang/design-judge-skills
Extract evidence-grounded project facts from user-provided design attachments, identify missing information, and prepare the exact written fields required by supported design-award entry forms.
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Claim Drafting Patterns
What does Claim Drafting Patterns do?
Strategic drafting patterns and claim scope design guide for patent claims. Claim Drafting Patterns is an agent skill from revfactory/harness-100. Strategic drafting patterns and claim scope design guide for patent claims.
When should I use Claim Drafting Patterns?
Claim Drafting Patterns fits situations like: tasks that involve Intellectual property.
How do I install Claim Drafting Patterns in Claude Code?
Run `npx skills add revfactory/harness-100 --skill claim-drafting-patterns -a claude-code`. Or copy the skill folder (en/68-patent-drafter/.claude/skills/claim-drafting-patterns in revfactory/harness-100) into .claude/skills/claim-drafting-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Claim Drafting Patterns in Codex?
Run `npx skills add revfactory/harness-100 --skill claim-drafting-patterns -a codex`. Or copy the skill folder (en/68-patent-drafter/.claude/skills/claim-drafting-patterns in revfactory/harness-100) into .agents/skills/claim-drafting-patterns in your project. Codex loads it when a task matches its description.
Can I use Claim Drafting Patterns 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 revfactory/harness-100 --skill claim-drafting-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claim-drafting-patterns, .gemini/skills/claim-drafting-patterns, .github/skills/claim-drafting-patterns and .opencode/skills/claim-drafting-patterns in your project.
What does Claim Drafting Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Claim Drafting Patterns is instructions for the agent only.
Does Claim Drafting Patterns 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 Claim Drafting Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Claim Drafting Patterns use?
Claim Drafting Patterns is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Claim Drafting Patterns use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Claim Drafting Patterns?
Skills that share tags, products or a category with Claim Drafting Patterns: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 46k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 105 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 Claim Drafting Patterns?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.