Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Patent

ASecurity

Patent research and IP landscape skill. Covers prior-art search strategy, claim mapping, landscape analysis, freedom-to-operate assessment, and patentability scoring. Use when conducting a prior-art search, mapping the IP landscape of a technology area, evaluating patentability of an invention, or running an FTO analysis before product launch.

847 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentspythongobashdatabase

Security Analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned 5/29/2026

$npx -y skills add borghei/Claude-Skills --skill patent --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Patent?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Patent
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/borghei-patent/badge)](https://www.skillsdirectory.com/skills/borghei-patent)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: patent
description: >
  Patent research and IP landscape skill. Covers prior-art search
  strategy, claim mapping, landscape analysis, freedom-to-operate
  assessment, and patentability scoring. Use when conducting a prior-art
  search, mapping the IP landscape of a technology area, evaluating
  patentability of an invention, or running an FTO analysis before
  product launch.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: research
  domain: research
  updated: 2026-05-27
  tags: [patent, ip, prior-art, freedom-to-operate, patentability, claims, landscape]
---

# Patent Research

A research-focused patent skill (not legal filing). Covers prior-art
search, IP landscape mapping, claim analysis, freedom-to-operate, and
patentability. For formal patent prosecution, work with a licensed
patent attorney.

## When to use this skill

- Conducting a **prior-art search** before filing a provisional patent
- Mapping the **IP landscape** in a technology area
- Evaluating the **patentability** of an invention
- Assessing **freedom-to-operate** before launching a product
- Tracking **competitive patent activity** in a market
- Preparing a **patent strategy** for a startup or R&D group

## Inputs the advisor expects

- Invention description (problem, solution, novelty)
- Technology area + relevant CPC/IPC classifications
- Target jurisdictions (US, EU, JP, CN — IP is jurisdictional)
- Existing prior art known (key references)
- Competitor list
- Timeline pressure (filing deadline, product launch)

## Workflows

### Workflow 1 — Plan a prior-art search

1. Define invention claims (key novel features).
2. Identify search classifications (CPC / IPC) + keywords.
3. Run `prior_art_search_planner.py` to produce a search plan.
4. Execute on USPTO / EPO / Espacenet / Google Patents / WIPO.

```bash
python3 patent/scripts/prior_art_search_planner.py \
  --input invention.json --format markdown
```

### Workflow 2 — Map the IP landscape

1. Capture identified patents (yours, competitors', adjacent).
2. Run `claim_landscape_mapper.py` to cluster by claim type, owner,
   technology subarea, recency; surface white space + crowded areas.

```bash
python3 patent/scripts/claim_landscape_mapper.py \
  --input patents.json --format markdown
```

### Workflow 3 — Score patentability of an invention

1. Capture invention + closest prior art.
2. Run `patentability_scorer.py` to rate novelty, non-obviousness,
   utility, subject matter eligibility.

```bash
python3 patent/scripts/patentability_scorer.py \
  --input patentability.json --format markdown
```

## Decision frameworks

### The three patentability criteria (US baseline)
1. **Novelty** (35 USC §102): not previously disclosed
2. **Non-obviousness** (35 USC §103): not obvious to person skilled in the art
3. **Utility** (35 USC §101): useful, with practical application

Plus:
- **Subject matter eligibility** (§101): not abstract idea, not law of nature
- **Enablement** (§112): described well enough to be made by skilled artisan
- **Definiteness** (§112): claims clearly distinguish

### Prior-art categories
- **Patents** (issued + published applications)
- **Non-patent literature** (papers, conference, dissertations, technical reports)
- **Commercial products** (sold publicly before filing)
- **Public disclosures** (talks, demos, blog posts — yes, including your own > 1 year prior)
- **Sales activity** (offers for sale, even pre-launch)

Inventors often miss non-patent prior art; this is where searches break.

### Freedom-to-operate (FTO)
Different from patentability. FTO asks: can I commercialize without
infringing someone else's patent?

- Patentability ≠ FTO (your patent could still infringe another)
- FTO is jurisdiction-specific
- Active patents only (not expired); typically 20 years from filing
- Patent attorney involvement essential for formal opinion

### IP strategy by stage
- **Pre-seed:** capture inventions; consider provisional filings; don't over-file
- **Seed/Series A:** strategic provisionals; key utility filings
- **Series B+:** PCT international; continuations to maintain pendency
- **Mature:** portfolio management; licensing; enforcement

## Common engagements

### "We have a new algorithm. Should we patent?"
1. Subject matter eligibility check (§101 — algorithms are tricky)
2. Prior art search (someone has probably published)
3. Strategic value (does patent enable / defend a business position?)
4. Cost-benefit ($5-25K provisional; $30-100K full prosecution)
5. Often answer: keep as trade secret, not patent

### "Run an FTO before our launch"
1. Identify candidate blocking patents (search + competitor review)
2. For each: review claims; assess infringement risk
3. Identify mitigations: design-around, license, abandon, challenge
4. Get formal opinion from patent counsel (insurance against willful infringement)

### "Map the patent landscape in our space"
1. Identify key players (companies + universities)
2. Search by classification + keyword
3. Cluster: by company, by sub-technology, by year
4. Surface white space (uncovered areas) + crowded zones
5. Strategy implications (where to play, where to design-around)

## Anti-patterns to avoid

- **Searching only keywords (no classification).** Misses translations + synonyms.
- **Searching only USPTO.** EPO + WIPO + JP have unique art.
- **Searching only patents.** Non-patent prior art is huge.
- **Public disclosure before filing.** Loses patentability outside US (1-year grace in US only).
- **Filing without prior-art search.** Reviewer finds it; patent invalid.
- **No FTO before product launch.** Surprise injunctions.
- **Patenting everything.** $30K per patent adds up; portfolio bloat distracts.
- **Filing without commercial strategy.** Patents are means, not ends.

## References

- `references/prior-art-search-strategy.md` — search databases, classifications, query patterns
- `references/claim-mapping-and-landscape.md` — claim analysis, landscape visualization
- `references/freedom-to-operate-and-patentability.md` — FTO process, patentability criteria

## Related skills

- `legal/contract-review` — IP licensing contracts
- `c-level-advisor/general-counsel-advisor` — strategic IP counsel
- `research/litreview` — non-patent literature search overlap

Attribution

borgheiborghei
View sourceSee grades on GitHubMore from borghei →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →