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 provides virtually no useful information for skill selection. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It is essentially unusable for Claude to make informed skill-selection decisions.

Suggestions

Add concrete actions describing what scout-explorer actually does (e.g., 'Explores directory structures, searches for files by pattern, and maps project layouts').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to explore a codebase, find files, navigate project structure, or search directories').

Replace the invocation instruction with functional description—Claude needs to know what the skill does and when to use it, not just how to invoke it.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for scout-explorer' is entirely vague and does not describe 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 the invocation method, providing no functional or contextual information.	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 vague that it's impossible to distinguish it from any other skill. Without knowing what it does, it could conflict with anything or nothing—Claude has no basis for selection.	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 excessively verbose, repeating the same memory storage pattern across 8+ nearly identical JSON blocks that differ only in their payload fields. It lacks a concrete, sequenced workflow for how to actually perform reconnaissance (what tools to use, what commands to run, how to verify findings). The scouting strategies are abstract numbered lists without actionable specifics, and the entire content could be condensed to roughly 30% of its current size.

Suggestions

Consolidate all memory storage examples into a single generic template plus a table/list of key schemas (key pattern, required fields, example values) instead of repeating the full mcp call 8+ times.

Add a concrete end-to-end workflow with numbered steps showing how to actually perform exploration (e.g., specific file system commands, search patterns, tool invocations) with validation checkpoints before storing findings.

Move detailed JSON schemas for each discovery type into a separate reference file and keep only a quick-start overview in the main skill body.

Replace the abstract scouting strategy lists (breadth-first, depth-first, continuous patrol) with concrete, actionable instructions or remove them entirely since they describe general concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with repetitive JSON templates that all follow the same pattern (store to memory with slightly different payloads). The skill could be reduced to a single template with a table of key/value schemas. Many sections (Environmental Scanning, Performance Metrics, Scouting Strategies) add bulk without unique actionable value.	1 / 3
Actionability	The JSON memory store calls provide concrete structure, but they are templates with placeholder values rather than truly executable code. The exploration patterns (breadth-first, depth-first, continuous patrol) are vague numbered lists without concrete commands or steps for actually performing reconnaissance.	2 / 3
Workflow Clarity	There is no clear sequential workflow with validation checkpoints. The skill presents a collection of memory storage templates and abstract strategy lists but never defines a concrete end-to-end scouting workflow (e.g., what to do first, how to verify findings before storing, when to stop). The 'verify findings before alerting' instruction in Quality Standards is mentioned but never operationalized.	1 / 3
Progressive Disclosure	The content is a monolithic wall of repetitive JSON blocks with no references to external files and no layered structure. All detail is inline regardless of importance, making it hard to navigate. The content would benefit greatly from a concise overview with references to detailed schemas or pattern files.	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/ruflo
Commit: 0f7c750

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