scout

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with a well-sequenced, validation-aware workflow, but it is a monolithic single-file skill with mild redundancy. Splitting reusable templates into reference files and trimming repetition would improve conciseness and progressive disclosure.

Suggestions

Extract the recurring output templates (Save/Skip blocks, batch summary table) into a references file and link to them, establishing one-level progressive disclosure.

Trim the repeated save/skip framing across Purpose, Boundary, and Process sections to a single canonical statement.

Condense the Quality Signals and Content Type Detection lists, which overlap, into a compact reference table.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no padding of concepts Claude already knows, but ~195 lines with some repeated framing of the save/skip distinction and inline templates makes it longer than necessary for a triage skill.	2 / 3
Actionability	Provides exact vault paths, specific grep/search strategies, explicit fields to extract, WebFetch/WebSearch usage, and copy-paste-ready output templates — fully executable guidance.	3 / 3
Workflow Clarity	A clear 7-step sequence with a pre-flight check, a fallback table for error states, and confidence-tiered branching that supplies validation checkpoints and feedback loops for batch URL processing.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a single monolithic file with no one-level references; sections are well-organized for in-file navigation, but content that could be split out (templates, fallback matrix) stays inline.	2 / 3
	Total	10 / 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 conveys a concrete, distinctive niche but relies on implied triggers and omits a 'Use when...' clause, leaving it readable but not fully self-activating. Adding explicit trigger phrasing would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks to evaluate a URL or tool before saving, or says "should I save this?" / "is this relevant?"'.

Surface the natural trigger phrases already in the body ("scout this", "evaluate this", "should I save this?") into the description itself.

Tighten the broad term 'tools' toward the triage vocabulary (e.g., 'tool/service') to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the URL/tool triage domain with several concrete actions ('check vault coverage, assess relevance, recommend save or skip'), but stops short of the multi-action comprehensiveness of the top anchor.	2 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so the 'when' is only implied — per guidelines this caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('evaluate', 'save or skip', 'relevance') but omits common variations users would actually say ('is this relevant?', 'should I save this?', 'scout this') that appear only in the body.	2 / 3
Distinctiveness Conflict Risk	The vault-coverage and binary save/skip framing carve a clear triage niche that is unlikely to trigger competing skills, despite the broad word 'tools'.	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: 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.