Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Accommodation Request

ASecurity

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the in...

1,330 stars
0 votes
0 copies
2 views
Added 9/3/2026
ai-agentsgogitdocumentation

Security Analysis

A100/100

Scanned 9/3/2026

$npx -y skills add mohitagw15856/pm-claude-skills --skill accommodation-request --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Accommodation Request?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Accommodation Request
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mohitagw15856-accommodation-request/badge)](https://www.skillsdirectory.com/skills/mohitagw15856-accommodation-request)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: accommodation-request
description: "Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/accommodation-request.html
metadata:
  {
    "openclaw": { "emoji": "🧠" }
  }
---

# Accommodation Request Skill

Reasonable accommodations (US: ADA; UK: reasonable adjustments under the Equality Act;
similar elsewhere) are a right, but getting them often stalls on how the request is
framed: people over-share medical detail, ask for a vague "help," or frame it as a
favor rather than an adjustment to a barrier. Employers and institutions respond best
to a specific request that names the *barrier* and the *adjustment that removes it* —
they generally don't need your diagnosis, only the functional limitation and what
helps. This skill writes that request, guides how much to disclose, and prepares you
for the interactive back-and-forth that follows. It is not legal advice; it routes to
the formal process and to advocacy if you hit resistance.

## What This Skill Produces

- A **barriers-and-adjustments map**: for each thing that's hard, the specific
  workplace/course barrier and the concrete adjustment that removes it (framed as an
  adjustment to a barrier, not a personal favor)
- The **request letter/email**: to the right person (HR, disability services, manager
  per the process), citing the process, naming the adjustments, and inviting the
  interactive dialogue
- **Disclosure guidance**: how much to share (usually the functional limitation and
  what helps, not the diagnosis), what you're not obliged to reveal, and where medical
  documentation is genuinely needed
- A **process plan**: the interactive/good-faith dialogue that's expected, how to
  handle "that's not possible," alternatives, and escalation to advocacy or the formal
  complaint route if needed

## Required Inputs

Ask for (if not already provided):
- The setting (workplace or education) and country/system, since the legal framework
  and process differ
- The specific difficulties and the tasks/situations where they bite (the barrier),
  and what adjustments would help
- What the user is comfortable disclosing and to whom, and whether there's an existing
  process (HR policy, disability services office)
- Any history (a prior refusal, a difficult manager) that shapes strategy

## Framework

1. **Frame around barrier → adjustment, not diagnosis.** The request names the barrier
   ("open-plan noise makes focused work impossible," "fixed exam timing conflicts with
   medication effects") and the specific adjustment that removes it (noise-cancelling/
   a quiet space, extra time/a separate room). The employer's duty attaches to the
   barrier and the reasonable fix, not to your medical history.
2. **Disclose the minimum that works.** Generally you must share enough functional
   information to justify the adjustment and may need medical documentation of the
   limitation — but not your full diagnosis or records. The skill helps calibrate:
   enough to establish the need, no more, and names what you're not obliged to reveal.
3. **Send it to the right process.** Route to whoever owns adjustments (HR, disability/
   access services, occupational health) rather than only a manager who can't approve,
   cite the relevant policy/law framing, and put it in writing so there's a record.
4. **Expect the interactive dialogue — and engage it.** These processes are meant to be
   a good-faith back-and-forth: they may propose alternatives, ask for documentation, or
   push back on cost/feasibility. The skill preps constructive responses, the
   "undue-hardship/reasonableness" conversation, and holding firm on the barrier while
   being flexible on the exact fix.
5. **Know the escalation and get support.** If met with refusal, delay, or retaliation:
   the formal grievance/complaint route, disability advocacy organizations, and (where
   warranted) legal advice. Retaliation for requesting accommodations is itself usually
   unlawful — flag it, and route to real help rather than adjudicating it here.

## Output Format

```
## Barriers → adjustments
| The barrier (situation/task) | The adjustment that removes it |

## Your request (send this)
[To the right owner · cites the process · names the adjustments · invites the
interactive dialogue · in writing]

## What to disclose (and what you needn't)
[The functional info to share · documentation if genuinely needed · what you're not
obliged to reveal]

## The back-and-forth
[Expect a good-faith dialogue · handling "not possible"/alternatives · firm on barrier,
flexible on fix]

## If you hit a wall
[Grievance/complaint route · disability advocacy orgs · legal advice · retaliation is
usually unlawful — get help]

⚠ Not legal advice. Frameworks differ by country and situation; route to the formal
process and to an advocate/lawyer if you meet resistance.
```

## Quality Checks

- [ ] Every request is framed as barrier → adjustment, not as a diagnosis disclosure or
      a favor
- [ ] Disclosure is calibrated to the minimum needed, and what's not required is stated
- [ ] It's routed to the actual owner of the process, in writing
- [ ] The interactive/good-faith dialogue is anticipated with constructive responses
- [ ] An escalation/advocacy path and the not-legal-advice line are present

## Anti-Patterns

- [ ] Do not over-disclose medical detail — the barrier and the fix are what matter
- [ ] Do not assert specific legal entitlements or "undue hardship" thresholds as fact —
      they vary; route to the process and to advocacy
- [ ] Do not frame it as asking a favor — it's a request to remove a barrier, often a legal duty
- [ ] Do not counsel giving up at first refusal — the interactive process and escalation
      exist for exactly that
- [ ] Do not treat retaliation as normal — flag it and route to real help

## Related

[[disability-disclosure-decision]] for the whether/how of telling work at all;
[[disability-benefit-appeal]] for the benefits side; [[venue-access-check]] and
[[accessible-travel-planner]] for physical access; [[nt-translator]] for the workplace-
communication layer.

Attribution

mohitagw15856mohitagw15856
View sourceSee grades on GitHubMore from mohitagw15856 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →