widget-forms

Collect structured user input via host-specific form workflows.

751|69|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ChatCut-Inc/agent-plugin --skill widget-forms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: widget-forms
Source: https://github.com/ChatCut-Inc/agent-plugin/tree/main/claude/skills/widget-forms
Command: npx skills add https://github.com/ChatCut-Inc/agent-plugin --skill widget-forms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps AI agents collect structured user input through the correct host-specific form surface without emitting unsupported ChatCut widget markup.

Core Features & Use Cases

  • Codex Forms: Uses the ChatCut MCP follow-up question tool to gather related fields in a single form.
  • Claude Code Forms: Uses the structured-input elicitation workflow with a visual form and requires submission through the supported mechanism.
  • Host-Aware Interaction: Prevents cross-host tool misuse and keeps the agent waiting until the user submits the requested information.
  • Use Case: Gather project settings, creative preferences, or other structured inputs before continuing a ChatCut editing workflow.

Quick Start

Ask the widget-forms skill to collect the user's structured ChatCut project preferences using the active plugin host's supported form surface.

Frequently Asked Questions about widget-forms

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

FAQPage Schema
How do I collect structured input in ChatCut workflows without unsupported widget markup?

You collect structured input by using host-specific form handling surfaces, such as Codex's ask_followup_questions MCP tool or Claude Code's visualize.show_widget elicitation workflow, and this approach prevents emitting unsupported ChatCut widget markup.

Does Claude Code support structured user input forms for project settings?

Yes, Claude Code supports structured user input forms through the visualize.show_widget elicitation workflow, which presents a visual form and requires submission through the supported mechanism.

How do I gather multiple creative preferences in a single form using Codex?

You gather multiple creative preferences in a single form in Codex by using the ChatCut MCP follow-up question tool, which collects related fields together and keeps the agent waiting until submission.

Why does my AI agent emit unsupported ChatCut widget markup when asking for project settings?

Your agent emits unsupported markup because it is not using the correct host-specific form surface; applying host-aware interaction through the proper MCP tool or elicitation workflow prevents this cross-host tool misuse.

What is the best way to prevent cross-host tool misuse when collecting structured responses?

The best way to prevent cross-host tool misuse is to apply host-aware interaction rules, ensuring the agent uses the correct Codex or Claude Code form surface and waits until the user submits the requested information.