ai-deployment_skill

This skill automates registration, build, upload, and deployment of Kuroco sites from AI prompts, delivering preview or production URLs efficiently.

0

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill diverta/kuroco-skills --skill ai-deployment

  • metadata.json104 B
  • SKILL.md13.3 KB

Overview

This skill automates Kuroco site registration, frontend build, artifact upload, and deployment. It coordinates site creation or selection, framework-specific builds (Nuxt/Next/Vite), S3 presigned uploads, and calls the Kuroco deploy API to publish preview or production URLs. The workflow is designed for CI/CD integration and hands-off releases.

How this skill works

The skill prompts the user to choose a target site, site_key strategy, and deploy mode. It then optionally calls the add_site API to register a new site, runs the detected frontend build command, zips the build output, requests a presigned URL via temp-upload, uploads the artifact to S3, and finally calls kuroco_front/deploy with artifact_url and preview flag. It returns stage_url for preview deployments or domain for production.

When to use it

  • Automating end-to-end Kuroco frontend deployments from CI pipelines.
  • Deploying static builds from Nuxt, Next (static), or Vite projects.
  • Registering new Kuroco sites and publishing builds programmatically.
  • Creating preview deployments for QA or stakeholder review.
  • Replacing manual S3 uploads and deploy API calls with a single flow.

Best practices

  • Use a StaticToken with correct X-RCMS-API-ACCESS-TOKEN header and keep it secure.
  • Prefer auto-generated site_key to avoid collisions; validate allowed characters if manual.
  • Detect framework from package.json and run the recommended build command before zipping.
  • Ensure artifact_url returned from temp-upload is HTTPS to avoid validation errors.
  • Run deployments in preview mode first, validate stage_url, then promote to production.

Example use cases

  • CI job that builds a Nuxt site, uploads artifact.zip via presigned URL, and triggers a preview deploy.
  • Onboarding flow that auto-creates a new Kuroco site, sets admin email, and publishes an initial build.
  • Scheduled nightly builds for a static Next site that automatically update the production domain.
  • Developer preview feature: each pull request triggers a Vite build and deploys to a unique stage_url for review.

FAQ

Nuxt: npm run generate, Next.js static: npm run build, Vite: npm run build. Detect from package.json and adjust output directory accordingly.

How is the ZIP artifact uploaded?

Request a presigned URL from /temp-upload, PUT the artifact.zip to that URL with Content-Type: application/zip, then pass the returned HTTPS url as artifact_url to the deploy API.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational