Semantius Modeler

Deploys a `*-semantic-spec.md` (from `semantius-analyst`) to a live Semantius instance via the `semantius` CLI. Already reconciled: every entity carries a `Reconciliation:` annotation (create-new, reuse-from, rename-incoming-from, promote-to-master, dropped), every cross-model link resolved, every collision decision baked in. A thin executor: parse spec, verify annotations hold against live, render plan, execute writes, verify, optional sample data. It does NOT detect collisions, classify entities, drive merge/rename/promotion widgets, or ask about catalog ambiguity; that is the analyst's job, carried in the spec. If annotations are missing or the catalog drifted since the analyst ran, the modeler refuses and routes the user back to the analyst. Trigger when the user has a spec and wants to deploy / apply / push / implement the spec ("deploy the spec", "apply the schema", "push this to Semantius", "now make it real"). If the user references a `*-semantic-blueprint.md`, route through the analyst first.

mkdir -p ~/.claude/skills/semantius-modeler
curl -L https://claudskills.com/skills/semantius-modeler/SKILL.md \
  -o ~/.claude/skills/semantius-modeler/SKILL.md

@misc{semantius-modeler-2026,
  author    = {IntranetFactory},
  title     = {Semantius Modeler [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/semantius-modeler/}
}