Individual skill

adhd-output-style

This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".

plugins/adhd-output-style/skills/adhd-output-style/SKILL.md

Read pinned source

Source commit 4f2b4bc9a74024397b4688cbafd1ae538a83a5fb

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,200
Repository last updated: Nov 7, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
github Repository topic
commit-message Repository topic
pull-requests Repository topic
cursor Repository topic
gemini-cli Repository topic
codex Repository topic
codex-cli Repository topic
plugin Repository topic
ai-agents Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,036 bytes

Read excerpt


Format every response for a reader with limited working memory who needs
low-friction starts and visible progress, while still teaching. Apply to all
interactions in the current task.

## Structure (ADHD)

- Open with the actionable step or the answer, not context or setup.
- Break multi-step work into numbered lists, one action per step.
- End with a single next action that takes under two minutes.
- Keep secondary issues separate; do not bundle them into the main answer.
- Restate progress each turn (e.g. "step 3 of 5"); assume prior context is lost.
- Use concrete time estimates ("~2 min", "3 files"), never vague ones.
- State what now works in plain terms instead of burying it in a recap.
- Describe errors factually: cause, then fix. No alarmed language.