smaqit.input-deployment

Validate deployment parameters from session context with defaults.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-input-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smaqit.input-deployment
Source: https://github.com/ruifrvaz/local-image-generator/tree/main/.github/skills/smaqit.input-deployment
Command: npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-input-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates deployment parameters and prompts for confirmation when needed, ensuring accurate and controlled deployment phases.

Core Features & Use Cases

  • Contextual Validation: Validates deployment parameters from session context.
  • Default Parameters: Utilizes defaults for unspecified parameters.
  • Selective Prompting: Informs the user when a parameter is missing and prompts for confirmation.

Quick Start

Trigger the Skill to confirm deployment parameters before beginning the deployment phase.

Frequently Asked Questions about smaqit.input-deployment

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

FAQPage Schema
How do I validate deployment parameters before execution?

Deployment parameter validation checks session context for missing values, applies defaults for unspecified parameters, and prompts for confirmation when undefined values or ambiguous target resolutions are detected to ensure accurate execution.

What happens when a deployment parameter is missing from the session context?

When a deployment parameter is missing, the validation process provides defaults if infrastructure specs allow, or selectively prompts the user for confirmation to resolve the undefined value before proceeding with the deployment phase.

How does contextual validation handle ambiguous target resolutions during deployment?

Contextual validation detects ambiguous target resolutions during deployment and requires explicit user confirmation before proceeding, ensuring that the deployment parameters are accurately resolved and controlled.

Do I need infrastructure specs to resolve default deployment parameters?

Yes, proper infrastructure specs are required for default resolution of deployment parameters. Without them, the validation process will prompt the user to confirm or manually provide the missing parameter values.

What is the best way to ensure deployment safety when parameters are undefined?

Deployment safety is ensured by validating parameters from the session context and selectively prompting users for confirmation whenever parameters are undefined or targets are ambiguous, preventing uncontrolled execution.

Can I use default parameters for all unspecified deployment values?

You can use default parameters for unspecified deployment values only when proper infrastructure specs are available for default resolution; otherwise, the system prompts for explicit user confirmation.