doc-scanner

Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance. Auto-activates when user asks to review, understand, or explore a codebase, when starting work in a new project, when asking about conventions or agents, or when documentation context would help. Can consolidate multiple platform docs into unified AGENTS.md.

2.00x

Quality

82%

Does it follow best practices?

Impact

98%

2.00x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

64%

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

This is a well-structured, concise skill that clearly defines when to activate and follows a logical multi-step workflow. Its main weaknesses are the lack of executable tool invocations (relying on descriptive instructions rather than concrete commands/code) and missing validation steps for the destructive consolidation operation. The referenced bundle files don't exist, which undermines the progressive disclosure strategy.

Suggestions

Add explicit validation/confirmation steps before archiving original documentation files in Step 4 (e.g., 'Show the user the consolidated output and get confirmation before archiving originals').

Include concrete, executable glob patterns or tool invocations (e.g., actual Glob tool call syntax) rather than just listing filenames.

Provide the referenced bundle files (references/file-patterns.md and references/templates.md) or remove the references if they don't exist.

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured. It doesn't explain what documentation files are or why scanning matters—it jumps straight into actionable steps. Every section earns its place.	3 / 3
Actionability	The skill provides a clear process outline and specific file names to scan, but lacks executable code or concrete tool invocations (e.g., actual glob patterns, shell commands, or code snippets). The synthesis output template is a useful skeleton but is more of a format guide than executable guidance.	2 / 3
Workflow Clarity	Steps are clearly sequenced and logically ordered, but the consolidation step (Step 4) involves destructive operations (archiving/moving original files) without any validation or confirmation checkpoint. There's no feedback loop for verifying the consolidated AGENTS.md is correct before removing originals.	2 / 3
Progressive Disclosure	References to `./references/file-patterns.md` and `./references/templates.md` are well-signaled and one level deep, which is good. However, no bundle files are provided, meaning these references point to non-existent files, undermining the progressive disclosure structure. The main content is appropriately scoped but the missing supporting files weaken this dimension.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 a strong skill description that clearly articulates specific capabilities (scanning for named documentation files, synthesizing guidance, consolidating into AGENTS.md), provides explicit trigger conditions via an 'Auto-activates when...' clause, and occupies a distinct niche around AI agent documentation files. The description is well-structured, uses third person voice, and includes natural trigger terms users would employ.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: scans for documentation files, synthesizes guidance, consolidates multiple platform docs into unified AGENTS.md. Also enumerates specific file formats (AGENTS.md, CLAUDE.md, GEMINI.md, etc.).	3 / 3
Completeness	Clearly answers both 'what' (scans for project documentation files and synthesizes guidance, consolidates into unified AGENTS.md) and 'when' (auto-activates when user asks to review/understand/explore a codebase, starting work in a new project, asking about conventions or agents, or when documentation context would help).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'review', 'understand', 'explore a codebase', 'new project', 'conventions', 'agents', 'documentation'. Also lists specific file names (AGENTS.md, CLAUDE.md, CURSOR.md, etc.) that users might reference.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche focused specifically on AI agent documentation files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) and their consolidation. The specific file formats and the consolidation use case make it clearly distinguishable from general documentation or code review skills.	3 / 3
	Total	12 / 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: NeverSight/skills_feed
Commit: 9f1a8a8

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