AgentStack
SKILL verified MIT Self-run

Document

skill-owl-listener-inclusive-design-skills-document · by Owl-Listener

Document accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping. Use when a feature is being designed or shipped and accessibility decisions need to be captured.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-owl-listener-inclusive-design-skills-document

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Document? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Document Accessibility Decisions

Capture all accessibility decisions for a feature in a single, structured record that will survive team changes and redesigns.

Process

Step 1: Identify Decisions

List every design or implementation choice that affects accessibility:

  • Interaction patterns chosen
  • Content and language decisions
  • Visual design decisions
  • What was included and what was deferred
  • Tradeoffs made under constraints

Step 2: Document Each Decision

Using decision-documentation, for each decision record:

  • Context: what prompted the decision
  • Decision: what was chosen
  • Alternatives: what was considered and rejected
  • Impact: who benefits, who is affected
  • Evidence: what supported the decision

Step 3: Analyse Tradeoffs

Using tradeoff-analysis, for any decision where accessibility was compromised or where user needs conflicted:

  • Who benefits from each option
  • Who is harmed by each option
  • Severity asymmetry (blocked vs friction)
  • Remediation plan for excluded users
  • Review date

Step 4: Map to Standards

Using compliance-mapping, map each decision to the relevant WCAG criteria:

  • Which criteria does this decision satisfy
  • Which criteria does this decision affect
  • Are there any conformance risks

Output

Deliver a feature accessibility decision record:

  1. Feature summary — what was built and for whom
  2. Decision log — each decision in the standard format
  3. Tradeoff register — any tradeoffs with remediation plans
  4. Compliance map — WCAG criteria coverage and gaps
  5. Open items — deferred decisions that need future resolution

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.