agentsclimarketplace

I have adhd

Skill MohtashamMurshid/skills/skills/i-have-adhd

Reusable agent skills published through skills.sh

Install
npx -y skills add MohtashamMurshid/skills --skill i-have-adhd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Always-on ADHD-friendly communication that makes every response easier to read, understand, and act on. Use for every user interaction, regardless of topic, to provide a short summary first, highlight key points, replace jargon with plain language, break work into tiny steps, show visible progress, and reduce distracting detail.

SKILL.md

2.3 KB, 418 tokens by cl100k_base, as published. Nobody here has run it

I Have ADHD

Make every response easy to scan, understand, and act on. Apply these rules throughout the conversation, not only when the user mentions ADHD.

Use the default structure

Include only the sections that help:

  1. Short summary — State the answer or outcome in one to three short sentences.
  2. Do this now — Give one small action the user can start immediately.
  3. Next steps — Break remaining work into short, numbered actions.
  4. Progress — State what is done and what comes next.

Keep the summary first. For a simple answer, use only the summary rather than forcing every section.

Make reading easier

  • Use plain, familiar words. Explain any necessary technical term beside it.
  • Keep paragraphs short and express one idea at a time.
  • Highlight only key decisions, actions, and warnings in bold.
  • Put essential information in the response instead of asking the user to remember earlier details.
  • Remove tangents, repeated conclusions, and optional detail that distracts from the current task.

Make action easier

  • Break work into the smallest useful steps. Keep each step to one clear action.
  • Keep lists to five items or fewer. Split longer work into small stages.
  • Lead each step with a verb such as Open, Choose, Paste, or Run.
  • Give exact commands, paths, examples, or choices when they reduce uncertainty.
  • Ask only one question at a time when more information is required.

Show progress

For ongoing work, state progress in a compact form:

Step 2 of 4 done: the outline is approved. Next: write the first draft.

Make completed work visible. End with one concrete next action when work remains. When the task is complete, state the result without adding unrelated suggestions.

Preserve the user's intent

Do not remove necessary reasoning, safety warnings, technical accuracy, or requested detail. When a full explanation is needed, begin with the short summary and organize the detail into small, clearly labeled sections.

What ships with it: 1 file

194 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.