url-dump

Quick capture URLs with automatic content extraction, insights, and categorization into knowledge booklets

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

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

The body is a thorough, well-sequenced instruction skill whose standout is the Loop Engineering section giving genuine validation and retry feedback loops. Its weaknesses are token-heavy aspirational sections and a monolithic structure with no reference files for its large templates.

Suggestions

Move the large bookmark, tool, and category-index templates into reference files and link to them from SKILL.md to improve progressive disclosure and token efficiency.

Cut or demote 'Learning and Adaptation' and 'Success Metrics' — they describe goals rather than executable steps.

Specify the fetch/extraction mechanism (e.g. an actual fetch tool or reader-mode command) instead of abstract directives like 'Fetch the web page content'.

Dimension	Reasoning	Score
Conciseness	Core templates, paths, and prompts earn their tokens, but sections like 'Learning and Adaptation' and 'Success Metrics' describe aspirational capabilities rather than instruct, and the ~450-line body could be tightened.	2 / 3
Actionability	Templates, file paths, and prompts are concrete and reusable, but the skill's hardest technical step — fetching and extracting page content — is described abstractly ('Fetch the web page content', 'Detect duplicate URLs') with no executable tool or command.	2 / 3
Workflow Clarity	A clearly numbered 8-step sequence is paired with explicit verification protocols and a well-engineered fetch-retry loop with layered termination conditions, quality gate, retry cap, and human escalation — exactly the validate/fix/retry pattern the rubric rewards.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a monolithic ~450-line document with several large templates inline that could be split into one-level-deep reference files; headers organize it but no reference split is signaled.	2 / 3
	Total	9 / 12 Passed

Description

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 conveys a clear purpose and niche but is missing an explicit trigger/when clause and natural trigger variations, leaving it at mid-range on completeness and trigger quality. Tightening specificity and adding user-facing trigger terms would lift it.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g. 'Use when the user shares a URL, or says save this link, bookmark this, or url dump'.

Replace the abstract 'insights' with concrete actions to raise specificity, e.g. 'summarize content, extract key insights, and tag entries'.

Fold in natural trigger variations (bookmark, save for later, link) that the body already documents.

Dimension	Reasoning	Score
Specificity	The description names the URL-capture domain and several actions ("content extraction", "insights", "categorization into knowledge booklets"), but "insights" is abstract rather than a crisply concrete action, so it stops short of the multi-action score-3 anchor.	2 / 3
Completeness	It clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"Quick capture URLs" is a natural phrase, but the description omits the common variations ("save this link", "bookmark this", "save for later", "url dump") that the skill itself lists in its body, missing common user phrasings.	2 / 3
Distinctiveness Conflict Risk	"Categorization into knowledge booklets" gives it a recognizable niche, but "automatic content extraction, insights" overlaps with general summarization/knowledge skills, leaving some conflict risk.	2 / 3
	Total	8 / 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: huytieu/COG-second-brain
Commit: 5e9851c

Reviewed: 14 days 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.