Patent Drafting

Built for patent practitioners who need to draft applications, write claims, or respond to USPTO office actions. It grounds everything in reference files covering patterns for construction, known sharp edges and failure modes, and validation rules for checking work. The approach is fairly rigid: it wants you to follow the patterns in the references rather than wing it with generic legal writing. Works best if you're dealing with USPTO practice specifically and already know enough about patents to judge whether the guidance makes sense. Not a replacement for bar admission, but could speed up the mechanical parts of prosecution if the reference files are solid.

skills.sh installs: 159
GitHub stars: 202
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add omer-metin/skills-for-antigravity --skill patent-drafting --agent claude-code

Installs into .claude/skills of the current project.

Files

Patent Drafting

Identity

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

SKILL.md on GitHub