workflow-clone

Copy workflow definitions into new files with draft status and provenance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hollis-labs/volon --skill workflow-clone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-clone
Source: https://github.com/hollis-labs/volon/tree/main/plugins/workflow-author/skills/workflow-clone
Command: npx skills add https://github.com/hollis-labs/volon --skill workflow-clone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates duplicating an existing workflow definition so authors can start from an exact copy without risking the original, enabling safe iterative edits and experimentation.

Core Features & Use Cases

  • Preserves the full workflow body verbatim while creating a new workflow file with updated frontmatter.
  • Resets the clone to status: draft, records the source in replaces for provenance, and appends an evidence note with the clone timestamp.
  • Validates source presence, checks target conflicts and domain directories to avoid overwriting active workflows; useful for creating domain-specific variants or revised versions for review.

Quick Start

Run the workflow-clone command with the source workflow name and the new name, for example: /workflow-clone old-workflow new-workflow.

Frequently Asked Questions about workflow-clone

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

FAQPage Schema
How do I duplicate an existing workflow definition into an editable draft?

To duplicate a workflow definition, run the clone command with the source and new names. This copies the full workflow body verbatim, resets the status to draft, and records the source in the replaces field for provenance.

Can I copy a workflow across different domains without overwriting active workflows?

Yes, you can copy workflows across domains safely. The tool validates source presence and checks target conflicts and domain directories to prevent overwriting any active workflows during the duplication process.

What happens to the frontmatter timestamps when cloning a workflow?

When cloning a workflow, the frontmatter timestamps are updated automatically. The new workflow file receives a status of draft and appends an evidence note containing the clone timestamp for tracking purposes.

Does cloning a workflow preserve the original workflow file content?

Yes, cloning a workflow preserves the original file content exactly. The operation creates a new file with the full workflow body copied verbatim, leaving the original workflow untouched and enabling safe iterative edits.

What's the best way to create domain-specific variants of a workflow for review?

The best way to create domain-specific variants is to clone the workflow. This generates an exact copy with draft status, allowing you to safely experiment and make revisions for review without risking the original active workflow.

Why does cloning a workflow reset the status to draft?

Cloning a workflow resets the status to draft to ensure the new copy undergoes review before activation. This safety measure prevents accidentally running unverified workflow logic while preserving the original provenance.