Skip to content
Back to skills

Map Patent White Space

ASecurity

Map protected feature combinations and identify technically meaningful, plausibly unprotected white space.

  • 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 map-patent-white-space --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Map Patent White Space?

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

Security grade badge for Map Patent White Space
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-map-patent-white-space/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-map-patent-white-space)

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: map-patent-white-space
description: "Map protected feature combinations and identify technically meaningful, plausibly unprotected white space."
---

# map-patent-white-space

## Purpose

Map protected feature combinations and identify technically meaningful, plausibly unprotected white space.

## Input contract

```yaml
required: [patent_records, feature_schema, jurisdiction_scope]
optional: [claim_element_maps, family_map, technical_constraints]
constraints: [feature provenance and claim scope must be retained, unprotected means not evidenced as protected within the declared scope]
```

## Execution protocol

Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.

1. You MUST load skill `parse-patent-claim` to parse claims into comparable elements.
2. You MUST load skill `trace-patent-family` to align family and jurisdiction evidence.
3. You MUST load skill `detect-coverage-gap` to identify absent, thin, or disconnected feature combinations.

Deviation: If claim records are already normalized, reuse them and skip reparsing. If family evidence is incomplete, label the white-space candidate provisional rather than treating absence as freedom to operate.

## Output contract

```yaml
produces: [feature_cross_matrix, protected_combinations, white_space_candidates, coverage_uncertainties]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
```

## Thresholds and quality gates

- Every candidate cell must cite the records and jurisdictions checked.
- Coverage is reported as a ratio over the declared feature universe; the denominator and missing cells must be visible.
- A gap is a candidate for investigation, not a legal conclusion.

## Failure and counterexamples

Do not infer unprotected status from an empty search result, a single family, or an unmatched synonym. Preserve alternative feature decompositions when the claim language is ambiguous.

## Provenance map

- `resolved: white-space-analysis`
- `resolved: knowledge-acquisition-white-space-mapping`
- `resolved: knowledge-acquisition-claim-decomposition`

## Preserved source criteria ledger

| source | source line | kind | source criterion |
|---|---:|---|---|
| none retained | - | - | No source numeric/textual criterion retained after normalization. |

## Context checkpoint / Delta notes

Append feature cells, cited claims, family/jurisdiction coverage, candidate gaps, and unresolved interpretation questions.

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…