reference-enrichment

Analyze domain coverage, generate missing reference files, and integrate them via a loading table.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill reference-enrichment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reference-enrichment
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/meta/reference-enrichment
Command: npx skills add https://github.com/notque/vexjoy-agent --skill reference-enrichment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Reference files for agents and skills often stay shallow or incomplete, which makes outputs generic, slow to improve, and hard to validate against progressive-disclosure standards.

Core Features & Use Cases

  • Analyze reference coverage: Detects which sub-domains are missing reference files based on what the skill claims it covers.
  • Research and compile Level 3 references: Creates concrete, domain-specific reference files with detection commands, version notes, and error-fix mappings.
  • Decompose bloated bodies into references: Extracts catalog-like and spec-heavy content out of overly long SKILL.md/agent bodies into focused references/ files, then wires a loading table.
  • Validate before integrating: Runs deterministic and rubric-driven checks to ensure references reach Level 3+ depth and are signal-loadable.

Quick Start

Run reference-enrichment for a target skill by invoking it with the skill or agent name (optionally adding --decompose to extract oversized sections into references).

Frequently Asked Questions about reference-enrichment

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

FAQPage Schema
How do I upgrade shallow agent reference files to reach progressive disclosure Level 3 depth?

Decompose bloated SKILL.md files by extracting spec-heavy and catalog-like content into focused references, then wire a loading table to integrate them safely without bloating the original prompt.

How do I decompose a bloated SKILL.md body into focused references without losing context?

To decompose a bloated SKILL.md body into focused references, extract spec-heavy and catalog-like content into separate files, then wire a loading table to integrate them safely without bloating the original prompt.

Why do my agent outputs stay generic when using progressive disclosure workflows?

Agent outputs stay generic during progressive disclosure when reference files lack domain-specific depth. Missing sub-domain references prevent the agent from loading concrete detection commands, version notes, and error-fix mappings needed for specialized tasks.

Can I validate reference depth before integrating new files into an agent's loading table?

Yes, you can validate reference depth before integrating files by running deterministic and rubric-driven checks to ensure references reach Level 3+ depth and are signal-loadable within progressive disclosure workflows.

What's the best way to discover missing domain coverage in an existing skill?

The best way to discover missing domain coverage in an existing skill is to analyze its claimed domain coverage against its current files, identifying gaps where sub-domain specific references need to be generated.