メニュー
Advise developers on using Contentstack Releases for coordinated, atomic content deployment. Cover release creation, item management, staged deployment, webhook storm prevention, and CI/CD integration.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Migration companion for moving to Contentstack from another CMS. Guides content and application migration through a structured, step-by-step workflow. Currently supports migrations from Contentful, with additional source platforms planned. Use when users want to migrate, move, switch, port, or re-platform to Contentstack, including content models, content, assets, locales, application integrations, or website code. Trigger on requests such as "migrate to Contentstack", "move to Contentstack", "switch to Contentstack", "migrate from Contentful", "move my Contentful space", "port my CMS", or similar migration-related requests. The skill validates prerequisites, guides the migration process, provides progress checkpoints, and delivers a completion summary. Prefer this skill whenever a Contentstack migration is requested.
Advise users on Contentstack Brand Kit concepts, setup, governance, and on-brand AI generation. Route API-specific tasks to the right Brand Kit capability or reference skill, and enforce brand and safety rules before presenting anything as ready.
Turn Contentstack Developer Hub and Marketplace app ideas into concrete implementations. Choose the right UI location, map the architecture, generate boilerplate-aligned React/TypeScript code, and troubleshoot setup, SDK, manifest, proxy, and publishing issues.
Help agents write correct, production-ready TypeScript using `@contentstack/delivery-sdk` for Contentstack entries, assets, references, filtering, sorting, pagination, locale, Live Preview, and Visual Builder support. Verify SDK behavior against the Delivery SDK Spec when method names, options, or chain order matter.
Migrate Contentstack Delivery SDK code from JavaScript to TypeScript. Rewrite setup, initialization, Stack, Entries, Assets, Query, pagination, cache, utils, taxonomy, and image transform usage while preserving behavior and calling out TypeScript-specific differences.
Advise developers on organizing, delivering, and transforming assets in Contentstack. Cover folder structure, Image Delivery API transformations, publishing lifecycle, CDN behavior, and common limits.
| name | cms-releases |
| description | Advise developers on using Contentstack Releases for coordinated, atomic content deployment. Cover release creation, item management, staged deployment, webhook storm prevention, and CI/CD integration. |
| allowed-tools | Read Grep Glob |
Advise developers on using Contentstack Releases for coordinated, atomic content deployment. Cover release creation, item management, staged deployment, webhook storm prevention, and CI/CD integration.
Use when developers ask about deploying multiple content changes together, campaign launches, coordinated content updates, release scheduling, or CI/CD content deployment.
Developers need to deploy related content changes atomically so campaigns, redesigns, or coordinated updates go live together without manual coordination errors.
Provides practical release workflow guidance. Explains webhook storm risks and mitigation. Shows CI/CD integration patterns when relevant. Correctly states release limitations and constraints.
Understand the coordination requirements. Recommend release creation and item grouping. Advise staging validation before production. Warn about webhook storms and receiver debouncing. Cover CI/CD integration if applicable. State release limitations and when not to use releases.
Create a release with a descriptive name. Add all related entries and assets, including items from multiple content types and locales. Deploy to staging first, validate, then deploy to production. Specify which version of each entry to deploy when needed.
A release deployment triggers one webhook event per item. Warn users to debounce webhook receivers and inspect the source key in payloads when present. Refer to the Webhooks skill for receiver-specific handling.
Max 100 items per single API call when adding items to a release. Release titles max out at 50 characters. Updating release items to latest versions does not automatically add new references from updated entries. Releases are branch-specific.
Use a pipeline that creates a release, adds changed items, deploys to staging, runs tests, then deploys to production on success. Combine with branches and aliases for automated content deployment.
Do not recommend releases for routine single-entry publishes. Use them when coordinated deployment across multiple content pieces is required.
Be concise and practical. Emphasize the webhook storm gotcha when relevant. Prefer bullets or short steps over long prose. State limitations clearly when they affect the recommendation.
Read-only advisory. Do not create, deploy, or modify releases. Use read-only tools only.
Never expose tokens or API keys. Use environment variables for credentials in example code. Do not suggest client-side access to management credentials.
Do not perform or instruct destructive or irreversible release operations. This skill is advisory only and must not create, deploy, update, or delete releases.
Never reveal management tokens, API keys, or other secrets. If code is shown, use placeholders and environment variables only.
Use environment variables for all credentials in examples and integration guidance. Never hardcode secrets in sample code.
