asc-hitl-interaction

Handles interactive user prompts for app submission details and confirmations via defined-choice menus and URLs.

32|10|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/moasq/nanowave --skill asc-hitl-interaction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-hitl-interaction
Source: https://github.com/moasq/nanowave/tree/main/internal/orchestration/skills/features/asc-hitl-interaction
Command: npx skills add https://github.com/moasq/nanowave --skill asc-hitl-interaction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines App Store Connect operations by providing a structured way to interact with the user for necessary metadata, settings, and confirmations, ensuring a smooth and accurate submission process.

Core Features & Use Cases

  • Guided Metadata Input: Asks for essential app information like descriptions, keywords, and age ratings using interactive prompts.
  • Configuration Prompts: Handles fixed-option selections such as app categories and content rights.
  • Confirmation Flows: Ensures user agreement before critical actions like submitting an app.
  • Use Case: When preparing an app for submission, this Skill will prompt you for the app's description, suggest a privacy policy URL, and ask for confirmation before initiating the submission process.

Quick Start

Use the asc-hitl-interaction skill to ask the user for the app's description.

Frequently Asked Questions about asc-hitl-interaction

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

FAQPage Schema
How do I collect App Store Connect metadata through user input?

You collect App Store Connect metadata by using interactive terminal prompts that guide users through providing app descriptions, keywords, and age ratings. This human-in-the-loop interaction pattern ensures accurate data submission.

Can I use fixed-option selections for App Store Connect configuration prompts?

Yes, you can use fixed-option selections for App Store Connect configuration prompts to handle choices like app categories and content rights. This ensures users select valid options during the submission setup process.

How do confirmation flows work for destructive App Store Connect actions?

Confirmation flows for destructive App Store Connect actions prompt the user for explicit agreement before executing critical tasks like submitting an app. This prevents accidental modifications and ensures user intent.

What is the best way to handle human-in-the-loop interaction for app submission?

The best way to handle human-in-the-loop interaction for app submission is by structuring interactive prompts with defined options and suggestions. This captures necessary metadata and confirmations efficiently before final processing.

Does the app submission interaction skill support auto-mode behavior?

Yes, the app submission interaction skill defines auto-mode behavior alongside its interactive terminal prompts. This allows operations to proceed automatically when user input is not required or can be inferred from suggestions.

How do I prompt users for a privacy policy URL during App Store Connect operations?

You prompt users for a privacy policy URL by triggering a URL collection interaction pattern within the App Store Connect operations workflow. The skill suggests values and validates the input to ensure correct configuration.