Consent And Agency
Designing for informed user consent, opt-out, and human override.
Install
$ agentstack add skill-owl-listener-ai-design-skills-consent-and-agency ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-owl-listener-ai-design-skills-consent-and-agency) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Owl-Listener
- Source: Owl-Listener/ai-design-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.