One-click install
npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-form-inputs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amvcp-form-inputs
Source: https://github.com/Emasoft/ai-maestro-visual-communicator-plugin/tree/main/skills/amvcp-form-inputs
Command: npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-form-inputs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates ambiguous free-text answers by giving agents a consistent, structured way to collect finite user responses inside conversational report flows.

Core Features & Use Cases

  • Nineteen structured-response widgets for radio, multi-select, numeric+unit, date, color, slider, toggle, rating, card picker, tag input, URL, hierarchical tree picker, password (with strength), currency, gallery picker, tier list, and drag-to-rank.
  • Deterministic, persistable answers that save to localStorage under a stable data-ve-id and rehydrate on reload.
  • Event-driven integration via ve-form-change so the runtime can thread the structured payload into the next comment-turn record, optionally combined with free-text rationale.
  • Use cases: choosing among controlled options (e.g., rollout strategy), collecting parameterized inputs (e.g., dates, budgets, ratings), and producing prioritization artifacts (e.g., tiering or ordered rank lists) without forcing the user to type.

Quick Start

Ask the user a finite question and embed the matching widget with a stable data-ve-id, then load amvcp-runtime.js and amvcp-form-inputs.js and listen for ve-form-change to capture the structured answer.

Frequently Asked Questions about amvcp-form-inputs

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

FAQPage Schema
How do I collect structured form inputs in a conversational agent instead of free-text?

Structured form widgets replace ambiguous free-text by rendering interactive elements like radio selectors, date pickers, and drag-to-rank lists inside conversational reports. You embed widgets with a stable data-ve-id and load the runtime scripts to capture finite user responses deterministically.

Can I persist structured user selections locally so they survive a page reload?

Structured user selections persist locally by saving answers to browser localStorage under the key amvcp-form-input:<data-ve-id>. The runtime automatically rehydrates these persisted values when the generated HTML page reloads, ensuring no data loss across sessions.

How do I capture widget selection events to thread answers into the next agent turn?

Widget selection events are captured by listening for the ve-form-change event emitted by the runtime. This event-driven integration threads the structured payload into the next comment-turn record, optionally combining the finite answers with free-text rationale provided by the user.

What types of interactive widgets are available for conversational UX prioritization tasks?

Interactive widgets for prioritization tasks include drag-to-rank, tier lists, and card pickers, alongside nineteen other structured-response controls like sliders, toggles, and multi-select tags. These widgets produce ordered prioritization artifacts without forcing users to type manual rankings.

Do I need external dependencies to render structured form widgets in generated HTML pages?

Rendering structured form widgets requires no external dependencies, only loading the provided scripts like amvcp-runtime.js and amvcp-form-inputs.js. Widgets render natively in generated HTML pages using JSON configuration scripts and deterministic runtime initialization tied to stable data-ve-id roots.

When should I avoid using free-text prompts and switch to structured widget inputs?

Free-text prompts should be replaced with structured widget inputs when collecting finite, controlled responses such as choosing among rollout strategies, setting parameterized budgets, or producing ordered rank lists. Free-text remains appropriate only when capturing optional rationale alongside the structured payload.