workflow-action-catalog-foundation

Model workflow-editor action discovery as catalog metadata with authored parameter schemas.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-action-catalog-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-action-catalog-foundation
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/workflow-action-catalog-foundation
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-action-catalog-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of decoupling runtime action execution from design-time workflow authoring, preventing the leakage of implementation details into workflow definitions.

Core Features & Use Cases

  • Unified Schema Contracts: Uses shared parameter schemas for both catalog discovery and workflow validation.
  • Data-Driven UI: Enables the frontend to dynamically render parameter editors based on metadata rather than hard-coded logic.
  • Use Case: When building a workflow editor, use this pattern to expose a consistent API that allows the UI to discover available actions and validate user inputs without needing to know how the backend executes those actions.

Quick Start

Use the workflow-action-catalog-foundation skill to generate a new action catalog entry by defining the parameter schema and registering it with the IActionCatalogProvider.

Frequently Asked Questions about workflow-action-catalog-foundation

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

FAQPage Schema
How do I decouple workflow action execution from declarative workflow JSON definitions?

Decouple workflow action execution by modeling action discovery as catalog metadata backed by authored parameter schemas, separating runtime handlers from design-time workflow JSON definitions. This prevents implementation details from leaking into workflow definitions.

How do I dynamically render workflow parameter editors from metadata instead of hard-coded logic?

Dynamically render parameter editors by using catalog metadata and shared parameter schemas to drive the frontend UI, allowing it to discover available actions and validate inputs without hard-coded logic.

What is an IActionCatalogProvider used for in workflow architecture?

An IActionCatalogProvider is used to register action catalog entries and expose a consistent API for workflow editors to discover available actions and validate user inputs across the authoring boundary.

How do I ensure consistent validation across workflow authoring and runtime boundaries?

Ensure consistent validation by using an AuthoredParameterSchema as a shared contract for both catalog discovery and workflow validation, maintaining schema consistency across the authoring boundary.

Do I need dependencies to implement action catalog metadata for a workflow editor?

No dependencies are required. You can implement the action catalog pattern by defining parameter schemas and registering them with an IActionCatalogProvider using your existing software engineering stack.