Browser-automated file download with enhanced features. Auto-detects platform (Windows/macOS/Linux, 64/32-bit, ARM/Intel), handles multi-step navigation (homepage to platform-specific pages), captures auto-downloads triggered on page load, and falls back to button clicking when needed. Ideal for complex download flows where curl/wget fail due to client-side rendering, automatic downloads, or multi-page navigation. Features page scrolling for lazy content, extended wait times, and Golang support.
78
Quality
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/aaronxx/browser-auto-download/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at specificity and distinctiveness, clearly articulating what the skill does with concrete technical capabilities. However, it lacks an explicit 'Use when...' clause and relies on somewhat technical jargon rather than natural user language, which could hinder skill selection in a large skill library.
Suggestions
Add an explicit 'Use when...' clause with natural trigger phrases like 'download file from website', 'get installer', 'fetch release binary', or 'download when curl doesn't work'
Include more natural user terms alongside technical ones - e.g., 'download software', 'get latest release', 'fetch from GitHub releases' rather than focusing on 'client-side rendering' and 'lazy content'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Auto-detects platform', 'handles multi-step navigation', 'captures auto-downloads', 'falls back to button clicking', 'page scrolling for lazy content'. Very detailed about capabilities. | 3 / 3 |
Completeness | Strong on 'what' with detailed capabilities, but lacks explicit 'Use when...' clause. The phrase 'Ideal for complex download flows where curl/wget fail' partially addresses when, but doesn't provide explicit trigger guidance for skill selection. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'download', 'curl/wget', 'browser', but missing common user phrases like 'download file', 'get installer', 'fetch binary'. Technical terms like 'client-side rendering' and 'lazy content' are jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing on browser-automated downloads with specific differentiators (platform detection, multi-step navigation, auto-downloads). Distinct from simple download tools or general browser automation skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and excellent executable examples. The main weakness is moderate verbosity - some sections repeat information and the document could be 20-30% shorter without losing clarity. The progressive disclosure is adequate but the document is on the longer side for a single file.
Suggestions
Consolidate the 'Examples' and 'Real-World Examples' sections to eliminate redundancy
Consider moving the detailed troubleshooting and advanced usage sections to separate reference files, keeping only quick tips inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the three-stage strategy is explained both in prose and ASCII diagrams, and some sections like 'Real-World Examples' repeat information already covered. The platform detection table and troubleshooting sections add value but could be tighter. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples, specific CLI commands with real flags, Python module usage, and copy-paste ready snippets. The examples cover multiple use cases with concrete URLs and expected outputs. | 3 / 3 |
Workflow Clarity | Clear three-stage workflow with explicit sequencing (auto-download → navigation → button clicking). The ASCII flow diagrams make the decision logic explicit, and troubleshooting provides clear feedback loops for when things fail. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's somewhat monolithic - the advanced usage, real-world examples, and troubleshooting could potentially be split into separate files. However, the inline organization with headers is reasonable for this length. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
45f9fac
Table of Contents
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.