embodiment-description

Write detailed patent embodiment descriptions supporting drafted claims with consistent reference numerals.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill embodiment-description-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embodiment-description
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/embodiment-description
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill embodiment-description-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting the detailed description section of a patent specification is labor-intensive and error-prone: every claim element needs embodiment support, reference numerals must stay consistent with figures, and experimental language from source papers must be excluded. This Skill structures that drafting process into a repeatable workflow. ## Core Features & Use Cases - Embodiment Planning: Maps each claim category (method, system, apparatus) to one or more embodiments, including a best-mode embodiment. - Reference Numeral Management: Enforces consistent numeral usage (100-series for FIG. 1, etc.) with first-mention parentheses formatting. - Claim Support Verification: Builds a mapping table confirming every claim element appears in at least one embodiment. - Use Case: Given an invention disclosure and drafted claims for a sensor device, generate a detailed description with three embodiments covering the preferred implementation and alternatives, written as manufacturing/operation instructions rather than experimental results. ## Quick Start Write detailed patent embodiments based on the claims in patent/CLAIMS.md and the invention disclosure in patent/INVENTION_DISCLOSURE.md.

Frequently Asked Questions about embodiment-description

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

FAQPage Schema
How do I write a detailed description for a patent specification?

Plan at least one embodiment per claim category, then describe each component or step with reference numerals tied to figures. Include variations and alternatives to support broader claim interpretation, and verify every claim element appears in at least one embodiment.

How many embodiments should a patent specification include?

At least one complete embodiment is required, with up to three being a practical limit. Multiple embodiments strengthen enablement, and at least one should represent the best mode of practicing the invention.

Can patent embodiments include experimental results or accuracy data?

No. Embodiments describe how to make and use the invention, not how well it performs. Experimental data, accuracy percentages, detection rates, and comparative performance tables belong in papers, not patent specifications.

How should reference numerals be formatted in patent descriptions?

On first mention, place the numeral in parentheses after the component name, such as "the processor (102)". Subsequent references drop the parentheses. Numbering follows figure series: 100-series for FIG. 1, 200-series for FIG. 2.

What inputs are needed to draft patent embodiments?

The workflow expects an invention disclosure decomposing core and optional features, drafted claims the embodiments must support, and optionally user-provided figures plus a numeral index from prior figure description work.