Skip to content
Back to skills

Map Coverage Space

ASecurity

Map a set of methods/assets/evidence items against a typed problem, capability, condition, or design space to expose redundancy, coverage structure, and the strength of support in each occupied region.

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

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill map-coverage-space --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Map Coverage Space?

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

Security grade badge for Map Coverage Space
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-map-coverage-space/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-map-coverage-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-coverage-space
description: "Map a set of methods/assets/evidence items against a typed problem, capability, condition, or design space to expose redundancy, coverage structure, and the strength of support in each occupied region."
---

# map-coverage-space
## Purpose
Map methods, assets, or evidence against a typed problem or capability space to expose redundancy, gaps, and how strongly each occupied region is supported.
## Input contract
```yaml
required: [item_set, coverage_dimensions, target_space]
optional: [strength_scale, applicability_rules, evidence_links]
constraints: [dimension semantics and coverage states are declared]
```
## Procedure
1. Define cells or regions from the supplied dimensions.
2. Assign each item to the regions it occupies, with evidence.
3. Grade every occupied region on the caller's strength scale, or on supported, partial, or unsupported when none is supplied; a region graded below the top names what it lacks.
4. Merge duplicate coverage and identify uncovered and weakly supported regions.
5. Return the map with evidence, strength grades, and confidence annotations.

If expected and observed coverage are represented on the same space, consider `detect-coverage-gap` as the next tactic.

## Output contract
```yaml
produces: [coverage_map, redundancy_clusters, gap_register, confidence_annotations]
delta_fields: [findings, evidence_updates, uncertainties]
```
## Quality gates
- Every assignment names its dimensions and evidence.
- Coverage ratio is computed from a declared universe and numerator/denominator.
- Weak and missing coverage are distinguished.
- No region is reported as occupied without a strength grade; a region backed by one item and a region backed by many independent items remain distinguishable.
## Parameterization
Caller supplies item schema, dimension ontology, coverage states, strength scale, and audit numerator/denominator definitions.
## Failure and counterexamples
Reject maps with implicit dimensions, unsupported assignments, ungraded occupancy, or ratios lacking a declared universe.
## Provenance map
- concept: creative-ideation/method-problem-crossing
- concept: knowledge-acquisition/capability-taxonomy-mapping
- intermediate: Pass3/map-method-problem-space
- intermediate: Pass3/map-capability-coverage

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…