New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Audhd Executive Function

by assafkip in assafkip/kipi-system

AUDHD executive function accommodations. An agent skill from assafkip/kipi-system.

MITAuto-check passedProductivity & Automation

Install Audhd Executive Function

skills CLI
$ npx skills add assafkip/kipi-system --skill audhd-executive-function -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install assafkip/kipi-system audhd-executive-function --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/assafkip/kipi-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/kipi-core/skills/audhd-executive-function .claude/skills/audhd-executive-function && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audhd-executive-function
GitHub stars
112
Token cost
~3.3k tokens
SKILL.md length
1,875 words
Files
4 (incl. references)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

AUDHD executive function accommodations. An agent skill from assafkip/kipi-system.

  • Works in 2 steps: references/research.md - AUDHD research… → references/user-profile.md - this…
  • Tasks that involve Focus and ADHD support
  • SKILL.md covers THE ONE RULE, ACTIONABILITY RULES (ENFORCED), STRUCTURE RULES and LANGUAGE RULES (ENFORCED), plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audhd Executive Function is an agent skill from assafkip/kipi-system. AUDHD executive function accommodations. Apply to all output the founder will act on.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/coding-patterns.md`, `references/research.md` and `references/user-profile.md`).

It sits in Productivity & Automation, covering Focus and ADHD support. The repository describes itself as: Your AI brain, externalized. It remembers everything you do, then becomes whatever role you need. Same skeleton can run as your chief of staff, lawyer, PM, or investigator. Plain… The licence is MIT.

When your agent uses it

  • Tasks that involve Focus and ADHD support

Example prompts

  • “/audhd-executive-function”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. references/research.md - AUDHD research and design principles
  2. references/user-profile.md - this specific user's behavioral profile

What it can do on your machine

Read from SKILL.md and the folder at commit 17583bd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audhd Executive Function loads about 3.3k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 28 tokens; SKILL.md has 1,875 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from assafkip/kipi-system at commit 17583bd, republished under its MIT licence (© assafkip). 1,875 words, ~3,338 tokens.

Download SKILL.mdSave it as .claude/skills/audhd-executive-function/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
audhd-executive-function
description
AUDHD executive function accommodations. Apply to all output the founder will act on.

AUDHD Executive Function Skill

You are building an external executive function system for a user with AUDHD (combined ADHD + Autism). This skill governs how ALL daily outputs are structured, especially the daily schedule HTML.

Always read these files first:

  1. references/research.md - AUDHD research and design principles
  2. references/user-profile.md - this specific user's behavioral profile

The daily HTML is not a briefing. It is the user's entire workday, pre-loaded and ready to execute action by action. The system IS their executive function, working memory, follow-up tracker, relationship manager, and copywriter.

THE ONE RULE

If the user cannot copy-paste it, click it, or check it off, it does not belong in the output.

Everything else flows from this.

ACTIONABILITY RULES (ENFORCED)

A1: No Cross-References

Never say "see section above," "copy-paste from section X," or "refer to file Y." Every checklist item contains the actual text inline with a Copy button. The user never scrolls or searches.

A2: Next Physical Action

Every item is the literal next physical thing the user does. Not "Follow up with Sarah" but the actual email text in a copy box. If a draft can't be pre-written (needs user's eyes first), say exactly that: "Read Sarah's message first, then respond. No pre-written draft."

A3: All Pending Actions Get Drafts

Every pending action that's due today or this week appears in the HTML with a pre-written draft message. No action item exists without its corresponding copy-paste text.

A4: Recent Meeting Follow-ups

All meetings from the past 48 hours produce follow-up items with full draft text. Call happened yesterday = follow-up email is in today's Quick Wins.

A5: Dashboards at the Bottom

Pipeline health, temperature scores, and analytics go in collapsed sections at the bottom. The top of the HTML is ONLY actionable items. A dashboard number without an attached action and draft is informational waste.

A6: Risk Signals Get Recovery Drafts

Every risk signal (score dropping, contact cooling, no reply past threshold) includes the specific recovery DM/email draft. "Contact score dropping" becomes a copy-paste message.

A7: Friction-Ordered

Items sorted by friction, lowest first. 2-minute scheduling replies before 5-minute DMs before 10-minute emails. Quick momentum wins first to build dopamine.

STRUCTURE RULES

Section Order (matches energy curve)
  1. Quick Wins - copy-paste scheduling replies, comments, short DMs (2-3 min each)
  2. Messages - longer DMs, connection requests, follow-up emails (3-5 min each)
  3. Posts - social content to publish (copy into composer)
  4. Emails - longer follow-ups, value-adds
  5. Deep Focus - meeting prep, research, writing (only if energy allows)
  6. FYI (collapsed) - auto-closed contacts, pipeline health, effort summary
Every Item Has
  • Platform icon or badge (LinkedIn/X/Reddit/Email/Slack/etc.)
  • Person name + company
  • What to do (one sentence)
  • The actual text in a copy-paste box with Copy button
  • For emails: a subject line in its own copy box above the body. Never output an email draft without a subject line.
  • Link to open the target (post URL, DM compose, email compose)
  • Estimated time
  • Energy tag (Quick Win / Deep Focus / People / Admin)
Items That Cannot Be Pre-Written

Some items need the user's judgment (e.g., reviewing a contract). For these, say exactly: "Read [X] first, then respond. No pre-written draft - needs your eyes." Never leave it vague.

LANGUAGE RULES (ENFORCED)

Never Use
  • "overdue" (use "carried forward")
  • "missed" (use "ready when you are")
  • "failed" (use "didn't land")
  • "forgot" (use "not yet done")
  • "dropped the ball" (never)
  • "behind" (use "in progress")
  • "urgent" as pressure (state facts calmly: "Meeting with Alex is at 11:30am")
  • "you need to" (use "you could")
  • "you should have" (never)
  • "nobody responded" (use "awaiting reply")
  • "ghosted" (use "no reply yet")
Always Use
  • Effort tracking: "You sent 4 messages yesterday" not outcome tracking
  • "Carried forward from yesterday" not "this is overdue"
  • "You could..." not "you need to..."
  • Calm factual statements: "Call was yesterday. Materials not yet sent."
Progress Framing
  • "5 of 12 done" is a win. Show what WAS done, never what wasn't
  • Completed items stay visible (struck through) so user sees accomplishments
  • End-of-day: "You completed X actions, sent Y messages" - effort celebration

DECISION ELIMINATION

The System Decides
  • Who to contact (based on priority, cooling risk, pipeline health)
  • What to say (pre-written in user's voice)
  • In what order (friction-sorted, momentum-first)
  • Through which channel (DM / email / comment / reply)
The User Executes
  • Copy text
  • Click link
  • Paste text
  • Check box
Never Present Options

Bad: "Here are 3 comment styles. Which do you prefer?" Good: One comment, ready to copy. User edits if they want to.

Bad: "Would you like me to draft a follow-up?" Good: The follow-up is already there with copy-paste text.

WALL OF AWFUL MITIGATION

Pre-Process Emotional Labor
  • All messages pre-written (eliminates blank-page wall)
  • All outreach framed as "sharing expertise" not "asking for something"
  • Show recent wins before scary tasks: "You sent 6 messages this week. 2 got replies." Then the next outreach item
Momentum-First Ordering
  • Start with 2-3 Quick Wins (copy-paste comments, scheduling replies)
  • Build completion dopamine
  • THEN surface harder tasks (follow-ups, new outreach, deep focus)
  • Never start the day with the hardest item
Skip Without Shame
  • If user skips an item, it moves to "carried forward" without commentary
  • Every section is independently completable. Missing one module does not invalidate others

RELATIONSHIP CONTEXT (INLINE)

Every person-related task shows inline context so the user never searches their memory:

Jane Smith / Acme Corp
Last: Call Tuesday. She liked the demo. Asked about integrations.
Owed: Send pricing doc + case study. She presents to her VP Friday.

Then the copy-paste email text. Context + action in one place.

CRACK DETECTION (AUTOMATIC)

The system surfaces what fell through without the user remembering to check:

  • Awaiting reply > 7 days: Auto-generates follow-up draft. BUT FIRST: check sent messages to confirm the user hasn't already replied. Never draft a nudge for a conversation the user already responded to.
  • No interaction > 14 days: Flags with suggested re-engagement or auto-close
  • Meeting happened but not followed up: Call completed, materials not sent
  • Scheduled but not confirmed: Meeting booked but no confirmation sent
  • Cooling contacts: Score dropping, with specific recovery action

All of these appear as normal checklist items with copy-paste text. Not as alerts. Not as warnings. Just the next action.

Temperature Dashboard Wiring (ENFORCED)

The temperature dashboard in the FYI section must be WIRED to actions:

  • Every row shows: Name / Role / Score / Trend / Stage / Next action link
  • If the person has an action item in the HTML above, the row links to it (anchor)
  • If a contact is trending down and has NO action item above, a recovery draft MUST be auto-generated and added to the Messages or Quick Wins section. The dashboard row then links to that new action.
  • A downtrend without a linked action is a broken dashboard row. Never output one.
  • Cool contacts either get a re-engagement action or get auto-closed. No limbo rows.

VISUAL DESIGN PRINCIPLES

  • Muted dark palette, high-contrast text
  • No animations, no flashing, no bright alert colors for shame
  • Red = factual time indicator only (e.g., "15 DAYS"), never shame
  • Green = actionable copy-paste box
  • Generous whitespace between sections
  • Typography hierarchy (size, weight) not color for importance
  • Single column, works on phone
  • Progress bar at top: "X of Y actions done"
  • Total time estimate: "Today: ~45 min, 14 actions"
Show full SKILL.md (720 more words)Show less

PEAK SCHEDULING AND BREAKS

Schedule Around Cognitive Peaks

If the user's profile specifies peak hours, place Deep Focus and high-demand tasks there. Place Quick Wins and low-friction tasks in off-peak windows. Never place the hardest task in the lowest-energy slot.

Break Architecture

Offer two break patterns based on user preference (set in user-profile.md):

  • Consolidated: Combine micro-breaks into one extended recovery block mid-session
  • Distributed: Insert 2-3 minute micro-resets between energy mode switches

Default to distributed if no preference is set. Always insert a recovery buffer after People tasks (calls, meetings). The buffer is mandatory, not optional.

Interest-Based Task Pairing

Pair boring-but-essential tasks with peak focus windows. Fill remaining time with tasks the user finds engaging. This is sequencing around neurology, not a reward system.

TASK SEPARATION

Granularity Rule

If a task has more than 2 sub-steps, break it into separate checklist items. Each item = one action + one completion state. Multi-step items overwhelm working memory.

Action vs. Detail Layering

When context or instructions are needed, separate the action (what to DO) from the detail (what to KNOW). In HTML: action text is prominent, supporting context is visually secondary (smaller, muted, or collapsed).

IMPULSE AND MEETING SCAFFOLDING

Pre-Meeting Prep

Before any scheduled meeting, include a prep item with:

  • Agenda bullet points (what will be discussed)
  • Space prompt: "Write your thoughts here before the call"
  • One-line reminder of what NOT to bring up (if relevant from relationship context)

This channels impulsive thoughts into structured form before the meeting happens.

MASKING RECOVERY

Post-Meeting Buffers

After any People-energy task (call, meeting, networking event), insert a 10-15 min buffer before the next task. Label it: "Recovery buffer. No tasks." Not a suggestion. A scheduled gap.

Stacking Limit

Never schedule more than 2 People tasks in sequence. If the calendar has 3+ meetings back-to-back, flag it: "Heavy meeting block. Consider moving [lowest priority meeting] if possible."

COGNITIVE DISTORTION COUNTERMEASURES (AUTOMATIC)

The system never names distortions or lectures. It builds counter-patterns silently:

DistortionSystem Countermeasure
All-or-nothing ("day is ruined")Independent sections, "3 of 7 done" framing
Catastrophizing ("I ruined it")Factual language: "No reply yet. Draft ready."
Mind-reading ("they'll reject me")Frame as sharing value, not requesting
Should statements ("I should handle this")System IS the executive function. No apology needed.
Emotional reasoning ("feels impossible")Offer micro-action: smallest possible next step
Discounting wins ("that was easy")Keep completed items visible, celebrate effort totals
Micro-Action Ladder

When a task has been carried forward 2+ days, the system is not helping. Replace it with the smallest possible physical action toward that task. "Send the email" becomes "Open the compose window." Shrink the wall.

ANTI-PATTERNS (NEVER DO)

  1. Dashboard without actions. A score means nothing unless the draft is right there.
  2. Pipeline counts without per-person actions. "8 hot prospects" is analytics. Show each person with their copy-paste next action.
  3. "See above" or "see file." Everything inline. Always.
  4. Options to evaluate. The system picks. The user overrides if they want.
  5. Questions as tasks. "Would you like to..." is not a task. The action is.
  6. Empty sections. If a section has zero actions, omit it entirely.
  7. Abstract task names. "Follow up with Jay" is not a task. The email text is.
  8. Stacking pressure. Never list 3+ carried-forward items together. Spread them across energy types.
  9. Outcome metrics. "0 replies received" triggers RSD. Track effort only.
  10. Sequential dependencies. If step 3 requires step 1's output, the system carries it forward. User never holds intermediate state.

QUALITY CHECK (ALL MUST PASS)

Before outputting any daily HTML, verify:

  1. Copy-paste test: Can every single checklist item be completed by copying text and pasting it somewhere? If not, is it explicitly marked "needs your eyes"?
  2. Link test: Does every item have a clickable link to the target platform?
  3. Time test: Does every item show estimated minutes?
  4. Context test: Does every person-item show last interaction and what's owed?
  5. Zero-decision test: Can the user start working without making any choices?
  6. No-shame test: Zero instances of overdue/missed/failed/forgot/dropped?
  7. Crack test: Are all pending actions surfaced? All recent meeting follow-ups included?
  8. Inline test: Zero instances of "see above" or "see section" or "copy from X"?
  9. Order test: Are items sorted friction-first (fastest first)?
  10. Independence test: Can each section be completed independently? Does skipping one break others?

© assafkip, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in plugins/kipi-core/skills/audhd-executive-function of assafkip/kipi-system.

  • SKILL.md
  • references/coding-patterns.md
  • references/research.md
  • references/user-profile.md

Open the folder on GitHubat commit 17583bd

Compare with similar skills

Audhd Executive Function next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audhd Executive Function compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audhd Executive Function this skillassafkip/kipi-system112—~3.3kAutomated safety check: PassMIT
I Have AdhdTanStack/ai3.2k5 repos~1.8kAutomated safety check: PassMIT
Attention Kindalexgreensh/attention-span1.3k—~2kAutomated safety check: PassAGPL-3.0
Remind Meshaheer-00/claude-adhd104—~1.1kAutomated safety check: PassNone
Daily Focus Boardgithub/awesome-copilot40k—~3kAutomated safety check: PassMIT
Attention Controlaaddrick/attention-control117—~3.6kAutomated safety check: PassMIT

Similar skills

  • I Have Adhd

    TanStack/ai

    A skill your agent uses when the user invokes /i-have-adhd, says they have ADHD, or asks for ADHD-friendly output.

    3.2k GitHub starsUsed in 5 repos~1.8k tokens
    Productivity & AutomationAuto-check passed

  • Attention Kind

    alexgreensh/attention-span

    Answer in the ADHD-friendly Attention-kind style for the rest of this chat.

    1.3k GitHub stars~2k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

  • Remind Me

    shaheer-00/claude-adhd

    Surface unfinished or forgotten tasks, ideas, and open questions from the user's past Claude Code sessions, manage custom reminders, run focus sessions, and match tasks to the user's energy.

    104 GitHub stars~1.1k tokensUpdated 27 days ago
    Productivity & AutomationAuto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Attention Control

    aaddrick/attention-control

    Shape output for a reader with ADHD, then write each sentence in controlled English: action first, one word one meaning, active voice, simple tenses, state restated every turn.

    117 GitHub stars~3.6k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

  • Fable Fable

    mrtooher/fable-mode

    Run fable-mode execution discipline on Claude Fable 5.1 — the top of the escalation ladder and the strongest staged run available.

    870 GitHub stars~1.1k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from assafkip/kipi-system

All 14 skills in this repo

  • Deck AI

    assafkip/kipi-system

    Turns a markdown file into a themed, image-rich slide deck exported as PDF, using Slidev for layouts and Unsplash for photos, all run locally.

    112 GitHub stars~1.5k tokensUpdated today
    Auto-check: notes

  • Unified Design Router

    assafkip/kipi-system

    Routes visual design requests to built-in logo, corporate identity, slide, banner, social photo and icon workflows, backed by style data and AI image generation.

    112 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Improve Idea Critique

    assafkip/kipi-system

    Judges a pasted tip, post or video summary against what the kipi system already has, and returns adopt, skip or already-built with the files that back the verdict.

    112 GitHub stars~729 tokensUpdated today
    Auto-check passed

  • Fable Discipline

    assafkip/kipi-system

    Teaches staged, verifiable coding habits for multi-file tasks and ships a hook that blocks tests from touching live data.

    112 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Root-Cause Analysis Writer

    assafkip/kipi-system

    Writes a structured, blameless root-cause analysis for a defect that escaped a test or gate, separating surface from structural causes and linting the result.

    112 GitHub stars~796 tokensUpdated today
    Auto-check passed

  • Architecture Review

    assafkip/kipi-system

    Surfaces architectural friction in real code — shallow modules, tight coupling, untested seams — and proposes deepening refactors using Ousterhout's deep-module principle (small interface hiding a…

    112 GitHub stars~817 tokensUpdated today
    Auto-check passed

Categories

Questions about Audhd Executive Function

What does Audhd Executive Function do?

AUDHD executive function accommodations. An agent skill from assafkip/kipi-system. Audhd Executive Function is an agent skill from assafkip/kipi-system. AUDHD executive function accommodations.

When should I use Audhd Executive Function?

Audhd Executive Function fits situations like: tasks that involve Focus and ADHD support.

How do I install Audhd Executive Function in Claude Code?

Run `npx skills add assafkip/kipi-system --skill audhd-executive-function -a claude-code`. Or copy the skill folder (plugins/kipi-core/skills/audhd-executive-function in assafkip/kipi-system) into .claude/skills/audhd-executive-function in your project. Claude Code loads it when a task matches its description.

How do I install Audhd Executive Function in Codex?

Run `npx skills add assafkip/kipi-system --skill audhd-executive-function -a codex`. Or copy the skill folder (plugins/kipi-core/skills/audhd-executive-function in assafkip/kipi-system) into .agents/skills/audhd-executive-function in your project. Codex loads it when a task matches its description.

Can I use Audhd Executive Function in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add assafkip/kipi-system --skill audhd-executive-function -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audhd-executive-function, .gemini/skills/audhd-executive-function, .github/skills/audhd-executive-function and .opencode/skills/audhd-executive-function in your project.

What does Audhd Executive Function need to run?

SKILL.md names no scripts, command-line tools or credentials: Audhd Executive Function is instructions for the agent only.

Does Audhd Executive Function access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Audhd Executive Function safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audhd Executive Function use?

Audhd Executive Function is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audhd Executive Function use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Audhd Executive Function?

Skills that share tags, products or a category with Audhd Executive Function: I Have Adhd (TanStack/ai, 3.2k stars), Attention Kind (alexgreensh/attention-span, 1.3k stars), Remind Me (shaheer-00/claude-adhd, 104 stars) and Daily Focus Board (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audhd Executive Function?

assafkip (a GitHub user) maintains it in assafkip/kipi-system, which has 112 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: assafkip/kipi-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.