ecm-model-validator

Diagnoses structural issues in ECM Studio repositories and enforces hierarchy invariants.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-model-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecm-model-validator
Source: https://github.com/ThomasRohde/ecm-studio/tree/main/.agents/skills/ecm-model-validator
Command: npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-model-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate, inspect, and diagnose ECM Studio repositories that store capability data in ecm/capabilities.jsonl. Use this whenever the user asks whether an ECM repo is valid, wants to inspect capability IDs and paths, needs help understanding capability hierarchy issues, or before and after capability edits in an ECM repo, even if they only say the model seems broken or inconsistent.

Core Features & Use Cases

  • Verify repo structure and capability mappings
  • Surface duplicates, missing parents, and hierarchy cycles
  • Provide diagnostics before edits and after repairs

Quick Start

Run the validator against your ECM workspace to verify structure and inspect IDs.

Frequently Asked Questions about ecm-model-validator

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

FAQPage Schema
How do I validate an ECM Studio repository structure?

To validate an ECM Studio repository, run the validator against your workspace to verify structure and inspect capability IDs, ensuring the ecm-studio.json and ecm/*.jsonl files conform to expected formats.

What causes capability hierarchy cycles or missing parents in ECM workspaces?

Capability hierarchy cycles or missing parents in ECM workspaces are caused by invalid parent references in capabilities.jsonl, which the validator surfaces by enforcing invariants like complete parentage and unique IDs.

Can I list all capability IDs and paths from an ecm-studio.json file?

Yes, you can list all capability IDs and paths from an ecm-studio.json file by running the validator, which inspects the workspace and extracts these identifiers for diagnostic and mapping purposes.

Do I need the ecm-capability-manager to run diagnostics on my ECM repo?

The validator leverages the shared ecm-capability-manager tooling for diagnostics, so having it available ensures comprehensive validation of your ECM repo's structural integrity and capability mappings.

When should I run pre-edit diagnostics on capabilities.jsonl?

You should run pre-edit diagnostics on capabilities.jsonl before making any capability edits in an ECM repo to ensure structural validity, and again after repairs to confirm all hierarchy issues are resolved.