skills.rest
raja21068
raja21068COMMUNITY
Explore all skills by this author →
WebsiteGitHub

specification-writing

Generate jurisdiction-formatted patent specification markdown from claims and invention disclosure.

2|1|Updated Apr 19, 2026
Search Tags:#specification#claims#patent#legal drafting#jurisdiction formatting#written description#technical disclosure
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill specification-writing-raja21068
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification-writing
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/specification-writing
Command: npx skills add https://github.com/raja21068/AutoResearch --skill specification-writing-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a full patent specification (not just claims) from scattered inputs is slow, inconsistent, and often misses required sections and claim support details.

Core Features & Use Cases

  • Section-by-section patent drafting: Produces a complete specification structure including title, technical field, background, summary, drawings description, detailed description, and abstract.
  • Jurisdiction-aware formatting: Adapts language and output rules for CN/US/EP styles so the draft matches expected filing conventions.
  • Claim support verification loop: Ensures every claim element is supported in the detailed description before finalizing the output.
  • Quality review for completeness: Uses an external reviewer model to check enablement, written description support, consistency, and missing embodiments.

Quick Start

Use specification-writing to generate the full patent specification from your existing files 'patent/CLAIMS.md' and 'patent/INVENTION_DISCLOSURE.md'.

Frequently Asked Questions about specification-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I format a patent specification for different jurisdictions like US, CN, and EP?▼

Yes, jurisdiction-aware formatting adapts language and output rules for CN, US, and EP patent filing conventions. The generated specification matches the expected structural and stylistic requirements for the selected jurisdiction.

What is the best way to ensure patent specification completeness and enablement?▼

Claim support verification ensures every claim element is explicitly supported in the detailed description before finalizing the patent specification. This loop checks that the drafted technical disclosure aligns with the provided claims to meet written description requirements.

Do I need existing claims and technical disclosure files to generate a patent specification?▼

To ensure patent specification completeness, an external reviewer model checks enablement, written description support, consistency, and missing embodiments. This quality review validates that all required sections and claim support details are present before output.

Do I need existing claims and technical disclosure files to generate a patent specification?▼

Yes, you need existing 'patent/CLAIMS.md' and 'patent/INVENTION_DISCLOSURE.md' files as inputs to generate the full patent specification. These source files provide the necessary claim elements and technical context for drafting the complete document.

Related Skills

Explore More Legal & Compliance Skills→
dogekikidogekiki

specification-writing

Generate patent specification sections from claims and invention disclosures.

Community
Advanced
Mang30Mang30

jurisdiction-format

Compile patent drafts into CN, US, and EP filing documents.

Community
Intermediate
xqinagxqinag

claims-drafting

Draft patent claims in CN, US, and EP formats from invention disclosures.

Community
Advanced
modu-aimodu-ai
267

patent-analyzer

Analyze patent portfolios and technical trends from patent datasets.

Official
Advanced