agent-scout-explorer

Agent skill for scout-explorer - invoke with $agent-scout-explorer

5.41x

Quality

Does it follow best practices?

Impact

92%

5.41x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-scout-explorer/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when to use it, or what domain it operates in. It reads as a placeholder rather than a functional description that would help Claude select the right skill.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Explores and scouts codebases to map file structures, identify dependencies, and summarize module purposes').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user asks to explore a codebase, understand project structure, or find specific files').

Remove the invocation syntax ('invoke with $agent-scout-explorer') from the description field, as this is operational detail that doesn't help with skill selection and should be documented elsewhere.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for scout-explorer' is entirely vague and abstract, giving no indication of what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and how to invoke it, with no explanation of purpose or trigger conditions.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'scout-explorer' is an internal tool name, not a term users would naturally use in requests. The invocation syntax '$agent-scout-explorer' is technical jargon.	1 / 3
Distinctiveness Conflict Risk	The description is so generic ('agent skill') that it provides no distinguishing characteristics. Without knowing what it does, it could conflict with any other skill, and Claude would have no basis for selecting it appropriately.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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

This skill is heavily padded with repetitive JSON memory-store templates that all follow the same pattern, making it extremely token-inefficient. It lacks actual exploration instructions—it tells the scout how to report findings but never explains how to actually discover them (no file system commands, no analysis tools, no concrete investigation steps). The abstract strategy sections and integration points add little actionable value.

Suggestions

Replace the 6+ nearly identical memory store examples with a single generic template and a concise table listing the different key patterns, categories, and required fields for each discovery type.

Add concrete, executable steps for how to actually perform reconnaissance—e.g., specific shell commands to map directory structures, tools to check dependencies, grep patterns to find vulnerabilities.

Define a clear end-to-end workflow: receive mission → explore using specific tools → validate findings → store to memory → report completion, with explicit checkpoints.

Extract the JSON schema definitions into a separate reference file and keep SKILL.md as a concise overview with one example and links to detailed schemas.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with repetitive JSON templates that all follow the same pattern (memory store calls). The skill could be reduced to a single template with a table of key/value schemas. Many sections (Environmental Scanning, Performance Metrics, Opportunity Identification) are near-duplicates structurally. The 'Integration Points' and 'Scouting Strategies' sections are abstract filler that don't add actionable value.	1 / 3
Actionability	The memory store call patterns are concrete and show specific JSON schemas, which is useful. However, the code blocks are illustrative templates with placeholder values (e.g., 'scout-[ID]', 'dep1', 'dep2') rather than truly executable examples. The scouting strategies section is entirely abstract with no concrete commands for how to actually explore a codebase, analyze dependencies, or detect threats.	2 / 3
Workflow Clarity	There is no clear end-to-end workflow with sequenced steps and validation checkpoints. The skill presents isolated memory store operations without showing how a scout actually performs reconnaissance (what tools to use, what commands to run, how to analyze results). The 'Scouting Strategies' lists are vague numbered steps like 'Survey entire landscape quickly' with no concrete actions. No validation or error recovery is mentioned.	1 / 3
Progressive Disclosure	The content is a monolithic wall of repetitive JSON templates with no references to external files and no layered structure. All the detailed schemas are inline when they could be in a reference file. No bundle files exist to support progressive disclosure, and the content doesn't organize itself into overview vs. detail levels.	1 / 3
	Total	5 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 9d4a9ea

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