content-model

Design Crystallize content models and validate mass-operations JSON.

4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/CrystallizeAPI/ai --skill content-model-crystallizeapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-model
Source: https://github.com/CrystallizeAPI/ai/tree/main/use-crystallize/skills/content-model
Command: npx skills add https://github.com/CrystallizeAPI/ai --skill content-model-crystallizeapi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design correct, maintainable Crystallize content models by guiding you from business intent to Shapes, Components, Pieces, taxonomies, and relationship patterns—then producing validated mass-operations JSON.

Core Features & Use Cases

  • Content modelling guidance: Choose the right Shape type (Product, Document, Folder), then add Components and nested Pieces using the proper discipline.
  • Relationship pattern design: Implement semantic/quantised/composite/conditional bridges using item relations with strict acceptedShapeIdentifiers and cardinality constraints.
  • Taxonomy and structure planning: Model topic maps and catalogue structures for scalable discovery and organization.
  • Safe build workflow: Always validate the generated mass operations using the build-mass-operation MCP tool before returning results.

Quick Start

Use the content-model skill to generate and validate mass operations JSON for a new Crystallize content model that includes shapes, pieces, and relationship constraints tailored to your product or editorial domain.

Frequently Asked Questions about content-model

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

FAQPage Schema
How do I design scalable content models in Crystallize for products and documents?

To design scalable Crystallize content models, translate your business intent into appropriate Shape types, Components, and Pieces, then define taxonomy relationship patterns and item relations with strict acceptedShapeIdentifiers and cardinality constraints.

How do I build item relations in Crystallize with acceptedShapeIdentifiers and cardinality?

Building Crystallize item relations requires configuring acceptedShapeIdentifiers to restrict which Shapes can connect, then setting cardinality constraints to enforce semantic, quantised, composite, or conditional bridges between items.

What's the best way to generate mass operations JSON for Crystallize content structures?

Generating mass operations JSON for Crystallize requires following a correct multi-phase creation order for Shapes, Pieces, and taxonomies, then running mandatory validation via the build-mass-operation MCP tool against the @crystallize/schema before returning results.

When should I use nested Pieces versus Components in a Crystallize content model?

Use Crystallize Components for reusable building blocks within a Shape, and use nested Pieces when you need polymorphic or reusable component groups that maintain structural discipline across your editorial domain.

Can I model topic maps and catalogue taxonomies in Crystallize for scalable discovery?

Yes, Crystallize supports modelling topic maps and catalogue taxonomy structures by defining Folder Shapes and relationship patterns, enabling scalable content discovery and organization across large product catalogues and editorial domains.