hackernews-frontpage

Scrape the Hacker News front page (titles, points, comment counts).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The body is well-organized and appropriately brief for a simple read-only skill, with a clear run command and output contract. It loses points for prose-described internals, a tangential "reference skill" section, and the absence of in-workflow validation checkpoints.

Suggestions

Trim or repurpose the 'Why this is the reference skill' section; keep only what helps Claude execute the skill.

Show the executable parsing code (or clearly link the bundled script) instead of describing the tr.athing parse in prose.

Add an explicit validation step before emitting JSON, e.g. verify the parsed story count is 30 and that rank/title/url/points/comments are non-empty.

Dimension	Reasoning	Score
Conciseness	The body is brief and does not explain concepts Claude already knows, but the "Why this is the reference skill" section is meta-commentary about the skill's role in a broader system that does not serve execution and could be tightened, placing it at level 2 rather than the fully lean level 3.	2 / 3
Actionability	It provides a concrete copy-paste run command (`$B skill run hackernews-frontpage`) with expected JSON output and selector detail (`tr.athing`), but describes the scraping mechanism in prose rather than showing executable parsing code, and references a bundled `script.test.ts` that is not present here.	2 / 3
Workflow Clarity	The four-step "How it works" sequence is clearly ordered, but there are no explicit validation checkpoints; the test-fixture feedback loop is mentioned separately rather than as an in-workflow step, so it stops at level 2.	2 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references (none of references/, scripts/, assets/ exist), and is organized into clear sections (Usage, How it works, Why this is the reference skill), meeting the simple-skill bar for level 3.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 concise and specific with a clear, conflict-free niche, but it omits an explicit "Use when..." trigger clause and common term variations such as "HN" or "top stories", capping completeness and trigger quality at level 2.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants the current Hacker News front page or top stories.'

Include common trigger variations like 'HN' and 'top stories' alongside 'Hacker News front page' for broader natural-term coverage.

Dimension	Reasoning	Score
Specificity	"Scrape the Hacker News front page (titles, points, comment counts)" names a concrete action and domain with specific output fields, but lists a single scrape action rather than multiple distinct actions, matching the level-2 anchor rather than level 3.	2 / 3
Completeness	It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	It uses natural terms a user would say ("Scrape the Hacker News front page") plus field names, but omits common variations like "HN" or "top stories", so it sits at level 2 rather than the broad coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	"Hacker News front page" scraping is a clear, narrow niche with distinct triggers and is unlikely to overlap with other skills, matching the level-3 anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: garrytan/gstack
Commit: 11de390

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.