hackernews-frontpage
Scrape the Hacker News front page (titles, points, comment counts).
47
35%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./browser-skills/hackernews-frontpage/SKILL.mdQuality
Discovery
50%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 is specific about what it does—scraping particular data fields from Hacker News—and occupies a clear niche. However, it completely lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. It also misses common trigger term variations like 'HN', 'news.ycombinator.com', or 'top stories'.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about Hacker News stories, trending tech news, or wants to fetch data from news.ycombinator.com.'
Include common trigger term variations such as 'HN', 'news.ycombinator.com', 'top stories', 'trending posts', and 'web scraping' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete data points to extract: titles, points, and comment counts from a specific source (Hacker News front page). These are clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what it does (scrape HN front page data) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Hacker News' and 'scrape' as natural keywords, but misses common variations like 'HN', 'news.ycombinator.com', 'top stories', 'trending', or 'web scraping'. Users might ask about HN without saying 'scrape'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Hacker News specifically, with distinct data extraction targets. Unlikely to conflict with other skills unless there are multiple HN-related skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a README or design document than an actionable skill for Claude. It lacks any executable code, concrete selectors, or parsing logic needed to actually scrape Hacker News. The 'Why this is the reference skill' section wastes tokens on meta-commentary about project architecture that is irrelevant to performing the task.
Suggestions
Add executable code showing the actual scraping implementation: HTML fetching, CSS selectors (e.g., `tr.athing`, `.score`, `.subtext`), and JSON output construction.
Remove the 'Why this is the reference skill' section entirely — it's project meta-commentary that doesn't help Claude perform the scraping task.
Replace the abstract 'How it works' steps with concrete, actionable instructions including the specific selectors and parsing logic needed.
Add error handling guidance for common failure modes (e.g., selector changes, network errors, missing fields in story rows).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content spends significant tokens explaining 'why this is the reference skill,' Phase 1 components, SDK details, and design rationale that Claude doesn't need to perform the scraping task. The 'How it works' section describes rather than instructs, and the 'Why this is the reference skill' section is entirely unnecessary for task execution. | 1 / 3 |
Actionability | There is no executable code, no concrete scraping logic, no selectors, no parsing code, and no actual implementation. The skill describes what happens at a high level ('Reads the page HTML', 'Parses each story row') but provides zero copy-paste-ready code or commands that Claude could use to actually scrape Hacker News. | 1 / 3 |
Workflow Clarity | The 'How it works' section provides a numbered sequence of steps, but they are abstract descriptions rather than actionable instructions. There are no validation checkpoints, no error handling guidance, and no feedback loops for when selectors break or the page structure changes. | 2 / 3 |
Progressive Disclosure | The content references `script.test.ts` and a bundle structure but no bundle files are provided. The sections are organized but the 'Why this is the reference skill' section is misplaced meta-commentary. References to external files like test fixtures are mentioned but not clearly linked or navigable. | 2 / 3 |
Total | 6 / 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 | |
- Repository
- garrytan/gstack
- Commit
db9447c
- 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.