Emc
aklofas/kicad-happy
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…
Identify and design for edge cases that disproportionately affect users with disabilities.
Install Edge Case Identification
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .claude/skills/edge-case-identification && rm -rf skills-srcUse ~/.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/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .claude/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .agents/skills/edge-case-identification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .agents/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .cursor/skills/edge-case-identification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .cursor/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path inclusive-personas/skills/edge-case-identification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .gemini/skills/edge-case-identification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .gemini/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .github/skills/edge-case-identification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .github/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills edge-case-identification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/inclusive-personas/skills/edge-case-identification .opencode/skills/edge-case-identification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "edge-case-identification" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/edge-case-identification into .opencode/skills/edge-case-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edge-case-identification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
edge-case-identification- GitHub stars
- 104
- Token cost
- ~1k tokens
- SKILL.md length
- 557 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identify and design for edge cases that disproportionately affect users with disabilities.
- Works in 4 steps: How many users does this affect? (often… → How severe is the impact? (a blocked… → Is this a permanent condition for some… → …
- Reviewing designs for completeness
- SKILL.md covers Core Principle, Categories of Overlooked Edge…, How to Find Edge Cases and Response to "That's an Edge…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Edge Case Identification is an agent skill from Owl-Listener/inclusive-design-skills. Identify and design for edge cases that disproportionately affect users with disabilities. Use when reviewing designs for completeness, planning test cases, or when someone says 'that's an edge case.' Triggers on: edge case, corner case, that's unlikely, only a few users, exception, unusual scenario, we'll handle that later, happy path, unhappy path, error state, empty state.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test generation. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Reviewing designs for completeness
- Planning test cases
- Someone says thats an edge case. Triggers on: edge case
- Only a few users
Example prompts
- “s an edge case.”
- “s unlikely, only a few users, exception, unusual scenario, we”
- “/edge-case-identification”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- How many users does this affect? (often more than assumed)
- How severe is the impact? (a blocked user is worse than a
- Is this a permanent condition for some users? (then it's their
- Would fixing this improve the experience for other users too?
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. 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
Edge Case Identification loads about 1k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 557 words of instructions outside code blocks.
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 Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 557 words, ~1,003 tokens.
Download SKILL.mdSave it as
.claude/skills/edge-case-identification/SKILL.md (or your agent's skills folder).- name
- edge-case-identification
- description
- Identify and design for edge cases that disproportionately affect users with disabilities. Use when reviewing designs for completeness, planning test cases, or when someone says 'that's an edge case.' Triggers on: edge case, corner case, that's unlikely, only a few users, exception, unusual scenario, we'll handle that later, happy path, unhappy path, error state, empty state.
Edge Case Identification
Identify the scenarios that teams dismiss as "edge cases" but that are everyday reality for users with disabilities. An edge case for the team is often a primary case for someone.
Core Principle
"That's an edge case" is the most common way accessibility gets deprioritised. If it affects people with disabilities, it's not an edge case — it's a design requirement you haven't met.
Categories of Overlooked Edge Cases
Input Edge Cases
- User cannot use a mouse (keyboard only)
- User cannot use a keyboard (voice or switch only)
- User cannot use both hands (one-handed operation)
- User pastes content instead of typing it
- User uses autocomplete or password manager to fill fields
- User enters content in a different script or language
- User inputs using dictation with punctuation spoken aloud
Output Edge Cases
- User cannot see the screen (screen reader)
- User sees only a small portion of the screen (magnification)
- User cannot distinguish colours
- User cannot hear audio
- User has screen in greyscale mode or high contrast mode
- User has text scaled to 200%
- User has animations disabled
Content Edge Cases
- Extremely long names (hyphenated, multi-word, cultural naming)
- Non-Latin characters in name or address fields
- Empty states where no data exists yet
- Error states when everything goes wrong at once
- First-time use with no prior context
- Returning after months away with forgotten context
- Content in the wrong language for the user
Context Edge Cases
- Session timeout during a long form
- Connection lost mid-task
- Battery dying during a critical flow
- Screen rotation mid-interaction
- System font size set to maximum
- Browser zoom at 200% or higher
- Ad blocker or privacy extension modifying the page
Timing Edge Cases
- User is much slower than expected (switch user, cognitive delay)
- User is much faster than expected (screen reader power user)
- User needs to pause mid-task for hours or days
- Timed session expires before user finishes
- Content updates while user is reading it
How to Find Edge Cases
Show full SKILL.md (235 more words)Show less
The "What If" Exercise
For each step in a flow, ask:
- What if the user can't see this?
- What if the user can't click this?
- What if the user can't understand this?
- What if the user takes 10x longer than expected?
- What if the user leaves and comes back tomorrow?
- What if this field contains unexpected content?
The Inversion Test
Take your happy path scenario. Invert each assumption:
- "User is on a desktop" → mobile, or tablet, or screen reader
- "User has fast internet" → slow, intermittent, or offline
- "User reads English fluently" → low literacy or second language
- "User can see the colour change" → colour blind or blind
- "User completes this in one sitting" → interrupted, returns later
Response to "That's an Edge Case"
When someone says this, ask:
- How many users does this affect? (often more than assumed)
- How severe is the impact? (a blocked user is worse than a mildly inconvenienced one)
- Is this a permanent condition for some users? (then it's their daily experience, not an edge case)
- Would fixing this improve the experience for other users too? (almost always yes)
Assessment Questions
- Has the team mapped edge cases beyond the happy path?
- Have input, output, content, context, and timing edge cases been considered?
- Are there dismissed "edge cases" that are daily reality for users with disabilities?
- Does the test plan include scenarios for assistive technology users?
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in inclusive-personas/skills/edge-case-identification of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Edge Case Identification 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Edge Case Identification this skillOwl-Listener/inclusive-design-skills | 104 | — | ~1k | Automated safety check: Pass | MIT | |
| Emcaklofas/kicad-happy | 1.4k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Generate Test Cases342164796/generate-test-cases | 119 | 1 repos | ~2.9k | Automated safety check: Pass | None | |
| Wioworkersio/skills | 200 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Verify Cc Safety Netkenryu42/cc-safety-net | 1.6k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Generate Test Cases
342164796/generate-test-cases
自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
Verify Cc Safety Net
kenryu42/cc-safety-net
Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.
- Official
File Server
microsoft/WindowsProtocolTestSuites
ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Related
Categories
Questions about Edge Case Identification
What does Edge Case Identification do?
Identify and design for edge cases that disproportionately affect users with disabilities. Edge Case Identification is an agent skill from Owl-Listener/inclusive-design-skills. Identify and design for edge cases that disproportionately affect users with disabilities.
When should I use Edge Case Identification?
Edge Case Identification fits situations like: reviewing designs for completeness; planning test cases; someone says thats an edge case. Triggers on: edge case; only a few users.
How do I install Edge Case Identification in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a claude-code`. Or copy the skill folder (inclusive-personas/skills/edge-case-identification in Owl-Listener/inclusive-design-skills) into .claude/skills/edge-case-identification in your project. Claude Code loads it when a task matches its description.
How do I install Edge Case Identification in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill edge-case-identification -a codex`. Or copy the skill folder (inclusive-personas/skills/edge-case-identification in Owl-Listener/inclusive-design-skills) into .agents/skills/edge-case-identification in your project. Codex loads it when a task matches its description.
Can I use Edge Case Identification 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 Owl-Listener/inclusive-design-skills --skill edge-case-identification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/edge-case-identification, .gemini/skills/edge-case-identification, .github/skills/edge-case-identification and .opencode/skills/edge-case-identification in your project.
What does Edge Case Identification need to run?
SKILL.md names no scripts, command-line tools or credentials: Edge Case Identification is instructions for the agent only.
Does Edge Case Identification 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 Edge Case Identification 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 Edge Case Identification use?
Edge Case Identification 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 Edge Case Identification use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Edge Case Identification?
Skills that share tags, products or a category with Edge Case Identification: Emc (aklofas/kicad-happy, 1.4k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 119 stars) and Wio (workersio/skills, 200 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Edge Case Identification?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 104 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.