scout

Evaluate URLs and tools — check vault coverage, assess relevance, recommend save or skip

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/scout/SKILL.md

Quality

Content

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 well-structured conceptually with a clear process flow and useful output templates, but it is significantly over-verbose for what it accomplishes. It explains too many concepts Claude already understands (content types, quality signals, relevance matching), includes aspirational sections (philosophy, success metrics) that don't aid execution, and packs everything into a single monolithic file. The actionability is moderate — good templates but lacking concrete tool invocation syntax.

Suggestions

Cut the 'Philosophy', 'Success Metrics', and 'Integration with Other Skills' sections entirely — these don't help Claude execute the skill and waste ~30 lines of context.

Replace the abstract 'Relevance Assessment' section with a concrete scoring template or checklist rather than describing what relevance means.

Add concrete tool invocation examples for vault search (e.g., specific grep commands or search patterns) and web-fetch/web-search calls instead of describing them abstractly.

Extract the fallback table, content type taxonomy, and output templates into a referenced bundle file to reduce the main SKILL.md to a lean overview.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~180 lines. Includes extensive philosophical sections, success metrics, integration notes, and explanations of concepts Claude can infer (e.g., what content types are, what 'quality signals' mean). The 'Philosophy' section, 'Success Metrics', and much of the 'Relevance Assessment' detail add little actionable value. The fallback table and uncertainty handling could be condensed significantly.	1 / 3
Actionability	Provides a clear process flow with specific output templates (emoji-tagged recommendations, markdown tables), which is good. However, there is no executable code, no concrete grep/search commands for vault scanning, and the web-fetch/web-search usage is described abstractly rather than with specific tool invocation syntax. The guidance is structured but not copy-paste ready.	2 / 3
Workflow Clarity	The 7-step process flow is clearly sequenced and covers the main workflow well. However, there are no explicit validation checkpoints — no step to verify that vault search was comprehensive, no confirmation that content fetch succeeded before proceeding to analysis, and no error recovery loops. The fallback table partially addresses failure modes but doesn't integrate into the workflow as validation steps.	2 / 3
Progressive Disclosure	All content is monolithically inlined in a single file with no bundle files. The relevance assessment criteria, fallback behaviors, content type detection taxonomy, and output templates could all be split into referenced files. At ~180 lines, this is a wall of text that would benefit significantly from progressive disclosure to separate files.	1 / 3
	Total	6 / 12 Passed

Description

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 provides a partial picture of what the skill does — evaluating URLs against some kind of vault and recommending actions — but lacks clarity on the domain context (what vault system?) and has no explicit trigger guidance. The terminology is a mix of somewhat specific actions and domain jargon that may not match natural user language.

Suggestions

Add an explicit 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to evaluate whether a URL should be saved to their vault or skipped.'

Clarify what 'vault' refers to (e.g., knowledge base, bookmark collection, Obsidian vault) so Claude can distinguish this skill from other URL-related skills.

Include natural trigger terms users might say, such as 'links', 'bookmarks', 'should I save this', 'URL triage', or 'web page relevance'.

Dimension	Reasoning	Score
Specificity	Names some actions ('check vault coverage', 'assess relevance', 'recommend save or skip') but the domain is unclear — what kind of vault? What URLs? The actions are somewhat concrete but lack full context about what the skill actually does.	2 / 3
Completeness	Describes what it does (evaluate URLs, check vault coverage, recommend save/skip) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also somewhat unclear, bringing this to 1.	1 / 3
Trigger Term Quality	Includes 'URLs', 'vault coverage', 'save or skip' which are somewhat relevant, but 'vault' is domain-specific jargon that users may not naturally say. Missing common variations like 'links', 'bookmarks', 'web pages', or clearer context about what system this relates to.	2 / 3
Distinctiveness Conflict Risk	The combination of 'vault coverage' and 'save or skip' recommendations is somewhat distinctive, but 'evaluate URLs' and 'assess relevance' are generic enough to overlap with other URL-processing or web-scraping skills. The vault concept adds some niche specificity but isn't well-defined.	2 / 3
	Total	7 / 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: about 1 month 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.