All products

Manage Storyblok content with AI and the CLI

Pull Storyblok content into local files, review changes and push an approved batch. Check the per-item results before assuming a whole operation succeeded.

To manage Storyblok content with AI and the CLI, identify the source space, target space and relationship you want to preserve. A batch of new articles can refer to an existing folder that the local files do not yet describe. Pulling that folder first gives the push enough context to place the articles correctly.

The storyblok-use-cli skill covers schema files, stories, components, datasources and migrations. It pays particular attention to IDs and references during a push. A command can finish while some individual writes fail, so an editor needs the item totals and errors as well as the process outcome.

What it does

  • Pull the relevant parent folder before adding stories beneath it.
  • Keep source and target space IDs clear when moving an approved batch.
  • Validate schema files locally before pushing changes to the CMS.
  • Read the success and failure totals to find a single rejected story.
  • Check publication flags in individual records before moving draft content.

Install and use

  1. Install the official Storyblok CLI using the project’s Node package manager and sign in for remote work. Local schema validation works offline.
  2. Ask, “Prepare these draft articles under the existing folder and show the target and proposed write.”
  3. Read the push summary and verify a destination record. Revisit failed items without repeating successful writes unnecessarily.

FAQ

Source

Made by Storyblok. Original skill: storyblok-use-cli, published on GitHub under the MIT licence.

View on GitHub