i-have-adhd: output shaped for ADHD readers
A persistent output style for ADHD readers — lead with the next action, number steps, give time estimates
- What
- A persistent output style for ADHD readers — lead with the next action, number steps, give time estimates
- Cost
- Free
- Needs
- none — the skill is guidance only, no accounts, keys or tools required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @ayghri's session-persistent output style that reshapes every agent answer so an ADHD reader can act on it: lead with the one next action (not context), number multi-step work in single bounded steps, end with one concrete under-two-minutes action, suppress tangents, restate state every turn ("Step 3 of 5 done: schema updated"), give specific time estimates ("about 15 minutes if tests already cover this"), make wins visible in concrete terms, use a matter-of-fact error tone (cause and fix, never "Uh oh"), cap lists at five, and strip preamble, recaps and closing pleasantries — with when-to-break-the-rules overrides (explain requests, destructive actions, debug spirals, real ambiguity, a rule that would delete the answer itself) and a pre-send checklist that deletes announcement sentences, "anything else?" closers, hedges and idioms, ending on a first-line/last-line test: does the reader know what to do next and what just happened? Invoke with /i-have-adhd; it stays on until "stop adhd mode". Honest caveats: it shapes presentation only and never limits the analysis itself; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: none — the skill is guidance only, no accounts, keys or tools required Install "i-have-adhd: output shaped for ADHD readers" for me. A session-persistent output style for agents: lead every response with the next action, number multi-step work, restate state every turn, suppress tangents, give specific time estimates, make wins visible, use a matter-of-fact error tone, cap lists at five, strip preamble/recaps/pleasantries — with documented overrides for explanations, destructive actions, debug spirals and ambiguity, plus a pre-send checklist. Invoked with /i-have-adhd, stays on until "stop adhd mode". Repository: https://github.com/ayghri/i-have-adhd/blob/main/.cursor/skills/i-have-adhd/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "i-have-adhd". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — invoke with /i-have-adhd when I want the style on, or "stop adhd mode" to turn it off). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.