patent
by alirezarezvani (GitHub) in alirezarezvani/claude-skills
What it does
Patent prior-art and landscape intelligence skill - not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacen
Quoted from the skill's SKILL.md under its MIT license.
Install
git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git /tmp/claude-skills mkdir -p ~/.claude/skills/ cp -r /tmp/claude-skills/research/patent/skills/patent ~/.claude/skills/patent
The command copies the skill from the author's repo. SkillTrove does not host it.
Files
- SKILL.md
- references/cpc_classification_canon.md
- references/legal_disclaimer_discipline.md
- references/sub_use_case_routing.md
- scripts/citation_tracker.py
- scripts/family_resolver.py
- scripts/sub_use_case_router.py
Source: https://github.com/alirezarezvani/claude-skills/tree/main/research/patent/skills/patent. Checked 2026-10-13.
Similar skills
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to ...
constraint-driven-development
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane...
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing publ...
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceedi...
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a mess...
incremental-implementation
Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up th...