claude-workflow-plugin-distribution

Package Claude Code workflows into plugins with sandbox-aware launcher architecture.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill claude-workflow-plugin-distribution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-workflow-plugin-distribution
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/claude-workflow-plugin-distribution
Command: npx skills add https://github.com/cajias/claude-skills --skill claude-workflow-plugin-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill explains how to package and distribute a Claude Code Workflow-based automation so it can be delivered through a plugin or marketplace instead of being left as an internal script.

Core Features & Use Cases

  • Workflow Packaging: Shows how to bundle a workflow engine inside a skill and launch it from the plugin root.
  • Sandbox-Aware Architecture: Clarifies what the workflow sandbox can and cannot do, especially around filesystem access and deterministic preprocessing.
  • Launcher and Engine Separation: Helps you keep file I/O, pre-processing, and prompt setup in the skill while the workflow engine handles in-memory orchestration.
  • Use Case: Use this Skill when you want to ship a multi-step Claude Code workflow as part of a plugin, or when you are designing a command that needs to invoke a workflow safely and predictably.

Quick Start

Use this skill to package your workflow into a plugin by placing the engine under the plugin root and having the skill launch it through the Workflow tool.

Frequently Asked Questions about claude-workflow-plugin-distribution

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

FAQPage Schema
How do I package a multi-step Claude Code workflow for plugin distribution?

To package a Claude Code workflow for plugin distribution, place the workflow engine under the plugin root and have the skill launch it through the Workflow tool. This bundles the automation so it can be delivered through a marketplace instead of remaining an internal script.

What is the workflow sandbox in Claude Code plugins and how does it handle file I/O?

The workflow sandbox in Claude Code plugins handles in-memory orchestration but restricts direct file I/O. File operations, pre-processing, and prompt setup must be separated and handled by the skill layer outside the sandbox engine.

How do I separate a workflow launcher from the engine when building a Claude Code plugin?

Separate the workflow launcher from the engine by keeping file I/O, pre-processing, and prompt setup in the skill while the workflow engine handles in-memory orchestration. Use plugin-root asset paths to reference the engine and launch it predictably.

Can I use a workflows plugin component directly in Claude Code?

No, there is no workflows plugin component available in Claude Code. You must structure your plugin by placing the workflow engine under the plugin root and having a skill invoke it through the Workflow tool for deterministic orchestration.

Why does my Claude Code workflow fail when accessing files inside the sandbox?

Claude Code workflow sandboxes lack direct filesystem access by design. File I/O and deterministic preprocessing must be handled by the skill layer before the in-memory orchestration engine takes over, ensuring safe and predictable execution.