weegloo-create-content-type

Designs and creates Weegloo ContentTypes with field types, validations, and localization rules.

1|2|Updated Feb 20, 2026
Ready to run
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-create-content-type-weeglooapi
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: weegloo-create-content-type
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-create-content-type
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-create-content-type-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modeling a ContentType in Weegloo involves subtle decisions—choosing between ShortText, LongText, and RichText based on CDA search semantics, setting per-field localization, and applying correct FieldValidation shapes—that are easy to get wrong and costly to migrate later. ## Core Features & Use Cases - Search-aware field typing: Selects ShortText, LongText, or RichText based on whether CDA full-text search will actually run on the field, defaulting to RichText for non-searchable body copy. - Validation design: Builds FieldValidation payloads (regexp, in, size, range, dateRange, unique, media constraints, referContentType) with correct API shapes and per-type applicability. - Localization and relationships: Decides localized true vs false per field, models relationships as Refer fields instead of raw id strings, and configures publishWithAuthor for author exposure on the delivery plane. - Use Case: When building a blog or resume site on Weegloo, use this Skill to design the post, comment, and profile ContentTypes with correct field types, validations, and self-referencing reply threads before any Content is created. ## Quick Start Ask the agent to create a Weegloo ContentType for blog posts with a title, body, tags, and an author-visible comment thread.

Frequently Asked Questions about weegloo-create-content-type

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

FAQPage Schema
How do I create a ContentType in Weegloo?▼

Call the cma_CreateContentType MCP tool with the field definitions, which auto-publishes the ContentType on success. Design each field's type, localized flag, and validations first, since a ContentType must be published before creating Content.

Should I use ShortText, LongText, or RichText for a body field?▼

Choose based on CDA search semantics, not text length. Use LongText only when the product will run CDA full-text search on that field; use RichText for long copy that is never full-text searched; use ShortText for short values needing exact or prefix matching.

When should a Weegloo field be localized false?▼

Set localized to false when the value is identical across all locales, such as stable identifiers or a single shared media reference. The value is then stored only under the default locale, and non-default locale values are rejected by the API.

Why does my regexp validation return a 400 error?▼

The regexp validation requires a nested object shape with a pattern key, not a bare string. Use { "regexp": { "pattern": "^\\d{4}$" }, "message": "..." } and escape backslashes in JSON; pattern is capped at 256 characters with flags limited to i, m, u, s.

Why is sys.createdBy empty on delivered content?▼

The ContentType's publishWithAuthor flag defaults to false, so published snapshots omit sys.createdBy on the CDA delivery plane. Enable it when modeling the ContentType and re-publish existing entries, since the change is not retroactive.

Should I store related entry ids in a ShortText field?▼

No, model relationships as Refer fields instead of ShortText id strings. Refer is typed, supports referContentType restrictions, server-side include resolution, and self-references for threads and trees, while ShortText ids cannot be validated or traversed.