
- Installs
- 130
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill consent-and-agency- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads consent-and-agency automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
FAQ
What does the consent-and-agency skill do?
Designing for informed user consent, opt-out, and human override.
How do I install consent-and-agency?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill consent-and-agency in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/consent-and-agency/ (personal) or .claude/skills/consent-and-agency/ (project).
Which AI agents can use consent-and-agency?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is consent-and-agency safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains consent-and-agency?
It is published by owl-listener in owl-listener/ai-design-skills. It has 130 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Defining behavioral boundaries — what the AI should and shouldn't do.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Revealing AI capability gradually to match user mental models.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.