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.
90
86%
Does it follow best practices?
Impact
98%
2.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
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 an excellent skill description that clearly articulates specific capabilities (scanning, synthesizing, consolidating documentation files), provides explicit trigger conditions via an 'Auto-activates when...' clause, and occupies a distinct niche around AI agent documentation files. The description is comprehensive yet concise, with strong natural trigger terms and minimal risk of conflicting with other skills.
| 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' (explicit auto-activation triggers: reviewing codebases, starting new projects, asking about conventions, when documentation context would help). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'review a codebase', 'explore a codebase', 'new project', 'conventions', 'agents', 'documentation'. Also mentions specific file names (AGENTS.md, CLAUDE.md, CURSOR.md, etc.) that users might reference directly. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on AI agent documentation files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) and their synthesis. The specific file formats and consolidation use case make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 communicates its purpose and workflow. Its main weaknesses are the lack of executable commands/code (particularly for the glob scanning and file archiving steps) and the absence of validation checkpoints before the destructive consolidation operation. The progressive disclosure and token efficiency are strong.
Suggestions
Add executable glob patterns or tool invocation examples (e.g., the exact Glob tool call syntax) instead of listing filenames as plain text.
Add a validation/confirmation checkpoint before Step 4's destructive archiving operation — e.g., 'Present the consolidation plan to the user and wait for confirmation before moving any files.'
Provide a concrete example of a synthesized output with realistic content rather than just placeholder brackets, so Claude knows the expected level of detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. Every section serves a purpose, there's no explanation of what documentation files are or why scanning matters, and it assumes Claude knows how to use Glob and read files. | 3 / 3 |
Actionability | The steps are clear but lack executable code. The Glob pattern is listed as a plain text list rather than an actual glob command, the synthesis output is a template outline rather than a concrete example, and the consolidation step lacks specific commands for archiving files. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and covers the happy path plus the no-docs-found case. However, the consolidation step (Step 4) involves destructive operations (archiving/moving original files) without any validation or confirmation checkpoint, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | The skill is well-organized with a clear overview structure, and appropriately references external files (file-patterns.md, templates.md) for detailed content rather than inlining everything. References are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
f772de4
- Reviewed
Table of Contents
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.