specification-writing

Generate jurisdiction-aware patent specification sections from claims and invention disclosure.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Shallow-W/llm-wiki --skill specification-writing-shallow-w
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specification-writing
Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/specification-writing
Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill specification-writing-shallow-w

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns your drafted claims and invention disclosure into a full, filing-style patent specification, including the required sections like technical field, background, summary, drawings description, detailed description, and abstract.

Core Features & Use Cases

  • Section-by-section patent drafting: Produces each specification section in the correct order and structure derived from your claims and disclosure.
  • Jurisdiction-aware formatting: Adapts language and section conventions based on detected or specified jurisdiction (e.g., CN vs US/EP).
  • Claim support verification and quality review: Ensures every claim element is supported in the detailed description and runs a completeness-focused review pass.

Quick Start

Ask the skill to write a full patent specification by providing the claims file path and ensuring the invention disclosure and (optionally) prior art report are available in the expected patent/ directory.

Frequently Asked Questions about specification-writing

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

FAQPage Schema
How do I draft a complete patent specification from claims?

To draft a patent specification from claims, you provide the drafted claims and invention disclosure in a patent directory, and the skill generates all filing-ready sections including background, summary, detailed description, and abstract.

What sections are needed for a filing-ready patent specification?

A filing-ready patent specification requires a technical field, background, summary, drawings description, detailed embodiments, and an abstract, all structured around the drafted claims and mapped solutions.

Can I generate patent specifications formatted for different jurisdictions like CN or US/EP?

Yes, jurisdiction-aware formatting adapts the patent specification language and section conventions automatically based on the detected or specified jurisdiction, such as CN versus US/EP filing requirements.

How do I verify claim support in a detailed patent description?

Claim support verification runs a completeness-focused review pass to ensure every claim element from the drafted claims is explicitly supported in the detailed description and maintains numeral consistency.

What is the best way to map invention disclosure solutions into a patent background section?

Mapping invention disclosure solutions involves framing the background technical problem and mapping the summary to the solution, directly deriving the narrative structure from the drafted claims and prior art.

Do I need a prior art report to generate a patent specification?

A prior art report is optional for generating a patent specification, but having it available in the expected patent directory alongside the claims and invention disclosure improves background framing and completeness.