One-click install
npx skills add https://github.com/petekp/circuit-next --skill create-petekp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create
Source: https://github.com/petekp/circuit-next/tree/main/plugins/circuit/skills/create
Command: npx skills add https://github.com/petekp/circuit-next --skill create-petekp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you turn a natural-language developer workflow into a reusable Circuit skill by drafting, validating, and publishing it safely with explicit confirmation.

Core Features & Use Cases

  • Infer a clean flow name using a short lowercase kebab-case slug, asking only when the idea is ambiguous.
  • Draft, then validate by running the Circuit flow authoring runtime in a deterministic, machine-checkable way.
  • Publish only with confirmation to prevent accidental releases of unfinished or incorrect flows.

Quick Start

Ask Circuit to create a reusable custom flow for your workflow request, then confirm the generated draft summary when prompted.

Frequently Asked Questions about create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a natural language workflow description into a validated YAML manifest for a custom flow?

To convert a workflow description into a validated YAML manifest, this Skill generates a kebab-case slug and safely invokes the circuit-next runtime to draft and validate the custom flow deterministically. You provide the description, and the runtime handles the machine-checkable validation.

What is the best way to publish reusable Circuit flows without accidentally releasing unfinished work?

The best way to publish reusable Circuit flows safely is by drafting and validating first, then requiring explicit operator confirmation before publishing. This prevents accidental releases by ensuring you review the generated draft summary and approve it before the flow goes live.

Do I need to manually name my custom flows, or can the authoring process infer a slug automatically?

You do not need to manually name custom flows. The authoring process infers a clean, short lowercase kebab-case slug automatically from your workflow description, only asking for your input when the original idea or request is too ambiguous to generate a name.

Can I use this to author multi-stage developer flows for both Codex and local CLI usage?

Yes, you can use this to author, package, and reuse consistent multi-stage developer flows across Codex or local CLI usage. It applies when you need to package workflows into reusable Circuit skills that run in these environments.

How does the Circuit flow authoring runtime render progress during the drafting and validation process?

The Circuit flow authoring runtime renders progress by processing JSONL presentations during the drafting and validation stages. This provides deterministic, machine-checkable feedback while the runtime safely generates and validates your custom flow.

Why does my custom flow not publish immediately after validation succeeds?

Your custom flow does not publish immediately after validation because the system requires explicit operator confirmation before publishing. This safety mechanism prevents accidental releases of unfinished or incorrect flows, ensuring you approve the draft summary first.