mcpField
C
consent-and-agency

consent-and-agency

github.com/owl-listenerDesign & UI191131 installsUpdated 20w ago
Repository

About consent-and-agency

A design skill for keeping users informed and in control when AI processes information or takes action on their behalf. It covers consent, overrides, reversibility, and ways to withdraw from AI assistance.

Key features

  1. 01Transparency about data use and actions
  2. 02Opt-in activation and preference controls
  3. 03Undo and override mechanisms
  4. 04Progressive and contextual consent
  5. 05Withdrawal and exit paths

Use cases

  1. 01Designing permission flows for specific AI actions
  2. 02Providing ways to undo or stop AI actions
  3. 03Explaining data use and limitations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/ai-design-skills --skill consent-and-agency

After installing, type/consent-and-agencyin Claude Code to confirm it loaded.

Details

From the project README

Consent and Agency

AI products make decisions, take actions, and process information on behalf of users. Consent and agency design ensures users remain in control — understanding what the AI does, agreeing to it, and being able to override it.

Informed Consent for AI

Users should understand and agree to:

  • What data the AI uses: Conversation history, personal data, uploaded documents, browsing behaviour
  • What the AI does with it: Training, personalisation, sharing with third parties, storage
  • What actions the AI takes: Sending messages, making changes, accessing systems
  • What the AI can't do: Limitations that might affect the user's expectations Consent is not a checkbox at sign-up. It's an ongoing design challenge throughout the experience.

Designing for Agency

Agency means the user feels — and is — in control:

  • Opt-in over opt-out: AI features should be activated by the user, not imposed
  • Reversibility: AI actions should be undoable wherever possible
  • Override mechanisms: The user can always stop, redirect, or override the AI
  • Exit paths: The user can disengage from AI assistance at any point without penalty
  • Preference controls: The user can adjust AI behaviour, scope, and autonomy levels

Consent Patterns

  • Progressive consent: Ask for permission incrementally as new capabilities are needed, not all at once
  • Contextual consent: Ask at the moment the action is about to happen, not in advance
  • Granular consent: Let users consent to specific actions or data uses, not blanket permissions
  • Revocable consent: Users can withdraw consent and have that withdrawal take effect

Agency Anti-Patterns

  • Dark patterns: Making it hard to opt out or override the AI
  • Consent fatigue: Asking for permission so often that users click through without reading
  • Learned helplessness: AI does so much that users forget how to do things themselves
  • Invisible actions: The AI takes actions the user doesn't know about
  • Irreversible defaults: AI actions that can't be undone without user awareness

Design Artefacts

  • Consent flow diagrams per feature
  • Agency checkpoint specifications
  • Override mechanism inventory
  • Data use transparency matrix
  • Opt-out path designs

Comments

Markdown supported