CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-edge-cases

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/browser-edge-cases/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable debugging SOP with strong code examples and a clear phased workflow. Its main weakness is progressive disclosure: a large inlined pattern library and two dead reference links.

Suggestions

Fix or remove the broken references: registry.md and ../../tools/BROWSER_USE_PATTERNS.md do not exist in the bundle, so the links 404 for Claude.

Move the 6-pattern Pattern Library into a references file (e.g. references/patterns.md) and keep only a summary table + the most common pattern in SKILL.md to reduce inline bulk.

Replace the placeholder functions in 'robust_operation' (primary_method, cdp_fallback, javascript_fallback, verify_success) with concrete implementations or clearly mark them as a template to fill in.

DimensionReasoningScore

Conciseness

Lean and mostly token-efficient — tables, detection snippets, and the quick reference carry their weight with little conceptual padding. A few inline comments and the 'Pattern: Always…' headers could be trimmed.

4 / 5

Actionability

Provides concrete executable JS detection snippets and Python browser_* calls covering the common cases. The 'robust_operation' example relies on undefined placeholder functions (primary_method, cdp_fallback, verify_success), keeping it just short of copy-paste ready.

4 / 5

Workflow Clarity

Four clearly sequenced phases (Reproduce & Isolate → Analyze Root Cause → Implement Fix → Verify Fix) with a regression check in Phase 4 and try/except fallback loops. Not a destructive/batch operation, so the cap does not apply; minor gaps in explicit error-recovery routing keep it at 4.

4 / 5

Progressive Disclosure

Has clear section structure and a references block, but the 6-pattern library is fully inlined and two of three references are broken (registry.md and ../../tools/BROWSER_USE_PATTERNS.md do not exist; only scripts/test_case.py resolves). Content that could live in separate files is inline and references are not reliably signaled.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that crisply states both purpose and concrete triggers with named sites and DOM patterns. Slightly under-sells the breadth of actions it covers relative to the body's pattern library.

DimensionReasoningScore

Specificity

Names the domain ('debugging browser automation failures on complex websites') with 1-2 concrete actions (debug, fix) and concrete sites, but the action set is not comprehensive — it stops at 'debugging failures' rather than listing distinct operations.

3 / 5

Completeness

Explicitly answers both what ('SOP for debugging browser automation failures on complex websites') and when ('Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('browser tools fail', 'LinkedIn', 'Twitter/X', 'SPAs', 'Shadow DOM'); good coverage with only minor synonyms missing (e.g. 'shadow root', 'infinite scroll').

4 / 5

Distinctiveness Conflict Risk

Clear niche (site-specific edge-case debugging with Shadow DOM/SPA triggers) that is mostly distinct; minor overlap risk with general browser-automation skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository
aden-hive/hive
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.