pulse-editor_skill

This skill helps you create, update, and publish Pulse Apps using the cloud-based Vibe Dev Flow, delivering instant deployment and versioned artifacts.
  • Python

2.5k

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 openclaw/skills --skill pulse-editor

  • _meta.json298 B
  • SKILL.md13.8 KB

Overview

This skill lets you generate, build, and publish Pulse Apps using the Vibe Dev Flow API. It offloads code generation to Pulse Editor’s cloud agents, producing a live app URL and source archive once the SSE stream completes. Use it to create new apps, update existing apps, or request generated source artifacts without local build tooling.

How this skill works

Send a POST to the Vibe Dev Flow generate endpoint with your prompt, optional appName, appId, version, and streamUpdatePolicy. The API returns a Server-Sent Events (SSE) stream with creation and update messages; final artifactOutput messages include publishedAppLink and sourceCodeArchiveLink. The call is long-running (typically 2–5 minutes) and must be allowed to run up to 10 minutes to complete.

When to use it

  • Create a new Pulse App from a natural-language description or specification.
  • Update an existing Pulse App by supplying appId (and optional version).
  • Generate production-ready source code and a published app URL without local builds.
  • Batch-generate multiple apps or microservices in parallel using concurrent calls.
  • Retrieve a source code archive and published link for automated deployments.

Best practices

  • Provide clear, detailed prompts describing features, auth, UI, and data models.
  • Set Accept: text/event-stream and streamUpdatePolicy: "artifactOnly" to reduce token usage.
  • Allow the request up to 10 minutes and treat idle SSE intervals as normal.
  • Never hardcode API keys; use environment variables or secure secrets storage.
  • Handle 400/401/500 responses and parse SSE creation/update messages robustly.

Example use cases

  • Scaffold a todo app with authentication, dark mode, and a calendar view.
  • Add a feature to an existing app by sending a prompt with appId and version.
  • Automate generation of multiple microservice frontends in a CI pipeline.
  • Obtain a final source archive and published URL for demo or testing builds.
  • Offload AI-driven code generation for lightweight agents without local tools.

FAQ

Typical runs finish in 2–5 minutes; complex apps can take longer. Do not timeout requests until 10 minutes.

How do I get the published app URL and source archive?

Watch for a final artifactOutput SSE message. It contains publishedAppLink and sourceCodeArchiveLink in the message result.

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