Disability Disclosure Decision Skill
Whether to tell work about a disability or health condition is one of the genuinely
hard modern career decisions, because both directions carry real cost: disclosing can
unlock accommodations and legal protection and end the exhaustion of hiding — and can
also invite bias, being passed over, or becoming "the sick one." There's no universal
right answer, only the right answer for this person, condition, workplace, and
moment. This skill won't tell you to disclose or not; it maps the specific tradeoffs,
surfaces the options between "full disclosure" and "nothing" that people forget exist,
and — if you choose to — helps you do it well.
What This Skill Produces
- A decision map for your situation: the concrete benefits and risks of disclosing
here, weighted by what you'd gain (accommodations you need now? protection? relief?)
and what you'd risk (this specific workplace's culture, this manager)
- The spectrum of options most people miss: not just all-or-nothing but partial and
targeted disclosure — telling HR but not the team, naming the functional limitation
without the diagnosis, disclosing to get an accommodation vs disclosing generally
- The timing question: application vs offer vs post-start vs point-of-need, and why
each changes the calculus
- If you choose to disclose: a script tuned to the audience and the goal, and the
minimum-disclosure framing (see [[accommodation-request]] for the accommodation route
specifically)
Required Inputs
Ask for (if not already provided):
- The condition and what's actually driving the question (needing an accommodation now?
a performance situation? tired of hiding? a new job?)
- The workplace reality, honestly: culture, this manager, whether others have disclosed
and how it went, and the country's legal protections
- What the user would gain by disclosing and what they most fear
- Their own instinct — this is theirs, and the skill starts from where they lean
Framework
- Clarify the actual goal — it changes everything. "Should I disclose?" usually
hides a specific driver: you need an adjustment, you're being managed for something
the condition explains, or hiding has become unbearable. The right disclosure (who,
how much) follows from the goal. Disclosing to secure an accommodation is a
different, narrower act than disclosing generally.
- Weigh the real, situation-specific tradeoffs. Benefits: accommodations, legal
protection (which in many places attaches once the employer knows), an end to the
masking tax, authenticity. Risks: bias, being sidelined, gossip, "reasonable-
adjustment reluctance." Weight these against this workplace, not a general average —
a supportive team and a hostile one are different decisions.
- Use the whole spectrum. The forgotten middle: tell HR/occupational health but not
your team; disclose the functional limitation and what helps without the diagnosis
([[nt-translator]]/[[accommodation-request]] framing); disclose only at the point of
need. All-or-nothing is a false binary, and naming the options often dissolves the
dilemma.
- Get the timing deliberately. Pre-offer disclosure risks the offer (and is rarely
required); post-offer/pre-start can secure adjustments with more protection;
post-start-at-need is common and often safest. The skill lays out what each timing
buys and costs so it's a choice, not an accident.
- If you disclose, do it well — and it's still your call. A tuned script: to whom,
how much, framed around what you need and can do (not an apology or an
over-share), and in writing where protection or accommodations depend on a record.
And the standing reminder throughout: not disclosing is a completely valid choice,
now or ever.
Output Format
## What's really driving this
[The specific goal behind the question — it shapes everything]
## The tradeoffs, for YOUR situation
Benefits of disclosing here: … · Risks here: … (weighted to this workplace)
## Your options (not just all-or-nothing)
[Full · HR-only · functional-not-diagnostic · point-of-need · none — with what each
gets you]
## Timing
[Application / offer / post-start / at-need — what each buys and costs]
## If you choose to disclose (your call)
[Script tuned to audience + goal · minimum-disclosure framing · in writing where it
protects you]
Reminder: not disclosing is valid, now or ever. This is yours to decide.
Quality Checks
Anti-Patterns
Related
[[accommodation-request]] for the accommodation-specific route (often needs only
functional disclosure); [[coming-out-rehearsal]] shares the whether/how-to-tell
engine; [[nt-translator]] and [[masking-budget]] for the neurodivergent version;
[[disability-benefit-appeal]] for the benefits side.
Example Trigger Phrases
- "Should I tell work about my disability/condition?"
- "Disclose my ADHD/chronic illness at work."
- "Do I tell my employer?"
- "How much do I share?"
1---2name: disability-disclosure-decision3description: "Decide whether, when, how, and to whom to disclose a disability or health condition at work — weighing the real benefits (accommodations, protection, honesty) against the real risks (bias, gossip), tuned to your specific situation. Use when someone says 'should I tell work about my disability/condition', 'disclose my ADHD/chronic illness at work', 'when do I tell my employer', or 'how much do I share'. Produces a decision framework for the situation, a disclosure script if you choose to, and the minimum-disclosure options. Your choice throughout; it never pushes disclosure."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/disability-disclosure-decision7---89# Disability Disclosure Decision Skill1011Whether to tell work about a disability or health condition is one of the genuinely12hard modern career decisions, because both directions carry real cost: disclosing can13unlock accommodations and legal protection and end the exhaustion of hiding — and can14also invite bias, being passed over, or becoming "the sick one." There's no universal15right answer, only the right answer for *this* person, condition, workplace, and16moment. This skill won't tell you to disclose or not; it maps the specific tradeoffs,17surfaces the options between "full disclosure" and "nothing" that people forget exist,18and — if you choose to — helps you do it well.1920## What This Skill Produces2122- A **decision map for your situation**: the concrete benefits and risks of disclosing23 *here*, weighted by what you'd gain (accommodations you need now? protection? relief?)24 and what you'd risk (this specific workplace's culture, this manager)25- The **spectrum of options** most people miss: not just all-or-nothing but partial and26 targeted disclosure — telling HR but not the team, naming the functional limitation27 without the diagnosis, disclosing to get an accommodation vs disclosing generally28- The **timing question**: application vs offer vs post-start vs point-of-need, and why29 each changes the calculus30- If you choose to disclose: a **script** tuned to the audience and the goal, and the31 minimum-disclosure framing (see [[accommodation-request]] for the accommodation route32 specifically)3334## Required Inputs3536Ask for (if not already provided):37- The condition and what's actually driving the question (needing an accommodation now?38 a performance situation? tired of hiding? a new job?)39- The workplace reality, honestly: culture, this manager, whether others have disclosed40 and how it went, and the country's legal protections41- What the user would gain by disclosing and what they most fear42- Their own instinct — this is theirs, and the skill starts from where they lean4344## Framework45461. **Clarify the actual goal — it changes everything.** "Should I disclose?" usually47 hides a specific driver: you need an adjustment, you're being managed for something48 the condition explains, or hiding has become unbearable. The right disclosure (who,49 how much) follows from the goal. Disclosing to secure an accommodation is a50 different, narrower act than disclosing generally.512. **Weigh the real, situation-specific tradeoffs.** Benefits: accommodations, legal52 protection (which in many places attaches once the employer knows), an end to the53 masking tax, authenticity. Risks: bias, being sidelined, gossip, "reasonable-54 adjustment reluctance." Weight these against *this* workplace, not a general average —55 a supportive team and a hostile one are different decisions.563. **Use the whole spectrum.** The forgotten middle: tell HR/occupational health but not57 your team; disclose the functional limitation and what helps without the diagnosis58 ([[nt-translator]]/[[accommodation-request]] framing); disclose only at the point of59 need. All-or-nothing is a false binary, and naming the options often dissolves the60 dilemma.614. **Get the timing deliberately.** Pre-offer disclosure risks the offer (and is rarely62 required); post-offer/pre-start can secure adjustments with more protection;63 post-start-at-need is common and often safest. The skill lays out what each timing64 buys and costs so it's a choice, not an accident.655. **If you disclose, do it well — and it's still your call.** A tuned script: to whom,66 how much, framed around what you need and can do (not an apology or an67 over-share), and in writing where protection or accommodations depend on a record.68 And the standing reminder throughout: not disclosing is a completely valid choice,69 now or ever.7071## Output Format7273```74## What's really driving this75[The specific goal behind the question — it shapes everything]7677## The tradeoffs, for YOUR situation78Benefits of disclosing here: … · Risks here: … (weighted to this workplace)7980## Your options (not just all-or-nothing)81[Full · HR-only · functional-not-diagnostic · point-of-need · none — with what each82gets you]8384## Timing85[Application / offer / post-start / at-need — what each buys and costs]8687## If you choose to disclose (your call)88[Script tuned to audience + goal · minimum-disclosure framing · in writing where it89protects you]9091Reminder: not disclosing is valid, now or ever. This is yours to decide.92```9394## Quality Checks9596- [ ] The actual goal behind the question is surfaced first, and shapes the recommendation97- [ ] Tradeoffs are weighted to this specific workplace, not generic98- [ ] The partial/targeted disclosure options are presented, not just all-or-nothing99- [ ] Timing is laid out as a deliberate choice100- [ ] The skill never pushes disclosure and states plainly that not disclosing is valid101102## Anti-Patterns103104- [ ] Do not push the user to disclose (or to stay silent) — map the tradeoffs, protect105 their autonomy; the choice is theirs106- [ ] Do not assert legal protections/rules as fact — they vary by country and attach107 differently; route to verify108- [ ] Do not treat it as all-or-nothing — the middle options are usually where the good109 answer lives110- [ ] Do not counsel over-disclosure — the goal usually needs the functional info, not111 the medical file112- [ ] Do not minimize the real risks to nudge an uplifting answer — some workplaces are113 genuinely unsafe to disclose in, and honesty about that is the help114115## Related116117[[accommodation-request]] for the accommodation-specific route (often needs only118functional disclosure); [[coming-out-rehearsal]] shares the whether/how-to-tell119engine; [[nt-translator]] and [[masking-budget]] for the neurodivergent version;120[[disability-benefit-appeal]] for the benefits side.121122## Example Trigger Phrases123124- "Should I tell work about my disability/condition?"125- "Disclose my ADHD/chronic illness at work."126- "Do I tell my employer?"127- "How much do I share?"