odylith-component-registry

Update and validate the Odylith component registry against component dossier truth.

34|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-component-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odylith-component-registry
Source: https://github.com/odylith/odylith/tree/main/.claude/skills/odylith-component-registry
Command: npx skills add https://github.com/odylith/odylith --skill odylith-component-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the Odylith component registry and component dossier truth remains accurate, auditable, and easy to inspect across sessions.

Core Features & Use Cases

  • Inspect and update the component registry to reflect current component dossier truth across environments.
  • Support audits, onboarding, and change reviews by validating metadata consistency and versioned records.
  • Provide deterministic queries and checks that surface drift between registry state and dossier truth.

Quick Start

Inspect and update the Odylith component registry to ensure the component dossier truth remains accurate.

Frequently Asked Questions about odylith-component-registry

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

FAQPage Schema
How do I audit a component registry for metadata drift across development environments?

Auditing a component registry for drift requires deterministic queries that compare versioned records against the current dossier truth. This skill validates metadata consistency across environments, surfacing discrepancies during change reviews and onboarding to ensure registry accuracy.

What is component dossier truth and how does it relate to registry validation?

Component dossier truth is the authoritative metadata state that registry records must reflect. Registry validation applies integrity checks to ensure versioned entries match this truth, enabling deterministic queries and accurate audits across shared development environments.

How do I update component metadata records to maintain registry consistency across multiple services?

Updating component metadata records requires validating the registry against current dossier truth. This skill applies integrity checks and versioning to ensure deterministic queries remain accurate when multiple services share component metadata across environments.

Can I use registry validation for onboarding and change reviews in engineering environments?

Registry validation supports onboarding and change reviews by providing deterministic queries that check metadata consistency. It validates versioned records against dossier truth, ensuring engineers inspect accurate component states during audits and transitions.

What's the best way to surface drift between a component registry and its dossier truth?

Surfacing drift requires deterministic checks that compare registry state against dossier truth. This skill performs integrity checks and versioned record validation to highlight metadata inconsistencies, ensuring auditable and accurate component tracking.

Why does component metadata become inconsistent across development environments?

Component metadata becomes inconsistent when registry state drifts from dossier truth across multiple shared environments. This skill applies integrity checks and versioned records to detect and resolve these discrepancies during audits and change reviews.