Consent and Agency
Designing for informed user consent, opt-out, and human override.
Install
/plugin marketplace add Owl-Listener/ai-design-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/ai-design-skills --skill consent-and-agencygit clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/ai-alignment-reasoning/skills/consent-and-agency ~/.claude/skills/consent-and-agencyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
consent-and-agency- Repository
- Owl-Listener/ai-design-skills
- Path
claude-plugin/ai-alignment-reasoning/skills/consent-and-agency/SKILL.md- License
- MIT
- Repo updated
- 9 June 2026
FAQ
What does the Consent and Agency skill do?
Designing for informed user consent, opt-out, and human override.
How do I install the Consent and Agency skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Consent and Agency popular?
It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.
Related skills
Agent Role Design
207Owl-Listener/ai-design-skills
Defining what each agent does, knows, and owns in a multi-agent system.
Behavioral Consistency
207Owl-Listener/ai-design-skills
Ensuring the AI behaves predictably across sessions, edge cases, and modalities.
Bias Detection Design
207Owl-Listener/ai-design-skills
Designing review workflows to surface and mitigate bias in AI outputs.
Context Engineering
207Owl-Listener/ai-design-skills
Designing what information goes into the context window and in what order.
Change Request
292danielvm-git/bigpowers
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.
Feedback Loops
207Owl-Listener/ai-design-skills
User correction, thumbs up/down, inline editing, and reinforcement signals.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.