invoke

Execute predefined workflows by name and return aggregated results.

4|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/synaptiai/agent-capability-standard --skill invoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoke
Source: https://github.com/synaptiai/agent-capability-standard/tree/main/skills/invoke
Command: npx skills add https://github.com/synaptiai/agent-capability-standard --skill invoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute predefined workflows by name, enabling reuse of complex capability compositions and consistent execution across contexts.

Core Features & Use Cases

  • Resolve workflow by name from a catalog and validate its existence.
  • Validate inputs against the chosen workflow schema, initialize execution context, and orchestrate steps with proper dependency handling.
  • Aggregate per-step outputs into a structured result and provide an execution trace for auditing and debugging.
  • Supports nested or hierarchical workflows and returns a complete execution record with provenance anchors.

Quick Start

Pass the workflow name and any input parameters, then review the aggregated results produced by the execution.

Frequently Asked Questions about invoke

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

FAQPage Schema
How do I execute a predefined workflow by name and validate its inputs?

To execute a predefined workflow, you pass the workflow name and input parameters. The system validates the requested workflow against the catalog and checks inputs against the schema before initializing the execution context and sequencing steps.

What is the best way to orchestrate multi-step processes and reuse capability compositions across projects?

Orchestrating multi-step processes is handled by invoking a named workflow. This delegates to templates, validates dependencies, sequences the steps, and aggregates per-step outputs into a structured result for consistent execution across projects.

Can I use nested or hierarchical workflows for complex process execution?

Yes, nested or hierarchical workflows are supported for complex process execution. The orchestrator handles dependencies within these structures and returns a complete execution record with provenance anchors for auditing.

How does workflow execution handle failures and aggregate outputs for auditing?

Workflow execution handles failures during the step sequencing phase and aggregates per-step outputs into a structured result. It provides an execution trace with provenance anchors to facilitate debugging and auditing.

Do I need a workflow catalog to resolve and validate predefined workflows?

Yes, a workflow catalog is required. The system resolves the workflow by name from this catalog and validates its existence to ensure the requested capability composition is available before initializing execution.

What is returned after orchestrating a multi-step workflow execution?

After orchestrating a multi-step workflow execution, the system returns a structured execution record. This record includes aggregated per-step outputs and an execution trace with provenance anchors for debugging and auditing.