patent-application-creator

robthepcguy/claude-patent-creator · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/robthepcguy/claude-patent-creator --skill patent-application-creator
0 commentsdiscussion
summary

Complete end-to-end patent application creation from invention disclosure to USPTO-ready filing.

skill.md

Patent Application Creator Skill

Complete end-to-end patent application creation from invention disclosure to USPTO-ready filing.

When to Use

Invoke this skill when users ask to:

  • Create a complete patent application
  • Draft a provisional patent application
  • Prepare a utility patent application
  • Write patent claims and specification
  • Generate a full patent filing package

What This Skill Does

Orchestrates the complete patent creation workflow:

  1. Prior Art Search → Identify existing patents
  2. Claims Drafting → Write independent and dependent claims
  3. Specification Writing → Create detailed description
  4. Diagram Generation → Produce technical figures
  5. Abstract Creation → Write concise summary
  6. Compliance Checking → Validate USPTO requirements
  7. IDS Preparation → List prior art for disclosure

Complete Workflow

Phase 1: Discovery & Research (15-30 min)

  1. Invention Interview:

    • Get detailed invention description from user
    • Extract key features and novel aspects
    • Identify problem being solved
    • List all components/steps
  2. Prior Art Search:

    • Use Prior Art Search skill (7-step methodology)
    • Find 10-20 most relevant patents
    • Document key differences
    • Assess patentability
  3. Technology Landscape:

    • Identify CPC classifications
    • Review competing approaches
    • Find terminology used in field

Output: Research summary with prior art analysis


Phase 2: Claims Drafting (20-40 min)

  1. Claim Strategy:

    • Define claim scope based on prior art
    • Identify distinguishing features
    • Plan independent/dependent structure
    • Choose claim types (system, method, etc.)
  2. Independent Claims:

    • Draft 1-3 broad independent claims
    • Use preamble-transition-body structure
    • Include all essential elements
    • Distinguish from prior art
  3. Dependent Claims:

    • Add 10-20 dependent claims
    • Cover specific implementations
    • Add fall-back positions
    • Include preferred embodiments
  4. Claim Review:

    • Use Patent Claims Analyzer skill
    • Check antecedent basis
    • Fix definiteness issues
    • Validate dependencies

Output: Complete claims section (20-25 claims)


Phase 3: Specification Writing (40-90 min)

  1. Title:

    • Clear, descriptive (< 500 characters)
    • Matches invention scope
    • Includes key technology terms
  2. Field of the Invention:

    • 1-2 paragraphs
    • Describe technical field
    • Reference relevant classifications
  3. Background:

    • Problem statement (2-3 paragraphs)
    • Limitations of existing solutions
    • Need for invention
    • Cite prior art from search
  4. Summary:

    • High-level description (3-5 paragraphs)
    • Main features and advantages
    • How it solves the problem
    • Independent claims in prose
  5. Brief Description of Drawings:

    • List each figure
    • One sentence per figure
    • Reference numbers introduced
  6. Detailed Description:

    • Complete description of all embodiments
    • Multiple embodiments (preferred + variations)
    • Step-by-step for methods
    • Component-by-component for systems
    • Reference numbers throughout
    • Support ALL claim elements (35 USC 112(a))
  7. Examples/Embodiments:

    • Specific implementations
    • Working examples
    • Alternative designs
  8. Advantages/Benefits:

    • List key advantages
    • Explain improvements over prior art
  9. Specification Review:

    • Use Patent Claims Analyzer skill (specification mode)
    • Verify all claims are supported
    • Check enablement
    • Validate completeness

Output: Complete specification (20-50 pages)


Phase 4: Diagrams & Figures (15-30 min)

  1. Identify Figures Needed:

    • System block diagrams
    • Method flowcharts
    • Component details
    • Alternative embodiments
  2. Generate Diagrams:

    • Use Patent Diagram Generator skill
    • Create all required figures
    • Add reference numbers (10, 20, 30...)
    • Ensure clarity
  3. Figure Descriptions:

    • Write detailed figure descriptions
    • Explain all reference numbers
    • Describe relationships between components

Output: 3-10 patent figures (SVG/PNG/PDF)


Phase 5: Abstract & Front Matter (10-15 min)

  1. Abstract:

    • 50-150 words (USPTO requirement)
    • Single paragraph
    • No claim limitations
    • Broad technical description
  2. Title Page Info:

    • Inventors
    • Assignee
    • Correspondence address
    • Prior applications (if any)
  3. Cross-References:

    • Related applications
    • Priority claims
    • Provisional references

Output: Complete front matter


Phase 6: Compliance & Validation (15-20 min)

  1. Formalities Check:

    • Use Patent Claims Analyzer skill (formalities mode)
    • Abstract length: 50-150 words
    • Title length: < 500 characters
    • Required sections present
    • Drawing references valid
  2. Claims Compliance:

    • 35 USC 112(b) definiteness
    • Antecedent basis correct
    • No indefinite terms
    • Proper dependencies
  3. Specification Compliance:

    • 35 USC 112(a) written description
    • Enablement complete
    • Best mode disclosed
    • All claims supported
  4. MPEP Guidance:

    • Use MPEP Search skill
    • Verify format requirements
    • Check section 608 compliance
    • Review any special requirements

Output: Compliance report with fixes


