Skip to content
Back to skills

Coverage White Space Search

ASecurity

Map known methods against problem/parameter space and generate candidates from uncovered and weakly covered intersections. Acquisition mechanism is runtime-selected.

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

Security analysis

A100/100

Scanned October 3, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Coverage White Space Search?

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

Security grade badge for Coverage White Space Search
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-coverage-white-space-search/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-coverage-white-space-search)

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: coverage-white-space-search
description: "Map known methods against problem/parameter space and generate candidates from uncovered and weakly covered intersections. Acquisition mechanism is runtime-selected."
---

# coverage-white-space-search
## Purpose
Map known methods against a problem space and generate candidates from intersections that are uncovered or covered without being closed.
## Input contract
```yaml
required: [reference_items, coverage_dimensions]
optional: [performance_records, eligibility_rules]
constraints: [reference items and dimension values must be identifiable]
```
## Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.

1. You MUST load skill `inventory-reference-items` to inventory references.
2. You MUST load skill `map-coverage-space` to map coverage and grade its strength.
3. You MUST load skill `detect-coverage-gap` to detect uncovered and weakly covered regions.
4. You MUST load skill `synthesize-idea` to synthesize candidates.
   If a candidate gap is ready to become a testable explanation, consider `formulate-hypotheses`. If the gap itself still requires evidence validation, consider `validate-research-gap`.
Deviation: acquisition is runtime-selected; do not infer coverage from missing records.
## Output contract
```yaml
produces: [reference_inventory, coverage_map, white_space_gaps, candidate_ideas]
delta_fields: [findings, evidence_updates, hypothesis_updates, decisions, open_questions]
```
## Thresholds and quality gates
- B: every reported gap is either an explicit uncovered intersection over the declared dimensions or an occupied intersection graded below full support, with its covering items and specific shortfall named; duplicate or ineligible regions are excluded.
## Failure and counterexamples
Do not label a region white space when it is merely unsearched, incomparable, or outside the declared universe, and do not treat a region as closed because items occupy it.
## Provenance map
- `systematic-enumeration`, `benchmark-sweep`, `coverage-analysis`, `white-space-identification`, `benchmark-inventory`, `coverage-gap-detection`, `white-space-detection`: resolved/concept by exact lookup.
- Status: all except `benchmark-inventory` resolved; `benchmark-inventory` concept (only package-prefixed variant found).
## Preserved source criteria ledger
- Preserve inventory -> coverage crossing -> gap detection -> candidate synthesis.
## Context checkpoint / Delta notes
Append inventory additions, occupied cells with strength grades, gap definitions, exclusions, and generated candidates.

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…