queen-colony-debug is an open-source workflow skill for Claude Code and compatible agents, published by aden-hive. It packages reusable instructions an agent loads on demand to help with workflow tasks. The project has 11k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/aden-hive/hive ~/.claude/skills/queen-colony-debug`.
browser-edge-cases
browser-edge-cases is an open-source workflow skill for Claude Code and compatible agents, published by aden-hive. Its author describes it as: “SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.”. The project has 11k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/aden-hive/hive ~/.claude/skills/browser-edge-cases`.
What browser-edge-cases does
Standard Operating Procedure for debugging and fixing browser automation failures on complex websites.
Installation
Add browser-edge-cases to your agent with:
git clone https://github.com/aden-hive/hive ~/.claude/skills/browser-edge-cases Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for browser-edge-cases is organised into these sections:
- When to Use This Skill
- SOP: Debugging Browser Tool Failures
- Phase 1: Reproduce & Isolate
- Phase 2: Analyze Root Cause
- Phase 3: Implement Multi-Layer Fix
- Phase 4: Verify Fix
- Pattern Library
- P1: Nested Scrollable Containers
- P2: Element Covered by Overlay
- P3: React Synthetic Events
- P4: Huge DOM / Accessibility Tree
- P5: SPA Hydration Delay
When to use it
Reach for browser-edge-cases when you want workflow help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in aden-hive/hive, an established project with 10,923 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does browser-edge-cases do?
- SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
- How do I install browser-edge-cases?
- Run git clone https://github.com/aden-hive/hive ~/.claude/skills/browser-edge-cases in your agent, then reload your skills. Review the source at https://github.com/aden-hive/hive before installing.
- Is browser-edge-cases free to use?
- Yes. browser-edge-cases is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does browser-edge-cases come from?
- browser-edge-cases ships inside aden-hive/hive, a repository that contains 25 catalogued skills in total. The repository's 10,923 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Workflow →test-reporting is an open-source workflow skill for Claude Code and compatible agents, published by aden-hive. It packages reusable instructions an agent loads on demand to help with workflow tasks. The project has 11k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/aden-hive/hive ~/.claude/skills/test-reporting`.
triage-issue is an open-source workflow skill for Claude Code and compatible agents, published by aden-hive. It packages reusable instructions an agent loads on demand to help with workflow tasks. The project has 11k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/aden-hive/hive ~/.claude/skills/triage-issue`.
Required before any hive-browser CLI command. The browser is driven from the terminal by running `hive-browser <command> ... --json` via terminal_exec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues, not crashes), the screenshot + coordinate workflow (hive-browser interact with a fractional coordinate) that reaches shadow-DOM inputs selectors can't see, the viewport-fraction coordinate rule (not pixels), rich-text editor quirks ("send button stays disabled" failures), and CSP gotchas. Covers Chrome via CDP through the GCU Beeline extension.
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a db_path field.