Phase 7: Final Assembly (10-15 min)

  1. Document Assembly:

    • Title page
    • Abstract
    • Drawings (brief description)
    • Specification
    • Claims
    • Abstract (at end)
  2. IDS Preparation:

    • List all prior art from search
    • Include publication numbers
    • Add filing/grant dates
    • Note relevance
  3. Filing Package:

    • Specification document
    • Claims document
    • Figures (separate files)
    • IDS form data
    • Assignment (if applicable)

Output: USPTO-ready filing package


Document Templates

Specification Structure

[TITLE]

FIELD OF THE INVENTION

[Technical field description]

BACKGROUND

[Problem statement and prior art]

SUMMARY

[High-level invention description]

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates...
FIG. 2 shows...
FIG. 3 depicts...

DETAILED DESCRIPTION

[Comprehensive description with reference numbers]

First Embodiment

[Detailed description of main embodiment]

Second Embodiment

[Alternative embodiment]

Examples

[Working examples]

ADVANTAGES

[Key benefits and improvements]

CONCLUSION

[Broad scope statement]

CLAIMS

[Claims section]

Claims Structure

What is claimed is:

1. A [system/method/apparatus] for [purpose], comprising:
    a [first element];
    a [second element]; and
    wherein [novel relationship/function].

2. The [system/method/apparatus] of claim 1, wherein [additional limitation].

3. The [system/method/apparatus] of claim 1, wherein [alternative limitation].

...

[Continue through all claims]

Quality Checklist

Before finalizing, verify:

  • Prior art search completed (Top 10 documented)
  • Claims drafted (1-3 independent, 10-20 dependent)
  • Specification written (20+ pages)
  • All claim elements supported in specification
  • Diagrams created (3+ figures with reference numbers)
  • Abstract written (50-150 words)
  • Title created (< 500 characters)
  • Antecedent basis checked (no critical issues)
  • Definiteness verified (no indefinite terms)
  • Enablement complete (sufficient detail)
  • Formalities compliant (MPEP 608)
  • IDS list prepared (all prior art included)
  • Figures match description
  • Reference numbers consistent
  • USPTO format requirements met

File Organization

patent-application/
├── 01-research/
│   ├── prior-art-search.md
│   ├── top-10-patents.md
│   └── patentability-assessment.md
├── 02-claims/
│   ├── claims-draft-v1.md
│   ├── claims-final.md
│   └── claims-analysis-report.md
├── 03-specification/
│   ├── specification-outline.md
│   ├── specification-full.md
│   └── specification-review.md
├── 04-diagrams/
│   ├── fig1-system-diagram.svg
│   ├── fig2-method-flowchart.svg
│   ├── fig3-component-detail.svg
│   └── figures-list.md
├── 05-front-matter/
│   ├── abstract.md
│   ├── title.md
│   └── bibliographic-data.md
├── 06-compliance/
│   ├── formalities-check.md
│   ├── claims-compliance.md
│   └── spec-compliance.md
└── 07-filing-package/
    ├── complete-specification.pdf
    ├── claims.pdf
    ├── drawings.pdf
    └── ids-list.md

Integration with Other Skills

This workflow orchestrates:

  • Prior Art Search skill (Phase 1)
  • Patent Claims Analyzer skill (Phase 2, 6)
  • Patent Diagram Generator skill (Phase 4)
  • MPEP Search skill (Phase 6)
  • BigQuery Patent Search skill (Phase 1)

Estimated Timeline

Provisional Application (Lighter requirements):

  • Research: 15 min
  • Claims: 20 min
  • Specification: 40 min
  • Diagrams: 15 min
  • Total: ~90 minutes

Utility Application (Full formal requirements):

  • Research: 30 min
  • Claims: 40 min
  • Specification: 90 min
  • Diagrams: 30 min
  • Compliance: 20 min
  • Total: ~3.5 hours

User Interaction Points

Throughout the workflow, pause to:

  1. After Research: Present patentability assessment, ask if should proceed
  2. After Claims: Show draft claims, get feedback on scope
  3. After Specification Outline: Review structure before full writing
  4. After Diagrams: Confirm figures match invention description
  5. After Compliance: Show any issues found, make fixes
  6. Before Final: Present complete package for review

Tools Available

  • Bash: Run Python tools for search, analysis
  • Write: Save all documents and sections
  • Read: Load user invention descriptions, prior art
  • Grep: Search through generated content
how to use patent-application-creator

How to use patent-application-creator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add patent-application-creator
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/robthepcguy/claude-patent-creator --skill patent-application-creator

The skills CLI fetches patent-application-creator from GitHub repository robthepcguy/claude-patent-creator and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/patent-application-creator

Reload or restart Cursor to activate patent-application-creator. Access the skill through slash commands (e.g., /patent-application-creator) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.666 reviews
  • Nia Abbas· Dec 24, 2024

    patent-application-creator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya Huang· Dec 24, 2024

    patent-application-creator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Jin Abbas· Dec 16, 2024

    patent-application-creator reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kiara Okafor· Dec 16, 2024

    Solid pick for teams standardizing on skills: patent-application-creator is focused, and the summary matches what you get after install.

  • Henry Thompson· Dec 12, 2024

    We added patent-application-creator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Jin Farah· Dec 8, 2024

    Registry listing for patent-application-creator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 4, 2024

    patent-application-creator reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • James Jackson· Nov 27, 2024

    Useful defaults in patent-application-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Oshnikdeep· Nov 23, 2024

    I recommend patent-application-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Carlos Park· Nov 19, 2024

    patent-application-creator has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 66

1 / 7