extending-action-types

Create custom action type hooks with PowerShell scripts for JSON workflows.

Updated Feb 14, 2026

Search Tags:#automation #workflow #hooks #extensibility #custom actions #powershell

Ready to run

npx skills add https://github.com/Kaim-Ru/KaisStepsExecutor --skill extending-action-types

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extending-action-types
Source: https://github.com/Kaim-Ru/KaisStepsExecutor/tree/main/.github/skills/extending-action-types
Command: npx skills add https://github.com/Kaim-Ru/KaisStepsExecutor --skill extending-action-types

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill empowers you to expand the capabilities of your automation workflows by creating custom action types, allowing for integration with new services and functionalities.

Core Features & Use Cases

Custom Action Hooks: Define new actions (e.g., download files, initialize Git repos, send HTTP requests) using PowerShell scripts.
Extensibility: Seamlessly integrate third-party tools or custom logic into your JSON-defined workflows.
Use Case: You need to automatically create a new GitHub repository and push initial project files. You can create a gitinit action type to handle this, then use it in your steps.json.

Quick Start

Create a new PowerShell script in the hooks/ directory named download.ps1 to define a custom download action type.

Frequently Asked Questions about extending-action-types

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

FAQPage Schema

How do I create custom action hooks for JSON automation workflows?▼

Custom action hooks extend JSON automation workflows by defining new actions using PowerShell scripts in the hooks directory. You create a new PowerShell script, such as download.ps1, to implement specific deterministic actions like file downloads or HTTP requests.

Can I use PowerShell scripts to add custom actions to declarative workflows?▼

Yes, you can use PowerShell scripts to add custom actions to declarative workflows. By adhering to a specific PowerShell function naming convention and parameter structure, you integrate custom logic directly into your JSON-defined automation steps.

What is the best way to integrate Git repository initialization into my automation?▼

The best way to integrate Git repository initialization into automation is to define a custom action type, such as gitinit. This allows you to handle repository creation and initial file pushes directly within your declarative JSON workflows.

Does this automation framework support sending HTTP requests as custom workflow steps?▼

Yes, the automation framework supports sending HTTP requests as custom workflow steps. You can define a custom action type using a PowerShell script to handle HTTP requests, seamlessly integrating external service calls into your JSON workflows.

What are the limitations when defining custom action types with PowerShell?▼

Custom action types defined with PowerShell are limited to deterministic actions and require strict adherence to a specific function naming convention and parameter structure to integrate correctly with declarative JSON workflows.