workflow-editor

Modify ACP workflow directories with validated JSON and naming checks.

Updated May 5, 2026
One-click install
npx skills add https://github.com/swghosh/ambient-workflows --skill workflow-editor-swghosh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-editor
Source: https://github.com/swghosh/ambient-workflows/tree/main/.claude/skills/workflow-editor
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill workflow-editor-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make safe, validated edits to existing ACP workflows so you can change agents, commands, and configuration without causing broken JSON, invalid naming, or inconsistent documentation.

Core Features & Use Cases

  • Validated workflow editing: Ensures workflow names and file names follow conventions and that .ambient/ambient.json remains valid JSON with required fields.
  • Minimal, targeted changes: Applies only the requested updates to agents, commands, .ambient/ambient.json, and README documentation while preserving structure and style.
  • Post-edit validation & cleanup: Runs JSON parsing validation (via jq), checks filename conventions, and verifies no temporary markers remain, then summarizes results and next steps.

Quick Start

Ask the Workflow Editor to update the command and documentation for a specific phase in an existing workflow directory.

Frequently Asked Questions about workflow-editor

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

FAQPage Schema
How do I safely edit ACP workflow JSON without breaking required fields?

To safely edit ACP workflow JSON, validate that required fields (name, description, systemPrompt) remain intact and parse the file with jq afterward. This ensures structural integrity while applying minimal, targeted changes to agents and commands.

What is the best way to rename an existing ACP workflow directory and update its configuration?

The best way to rename an ACP workflow directory is to apply strict filename convention linting alongside validated updates to the `.ambient/ambient.json` file. This preserves structural consistency while ensuring the new name follows required naming rules.

How do I validate ACP workflow configuration changes after modifying agents and commands?

Validating ACP workflow configuration changes requires running jq parsing checks on `.ambient/ambient.json`, verifying filename conventions, and confirming no temporary markers remain. This post-edit validation prevents broken JSON and inconsistent states.

Does workflow editing automatically update README documentation for modified ACP phases?

Workflow editing applies validated changes to agents, commands, and configuration while simultaneously updating README documentation. This keeps documentation consistent with the minimal, targeted modifications made across the workflow directory.

What are the limitations of applying git-safe changes to ACP workflows?

Git-safe changes are limited to minimal diffs within existing workflow directories under `workflows/`. This approach does not support creating entirely new workflow architectures, only refactoring, renaming, and editing existing configurations safely.