Multi Modal Input

Community

Owl-Listener

multi-modal-input

Design interfaces that offer multiple input methods so users can choose what works for their abilities and context. Use when designing any interactive system where users provide input — forms, search, editors, creative tools, communication interfaces. Triggers on: multi-modal, input methods, alternative input, how people interact, mouse alternative, touch alternative, input flexibility, switch access, eye tracking, head pointer.

Overview

Publisher	Owl-Listener
Repository	`inclusive-design-skills`
Skill name	`multi-modal-input`
Stars	108
Forks	28
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Multi Modal Input AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/multi-modal-input
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/multi-modal-input

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/inclusive-interaction/skills/multi-modal-input .claude/skills/multi-modal-input

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Multi Modal Input in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Multi Modal Input on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Multi Modal Input is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Multi-Modal Input Design

Design systems where users can accomplish any task through whichever input method works for them — keyboard, mouse, touch, voice, switch, eye tracking, or any combination.

Core Principle

Never assume how someone will interact with your interface. Offer choices. Let the user decide.

The Input Spectrum

People interact with technology through many methods, often combining several at once:

Keyboard — physical, on-screen, or switch-activated
Mouse / trackpad — standard pointer devices
Touch — fingers, stylus, or assistive touch
Voice — speech commands, dictation
Switch devices — single or dual switches scanning through options
Eye tracking — gaze-based selection
Head pointers — head movement controlling a cursor
Sip-and-puff — breath-controlled switches

Design Patterns

Input Equivalence

Every action must be possible through at least keyboard AND pointer (mouse/touch)
Voice input should be available as a third option where practical
Never lock a feature to a single input method
Test: can someone complete this task using ONLY keyboard? ONLY touch? ONLY voice?

Flexible Text Entry

Support physical keyboard, on-screen keyboard, voice dictation, and paste from clipboard
Auto-complete and suggestions reduce typing burden
Don't disable paste in form fields (password managers, assistive tools depend on this)
Allow scanning and OCR for filling in reference numbers or codes

Selection Without Precision

Radio buttons and checkboxes: make the label clickable, not just the control
Dropdowns: allow type-ahead search for long lists
Date pickers: always offer a text field alternative alongside the calendar widget
Colour pickers: provide text input for hex/RGB values

Complex Interactions

Drag-and-drop: always provide button-based reordering
Drawing/annotation: offer text description as alternative
Map interactions: provide address search alongside map selection
Gestures (swipe, pinch): always provide button equivalents

Assessment Questions

Can every task be completed through keyboard alone?
Can every task be completed through pointer alone?
Are there complex interactions (drag, gesture, drawing) that lack simpler alternatives?
Is paste enabled in all text fields?
Do all form controls have clickable labels?

Frequently asked questions

What does the Multi Modal Input AI skill do?

Why use Multi Modal Input on TypingMind?

Because you install it once and use it with any model. Multi Modal Input is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Multi Modal Input in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/multi-modal-input. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Multi Modal Input?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Multi Modal Input?

As many as you like. As long as a model supports skills, you can use Multi Modal Input with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Multi Modal Input AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Cloud Image Bake

openclaw

OrganizationPopular

Bake, select, prove, and safely retire a Cloud Worker image with crabbox and config one-liners.

Acp Router

Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw…

Diffs

Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.

Feishu Doc

Feishu document read/write workflows. Activate when the user mentions Feishu docs, cloud docs, or docx links.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Multi-Modal Input Design

Core Principle

The Input Spectrum

Design Patterns

Input Equivalence

Flexible Text Entry

Selection Without Precision

Complex Interactions

Assessment Questions

Frequently asked questions

Related AI Skills

Set up your own AI workspace now