check-existing-coverage

Name: check-existing-coverage
Availability: InStock
Author: largo2z9

Check existing DTC workspace structures before creating new extension requests.

1|Updated Apr 20, 2026

Search Tags:#scaffolding #workspace #coverage #entities #schemas #reuse

Ready to run

npx skills add https://github.com/Largo2z9/phantomos --skill check-existing-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-existing-coverage
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/check-existing-coverage
Command: npx skills add https://github.com/Largo2z9/phantomos --skill check-existing-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unnecessary workspace extensions by identifying whether an operator's intent is already covered by existing entities, sidecars, custom structures, or shared resources.

Core Features & Use Cases

Coverage Analysis: Scans core entities, active brand sidecars, custom entities, sibling brand patterns, and shared resources to find reusable structures.
Reuse Routing: Returns actionable routing decisions such as using existing structures, applying partial reuse, or proceeding with genuinely new scaffolding.
Use Case: When an operator wants to add a new tracked concept like competitor pricing or creative angle metadata, this Skill checks the workspace first and recommends reuse when a suitable structure already exists.

Quick Start

Ask the skill to check whether an intended workspace extension is already covered by existing structures before creating anything new.

Frequently Asked Questions about check-existing-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if existing workspace coverage already supports a new entity before scaffolding?▼

To check existing workspace coverage, analyze core entities, active brand sidecars, custom schemas, and shared resources to determine if an intended extension is already represented. This coverage analysis returns a validated decision to reuse existing structures or proceed with new scaffolding.

What happens when a new custom schema duplicates an existing brand sidecar structure?▼

When a new custom schema duplicates an existing brand sidecar, coverage analysis identifies the redundancy and routes the operator to reuse the existing structure. This prevents unnecessary workspace extensions by validating that the intended concept is already fully represented.

How do I analyze sibling brand patterns to find reusable workspace structures?▼

Analyze sibling brand patterns by scanning active brand sidecars and shared resource registries across the workspace. This coverage check identifies matching portfolio patterns, enabling partial reuse or full structural adoption before creating new custom entities.

Do I need access to resource registries to check for duplicate workspace structures?▼

Yes, checking for duplicate workspace structures requires access to workspace schemas, brand structures, indexes, and resource registries. These inputs enable the Skill to scan core entities and shared resources to return accurate reuse or creation decisions.

When should I avoid creating new scaffolding for DTC operations workspaces?▼

Avoid creating new scaffolding when coverage analysis confirms the intended extension is already represented by existing entities, sidecars, or shared resources. Proceed with new scaffolding only when the workspace schemas and resource registries lack suitable reusable structures.

Can I reuse portfolio patterns across sibling brands instead of building custom entities?▼

Yes, coverage analysis scans sibling brand patterns and shared resources to identify reusable portfolio structures. When a matching pattern exists, the Skill returns a routing decision to apply partial or full reuse, preventing the creation of redundant custom entities.