# How to Fork and Edit the i-have-adhd SKILL.md for Customization > Learn to fork and edit the i-have-adhd SKILL.md file for custom configuration. Follow simple steps to personalize your skill's metadata and rules. - Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd) - Tags: how-to-guide - Published: 2026-07-31 --- **To customize the i-have-adhd skill, fork the repository on GitHub, clone your fork locally, edit the [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) file at [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) to modify metadata or behavioral rules, then push changes to apply your personalized configuration.** The **i-have-adhd** repository by ayghri implements ADHD-friendly conversational behaviors through declarative YAML-based skills. Each skill is self-contained in a **SKILL.md** file that requires no code changes to customize, making it easy to fork and edit the i-have-adhd SKILL.md to match your specific workflow needs. ## Understanding the SKILL.md Structure The core skill definition resides in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md). This file contains a YAML front-matter block (lines 1-11) that defines the **name**, **description**, **license**, and **metadata** including tags and category. Following the front-matter, the file contains plain-text behavioral rules that the runtime enforces when the skill is invoked via `/i-have-adhd`. Because the architecture is data-driven, you customize behavior by editing declarative text rather than source code. ## Step-by-Step: Fork and Edit i-have-adhd SKILL.md ### Fork the Repository on GitHub Navigate to the `ayghri/i-have-adhd` repository and click the **Fork** button. Select your GitHub account as the destination to create a copy under your own namespace with full write access. ### Clone Your Fork Locally Open your terminal and clone your forked repository to your local machine: ```bash git clone https://github.com//i-have-adhd.git cd i-have-adhd ``` ### Customize the YAML Metadata Edit lines 1-11 of [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) to update the skill identity. You can modify the description, add custom tags under `metadata.hermes.tags`, or change the category to better organize your personal skill library: ```yaml name: i-have-adhd description: 'Personalized ADHD-friendly output with weekly progress tracking' license: MIT metadata: hermes: tags: [ADHD, Output Style, Productivity, Weekly-Review] category: productivity related_skills: [] ``` ### Modify the Behavioral Rules After the front-matter block, append or edit rules in the plain-text section. For example, add a new rule prompting users to log daily wins. The runtime applies these rules verbatim during sessions: ```markdown ### 11. Log a daily win After each session, prompt the user: "What was your biggest win today?" Store the response for later review. ``` ### Commit and Push Your Changes Stage your modifications and push them to your fork: ```bash git add skills/i-have-adhd/SKILL.md git commit -m "Add custom tag and daily-win rule" git push origin main ``` ## Loading Your Customized Skill Configure your assistant or bot to load skills from your forked repository URL. When you invoke `/i-have-adhd`, the runtime reads your updated [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) at [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) and applies your customized metadata and rule set. ## Summary - The skill definition lives at [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) with YAML front-matter (lines 1-11) and plain-text rules - Forking creates a personal copy for customization without affecting the upstream repository - Edit metadata to change tags, descriptions, and categorization in the YAML block - Modify or append rules after the front-matter to alter conversational behavior declaratively - Push changes to your fork and point your skill loader to your repository URL to activate customizations ## Frequently Asked Questions ### Do I need to know how to code to customize the i-have-adhd skill? No. The skill is purely data-driven. You only need to edit YAML front-matter and plain-text rules in [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md)—no programming knowledge is required because the runtime interprets the file declaratively. ### Where exactly is the SKILL.md file located in the repository? The file is located at [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) in the repository root. According to the repository structure, the skill loader specifically looks for [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) inside the `skills//` directory path. ### What happens if I modify the tags in the metadata section? Updating the `metadata.hermes.tags` array in the YAML front-matter changes how the skill is categorized and discovered by the runtime system. You can add custom tags like "Weekly-Review" or "Personalized" to organize your workflow, and these tags affect how the skill is indexed and related to other skills. ### Can I add new rules without breaking existing functionality? Yes. The runtime reads the rules section verbatim and applies them sequentially when processing the `/i-have-adhd` command. Adding new rules after existing ones extends the behavior safely, as long as you maintain the plain-text format and do not disrupt the YAML front-matter block that ends at line 11.