Skip to content
Back to skills

Assess Patent Claim Scope

ASecurity

Assess protection breadth, limiting elements, support, overlap, design-around vulnerability, and likely scope uncertainty for a patent claim without making legal conclusions beyond the evidence.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
research

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill assess-patent-claim-scope --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Assess Patent Claim Scope?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Assess Patent Claim Scope
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-assess-patent-claim-scope/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-assess-patent-claim-scope)

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

Download with Pro
SKILL.md
---
name: assess-patent-claim-scope
description: "Assess protection breadth, limiting elements, support, overlap, design-around vulnerability, and likely scope uncertainty for a patent claim without making legal conclusions beyond the evidence."
---

# assess-patent-claim-scope

## Purpose

Assess claim breadth, limiting elements, support, overlap, design-around vulnerability, and scope uncertainty without making a legal conclusion beyond the evidence.

## Input contract

```yaml
required: [parsed_claim, cited_support, jurisdiction_scope]
optional: [related_claims, family_map, prior_art_records]
constraints: [each scope judgment must identify claim language, support, jurisdiction, and uncertainty]
```

## Procedure

1. Separate mandatory, optional, functional, and contextual claim elements.
2. Map each element to disclosed support and identify limiting combinations.
3. Compare overlap and distinction against related claims and declared prior-art records.
4. Record design-around paths and unresolved interpretation questions.

## Output contract

```yaml
produces: [element_scope_map, support_map, overlap_assessment, design_around_options, scope_uncertainties]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
```

## Quality gates

- Mandatory elements and jurisdiction are explicit.
- Overlap claims cite the compared claim language.
- Unclear terms remain uncertainty markers.

## Failure and counterexamples

Do not infer broad protection from a title or abstract, and do not treat technical similarity as claim overlap.

## Provenance map

- `resolved: knowledge-acquisition-claim-analysis`
- `resolved: quality-scoring`

Attribution

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

Loading comments…