Preference Audit logo

Preference Audit

Community
Owl-Listener
preference-audit

Audit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling. Chains: user-preference-respect, responsive-accessibility, colour-independence. Use when reviewing an existing product for adaptive behaviour.

Overview

PublisherOwl-Listener
Repositoryinclusive-design-skills
Skill namepreference-audit
Stars
108
Forks
28
Bundled files
Instructions only
LicenseMIT
Links
  • 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 Preference Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/preference-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/adaptive-interfaces/skills/preference-audit .claude/skills/preference-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Preference Audit 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 Preference Audit 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 Preference Audit 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.

User Preference Audit

Test whether an existing interface correctly detects and responds to user preferences — the accessibility settings people have deliberately chosen.

Process

Step 1: Test Motion Preferences

Using user-preference-respect, enable prefers-reduced-motion and navigate the entire interface. Document:

  • Animations that continue playing
  • Transitions that still slide or fade
  • Parallax effects that remain active
  • Autoplay video or carousels that don't stop
  • Any motion that serves no functional purpose

Step 2: Test Contrast and Colour Preferences

Enable prefers-contrast (more) and forced-colors mode. Using user-preference-respect and colour-independence, document:

  • Elements that become invisible or indistinguishable
  • Focus indicators that disappear
  • Interactive elements that lose their borders
  • Colour-only status indicators that become meaningless
  • Charts or visualisations that become unreadable

Step 3: Test Colour Scheme

Switch between light and dark modes. Document:

  • Content that becomes illegible in one mode
  • Images or icons that don't adapt
  • Hardcoded colours that clash with the theme
  • Contrast failures specific to one mode

Step 4: Test Text Scaling and Zoom

Using responsive-accessibility, test at 200% browser zoom and with system font size at maximum. Document:

  • Text that overflows or gets clipped
  • Layouts that break or overlap
  • Horizontal scrolling that appears
  • Fixed-height containers that truncate content
  • Interactive elements that become unreachable

Step 5: Test Combinations

Test realistic combinations:

  • Dark mode + high contrast + reduced motion
  • 200% zoom + large system font
  • Forced colours + reduced motion

Document any failures that only appear in combination.

Output

Deliver an audit report:

  1. Summary — which preferences are respected, which are ignored
  2. Preference-by-preference findings — specific failures for each
  3. Combination failures — issues that appear only when multiple preferences are active
  4. Fix list — prioritised by severity and number of users affected

Severity definitions:

  • Critical — preference is completely ignored, causing harm or blocking access
  • Major — preference is partially respected, significant gaps remain
  • Minor — preference is mostly respected, edge cases need fixing

Frequently asked questions

What does the Preference Audit AI skill do?

Audit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling. Chains: user-preference-respect, responsive-accessibility, colour-independence. Use when reviewing an existing product for adaptive behaviour.

Why use Preference Audit on TypingMind?

Because you install it once and use it with any model. Preference Audit 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 Preference Audit in TypingMind?

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

Which AI models can use Preference Audit?

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 Preference Audit?

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

Is the Preference Audit 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