widget-forms
Use when the agent should ask the user for structured input with an in-chat form, including single-select, multi-select, text fields, style pickers, or voice audition choices.
Install / Use
npx skills add 0xsline/OpenChatCut --skill widget-formsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of widget-forms
widget-forms scores 89/100 on our quality scale, 501st of 1,155 Content & Media skills we index (top 44%).
Its SKILL.md is 8.8 KB long, split into 6 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,986 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so widget-forms is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
widget-forms compared with similar skills
All 4 of these similar skills score higher than widget-forms; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| widget-forms (this skill)by 0xsline | 89 | 2.0k | 56d ago | SKILL.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install widget-forms?
- Run
npx skills add 0xsline/OpenChatCut --skill widget-forms. The install tabs above show the steps for each supported agent. - Which AI agents does widget-forms work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is widget-forms safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is widget-forms still maintained?
- The repository was last updated about 2 months ago, so widget-forms is actively maintained.
Skill content
View source on GitHubname: widget-forms description: Use when the agent should ask the user for structured input with an in-chat form, including single-select, multi-select, text fields, style pickers, or voice audition choices.
Widget Forms
Use the form tool instead of hand-writing markup: the editor chat renders the form as an interactive card and returns the user's structured answer.
Runtime Rule
Call ask_followup_questions. It serializes your fields into the editor's
native form card; the user's submission comes back as their next message.
Plan the whole questionnaire before calling the tool. Send one final form, not a trial form followed by a corrected form. The tool supports at most 12 fields; if the user asks for more questions, merge related prompts into combined fields before the first call.
After calling ask_followup_questions, stop the turn and wait for the submitted
answer to appear in chat. Do not apply a choice, create assets, or continue
planning from a recommendation until the user's selection is present in the
conversation.
Supported Field Mapping
Build a fields array. Write every visible string in the user's conversation
language.
- Native
<form-single>->{ type: "single", variant: "default" } - Native
<form-multi>->{ type: "multi", variant: "default" } - Native
<form-text>/<form-textarea>->{ type: "text" } - Native
<form-visual>->{ type: "single", variant: "visual" } - Voice audition cards ->
{ type: "single", variant: "voice" } - Native start-scenario cards ->
{ type: "single", variant: "scenario" }
Form Copy Tone
For form-level text (title, prompt, fields[].label, submitLabel, and
messagePrefix), write like OpenChatCut is a capable video-making partner inviting
the user to describe what they want, not like a rigid survey.
Aim for:
- Warm, open-ended, and action-oriented. The copy should imply "choose the closest video need or just tell me your idea; we can figure it out together."
- Short and scannable. Use one natural sentence for
promptand concise question labels. - Honest capability framing. OpenChatCut can help with many video workflows, but do not claim unsupported abilities or guarantee a result before inputs are known.
- The user's language and local product terms. Keep "OpenChatCut", "B-roll", "Motion Graphics", "MG 动画", model/product names, and platform names in their established forms.
- User-facing creative wording. For early planning or creative-intake forms, prefer natural terms such as idea, direction, plan, story, shot list, audience, mood, or video need over internal production-document language.
Avoid stiff labels such as "Select video type", "Please choose the video type for this project", or "What type of video do you want to make?" for scenario intake unless the host has no room for warmer copy.
For a scenario-intake form, prefer copy like:
{
"title": "What do you want to make?",
"prompt": "Choose the closest video scenario, or choose Something else and describe your idea.",
"submitLabel": "Start creating",
"messagePrefix": "I want to start with this video direction:",
"fields": [
{
"id": "scenario",
"label": "Which scenario fits your video best?",
"type": "single",
"variant": "scenario",
"otherPlaceholder": "For example: turn my travel footage into an atmospheric vlog / make a launch video for a new product"
}
]
}
Do not include file-upload questions in forms. If a task actually needs source media and the project/chat does not already have it, ask the user separately to upload files in the editor (drag & drop or the upload button, or paste into the chat composer). File upload is not a default prerequisite for every questionnaire; only ask for it when the next editing step depends on missing media.
For choice fields:
- Use
idfor the internal value the next tool call needs. - Use
labelfor what the user sees. - For ordinary single-select and multi-select cards (
variant: "default"), keep options label-only. Do not add per-optiondescriptionunless the user cannot distinguish the choices from labels alone. - Use
descriptionmainly for voice cards. Visual style cards should usually use onlypreview+label. - When an off-list answer is acceptable, add an explicit option with
id: "__other__"and alabelin the same language as the rest of the form, using the word the user would expect for an off-list answer. The widget will turn this option into a text entry when selected. UseotherPlaceholderif the text entry needs a placeholder.
For visual cards:
- Use real image URLs or data image URLs in
preview. - For Design Style catalog choices, call
manage_design_stylewithaction: "list"first, then map each returned preset to{ id: preset.presetId, label: preset.name }(no thumbnails in this build). - Never hardcode catalog preset ids unless the user already selected one.
For voice cards:
- Use
audioUrlfor the sample file. - Prefer the documented sample path such as
/voice-samples/doubao-liuchang.mp3or a public HTTPS URL. Do not pass localhost sample URLs; MCP host iframes do not reliably resolve editor-local media. - Keep user-visible descriptions provider-neutral. Describe the voice the same
way the native OpenChatCut audition UI does: gender / age range / tone / use case,
such as
Female / young / friendly, generalor男 / 中年 / 低沉知识解说. Do not show provider names like ElevenLabs or Doubao in option descriptions. - Keep the option
idequal to the provider voice id needed bysubmit_voice.
For native start-scenario cards:
- Use this when the user should choose which OpenChatCut video workflow to start, such as talking-head editing, MG animation, long-video-to-shorts, product/app promo, AI short film, or explainer video.
- Present these as common video needs/scenarios, not as the only possible video workflows. The form must also let the user describe a different video need.
- Use exactly one single-select field with
variant: "scenario". - Provide options using the canonical ids below and localized labels in the
user's language. Include
id: "__other__"only when you need to customize the off-list label; otherwise the backend appends a localized Other option. - English, Chinese, and Spanish scenario labels/descriptions/starter prompts are
built in. For any other user language, faithfully translate each scenario's
English
label,description, and starter prompt into the user's language and pass those localized values in the option objects. Preserve OpenChatCut product terms and workflow meaning; do not add new requirements. UsesubmitPromptfor the translated starter prompt. This override is specific tovariant: "scenario"; ordinary option cards, voice cards, and visual style cards already get their visible text from the values you pass. - Do not provide custom
previeworaudioUrl; the backend fills the native first-screen preview image. - Canonical ids:
talking-head,motion-graphics,long-video-to-shorts,app-promo,ai-cinematic-short-film,explainer, plus__other__for a free-form video need. - Example options:
{ "id": "talking-head", "label": "Talking Head Editing" },{ "id": "motion-graphics", "label": "Motion Graphics" },{ "id": "long-video-to-shorts", "label": "Long Video to Shorts" },{ "id": "app-promo", "label": "Product / App Promo" },{ "id": "ai-cinematic-short-film", "label": "AI Short Film" },{ "id": "explainer", "label": "Explainer Video" },{ "id": "__other__", "label": "Something else" }.
Current Gaps
ask_followup_questions is for structured answers only. It does not support native
custom HTML, timeline parameter bridges, editor item selection, or file upload
fields. For files already held by the agent runtime or attached directly to the
chat outside this card, the media-import workflow is still valid: call
import_media and run the helper/direct upload path. For files the user wants
to place directly in a project, ask them to use the OpenChatCut editor upload UI.
Example
{
"title": "Your video idea",
"prompt": "Choose or fill in what you have in mind so OpenChatCut can pick a good starting direction.",
"submitLabel": "Send idea",
"messagePrefix": "Continue with this video direction:",
"fields": [
{
"id": "goal",
"label": "What's the main goal of this video?",
"type": "single",
"options": [
{ "id": "product_intro", "label": "Product intro" },
{ "id": "social_ad", "label": "Social ad" },
{ "id": "__other__", "label": "Something else" }
]
},
{
"id": "elements",
"label": "What should it include? (Select all that apply)",
"type": "multi",
"options": [
{ "id": "broll", "label": "B-roll" },
{ "id": "logo", "label": "Brand logo" },
{ "id": "__other__", "label": "Something else" }
]
}
]
}
Related Skills
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
