extending-input-types

Create custom input types for PowerShell command-line prompts.

Updated Feb 14, 2026

Search Tags:#automation #hooks #scripting #user interaction #powershell #custom input

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables the creation of custom input types beyond basic text fields, allowing for more interactive and user-friendly prompts within automation workflows.

Core Features & Use Cases

Custom Input Hooks: Develop PowerShell scripts to handle unique input requirements like password masking, numeric validation, confirmations, file path selection, multi-line text, and interactive menus.
Extensibility: Seamlessly integrate new input methods into your JSON-defined workflows by creating simple PowerShell functions.
Use Case: When setting up a new project, you can prompt the user for a port number using a custom 'number' input type that validates the input is within a specified range, ensuring valid configuration.

Quick Start

Create a new input type hook by defining a Get-UserInput function in a hooks/{input_type}.ps1 file.

Frequently Asked Questions about extending-input-types

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

FAQPage Schema

How do I create custom input types for interactive PowerShell command-line prompts?▼

You can create custom input types for interactive PowerShell command-line prompts by defining a `Get-UserInput` function within a hook script. This allows you to implement specialized validation rules and handle unique input requirements directly in your automation workflows.

Can I validate numeric ranges and mask passwords in PowerShell user prompts?▼

Yes, you can validate numeric ranges and mask passwords in PowerShell user prompts by developing custom input hooks. This Skill supports scenarios requiring secure data entry and specialized input validation beyond standard text fields.

Do I need PowerShell hook scripts to integrate custom input validation into JSON workflows?▼

Yes, you need PowerShell hook scripts to integrate custom input validation into JSON workflows. The extensibility relies on defining specific PowerShell functions within these hook scripts to handle the input logic and validation rules.

What is the best way to expand input options for custom command-line automation scripts?▼

The best way to expand input options for custom command-line automation scripts is using custom input hooks. This approach enables interactive menus, multi-line text, file path selection, and confirmations to enhance user experience beyond basic text fields.

Why does my standard text prompt fail to handle specialized user input validation?▼

Standard text prompts fail to handle specialized user input validation because they lack interactive logic. You need custom PowerShell hooks to define specific validation rules for scenarios like port number ranges or secure data entry.