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 it should be used, or what domain it operates in. It reads as a placeholder rather than a functional description that could help Claude select the right skill.

Suggestions

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

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, find files, or understand project structure').

Replace the generic 'Agent skill for scout-explorer' framing with a domain-specific description that distinguishes this skill from others.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for scout-explorer' is entirely vague and abstract, providing no information about 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 only actionable content is the invocation command.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it provides no distinguishing characteristics. Without knowing what the skill does, it's impossible to differentiate it from any other agent skill.	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 seven times with minor variations in payload structure. It lacks concrete, executable exploration steps—describing what to report but not how to actually perform reconnaissance. The abstract scouting strategies and generic do/don't lists add little value for Claude, and the entire document could be condensed to roughly 30% of its current size with better organization.

Suggestions

Consolidate the repetitive MCP memory_usage templates into a single generic template with a table or list describing the different key patterns and payload schemas for each scout type.

Add concrete, executable exploration steps—specify which tools to use (e.g., file listing, grep, dependency audit commands) rather than abstract instructions like 'Survey entire landscape quickly'.

Add validation checkpoints: after storing discoveries, verify they were stored correctly; after completing an area, check coverage before moving on.

Move detailed JSON schemas for each scout type into a separate reference file and keep SKILL.md as a concise overview with one representative example.

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, Opportunity Identification) are near-duplicates structurally. The 'Scouting Strategies' section lists generic exploration concepts Claude already knows.	1 / 3
Actionability	The MCP tool call patterns are concrete and show specific key naming conventions and JSON schemas, which is useful. However, the code blocks are illustrative templates rather than executable code—they use placeholder values like '[ID]', '[timestamp]', and generic descriptions. The actual exploration steps (how to scan a codebase, how to detect vulnerabilities) are never specified with real commands or tools.	2 / 3
Workflow Clarity	There is no clear sequential workflow with validation checkpoints. The 'Scouting Strategies' sections list abstract numbered steps like 'Survey entire landscape quickly' and 'Identify high-level patterns' without specifying how. There are no feedback loops, no error recovery steps, and no validation that discoveries are correctly stored or that exploration is complete.	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 for every scout type are inlined, making the document very long. The content would benefit greatly from a concise overview with references to separate schema/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: 398f7c2

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.