url-dump

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

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/url-dump/SKILL.md

Quality

Discovery

32%

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 general sense of the skill's purpose—capturing URLs and organizing extracted content—but lacks explicit trigger guidance ('Use when...') and misses common user-facing terms like 'bookmark', 'save link', or 'web page'. The term 'knowledge booklets' is distinctive but may not match how users naturally describe their needs.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to save, bookmark, or capture a URL, web page, or article for later reference.'

Include natural trigger terms users would say, such as 'bookmark', 'save link', 'web page', 'article', 'reading list', or 'clip'.

Clarify what 'insights' and 'knowledge booklets' mean concretely—e.g., 'generates summaries and key takeaways, organizing them into themed collections'.

Dimension	Reasoning	Score
Specificity	Names several actions (capture URLs, content extraction, insights, categorization) and mentions a specific output format (knowledge booklets), but the terms 'insights' and 'quick capture' are somewhat vague and don't describe concrete operations in detail.	2 / 3
Completeness	Describes what the skill does (capture URLs, extract content, categorize into booklets) 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 'what' is also only moderately clear, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'URLs', 'content extraction', 'categorization', and 'booklets', but misses common user terms like 'bookmark', 'save link', 'web page', 'article', or 'reading list' that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	The combination of URL capture and 'knowledge booklets' is somewhat distinctive, but 'content extraction' and 'categorization' are generic enough to overlap with web scraping, note-taking, or general knowledge management skills.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill is significantly over-engineered and verbose for what is essentially a URL bookmarking workflow. It contains extensive template boilerplate inline, explains concepts Claude already understands (YAML syntax, confidence percentages, content categories), and includes aspirational sections (Learning and Adaptation, Success Metrics) that describe system behavior Claude cannot actually implement in a single interaction. The core workflow is reasonably clear but lacks concrete implementation for the most critical step—actually fetching and extracting URL content.

Suggestions

Reduce content by 60-70%: move templates to separate bundle files (e.g., templates/bookmark.md, templates/tool.md, templates/index.md), remove YAML formatting basics, and cut the Success Metrics and Learning and Adaptation sections entirely.

Add concrete guidance for URL content extraction—specify which tools/approaches to use (e.g., fetch tool, browser tool) rather than just listing what fields to extract.

Remove explanations of what categories mean (e.g., 'Articles & Blogs: Long-form content, tutorials, opinion pieces')—Claude can infer category semantics from names alone.

Consolidate the four-phase content analysis into a single concise checklist rather than spreading it across labeled phases with redundant structure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Includes extensive template boilerplate, explains obvious concepts (what categories mean, what confidence percentages represent), and has sections like 'Success Metrics' and 'Learning and Adaptation' that describe aspirational system behavior Claude cannot actually implement. The YAML formatting section explains basic YAML syntax Claude already knows.	1 / 3
Actionability	Provides concrete file templates and folder structures which are useful, but much of the 'process' is descriptive rather than executable—there are no actual commands or code for fetching URLs, extracting content, or detecting duplicates. The phases describe what to do conceptually but lack implementation details for the extraction pipeline.	2 / 3
Workflow Clarity	The 8-step process flow is clearly sequenced and includes a pre-flight check and confirmation step. However, validation is mostly described as checklists to mentally verify rather than concrete validation commands. The verification protocols section lists checks but doesn't provide actionable steps for error recovery or feedback loops when extraction fails.	2 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files to offload content to. The full bookmark template, tool template, category index template, booklet folder structure, YAML formatting guide, verification protocols, and uncertainty handling are all inline. These could easily be split into separate reference files, but no bundle exists and no references are made to external files.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: huytieu/COG-second-brain
Commit: 034af4c

Reviewed: 18 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.