Skip to content
Back to skills

Parse Patent Claim

ASecurity

Parse independent/dependent claim structure, extract elements, and map claim features to technical functions/domains.

  • 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 parse-patent-claim --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Parse Patent Claim?

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

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

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: parse-patent-claim
description: "Parse independent/dependent claim structure, extract elements, and map claim features to technical functions/domains."
---

# parse-patent-claim

## Purpose

Parse independent and dependent claim structure, extract elements, and map claim features to technical functions or domains.

## Input contract

```yaml
required: [claim_text, claim_set]
optional: [technical_ontology, family_context, jurisdiction]
constraints: [element boundaries, dependency links, and source spans must be retained]
```

## Procedure

1. Identify independent claims and dependency relations.
2. Segment each claim into required elements, limitations, and functional language.
3. Map elements to technical functions and preserve alternative interpretations.
4. Emit a source-linked claim-element graph.

If claim elements, dependencies, and limiting language are parsed, consider `assess-patent-claim-scope` as the next tactic.

## Output contract

```yaml
produces: [claim_element_map, dependency_graph, function_map, interpretation_alternatives]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]
```

## Quality gates

- Every element points to a claim span.
- Dependency and optionality are not conflated.

## Failure and counterexamples

Do not paraphrase away limiting language or treat a dependent claim as independent coverage.

## Provenance map

- `resolved: claim-parsing`
- `resolved: knowledge-acquisition-claim-decomposition`

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…