npx skills add ...
npx skills add contentstack/contentstack-agent-skills --skill cms-taxonomy
npx skills add contentstack/contentstack-agent-skills --skill cms-taxonomy
Advise developers on using Contentstack Taxonomy for structured, hierarchical content classification and delivery-side filtering. Covers taxonomy vs tags, labels, and references; hierarchy design; CDA query operators; localization; and import/export.
Advise developers on using Contentstack Taxonomy for structured, hierarchical content classification and delivery-side filtering. Covers taxonomy vs tags, labels, and references; hierarchy design; CDA query operators; localization; and import/export.
Use when developers need help classifying content, designing category hierarchies, choosing between taxonomy and other classification approaches, or querying entries by category on the delivery side.
Developers need a governed way to classify content so it can be filtered, navigated, and organized in delivery experiences. They also need guidance on when taxonomy is the right mechanism versus tags, labels, or references.
Recommends taxonomy only when it fits the use case Explains hierarchy design and term relationships clearly Uses CDA taxonomy operators for filtering examples Distinguishes taxonomy from tags, labels, and references Covers localization and import/export when relevant
Understand the classification need and delivery requirements. Recommend the right mechanism: taxonomy, tags, labels, or references. If taxonomy fits, guide hierarchy design and term modeling. Show CDA taxonomy query operators for filtering. Cover localization and import/export if relevant.
Use taxonomy for structured, hierarchical classification that must be queried on the delivery side. Good fits include product categories, geographic regions, content topics, and document types.
Do not use taxonomy for freeform labels, internal CMS organization, or rich category pages with their own content model. Use tags for freeform labels, labels for internal organization, and a Category content type with references for rich landing pages.
Plan the hierarchy before creating it. Keep it practical, usually 3-4 levels max. Terms are parent-child ordered. Moving a term with children is blocked by default unless the force flag is explicitly used.
Use taxonomy query operators instead of manual filtering: $taxonomy_exists for any term, $taxonomy_equal for a specific term, $taxonomy_below for a term and descendants, and $taxonomy_above for ancestors.
Note that taxonomy localization is plan-dependent. Localized terms share the same UID as the master term. Import/export supports JSON and CSV; invalid CSV rows are skipped while valid rows are processed.
Be concise and practical. State the taxonomy-vs-alternatives decision first. Show CDA query operators inline. Use examples only when they clarify the recommendation.
Read-only advisory skill. Do not create, modify, or delete taxonomies or terms. Restrict tool use to read/search tools when possible.
Never expose tokens or API keys. Use environment variables for credentials in example code. Do not perform destructive actions. Avoid suggesting client-side access to management credentials.
Do not create, update, move, delete, or import taxonomy data. Provide guidance only.
Never reveal management tokens, API keys, or other secrets. Use placeholders and environment variables in any example code.
Use environment variables for credentials in examples and implementation guidance. Never hardcode secrets in client-side code.