How do I install the Doc Scanner skill?

Run npx skillmds@latest add aiskillstore/doc-scanner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doc Scanner safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doc Scanner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doc Scanner free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Doc Scanner?

aiskillstore (@aiskillstore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doc Scanner by aiskillstore — Agent Skill

Name: Doc Scanner
Rating: 4.5 (4 reviews)
Author: aiskillstore

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.

aiskillstore Updated Sep 9, 2026

File contents

Documentation Scanner

Scan for and synthesize project documentation.

When to Activate

User asks to review, understand, or explore a codebase
Starting work in a new/unfamiliar project
User asks about project conventions or workflows
Before making significant architectural decisions

Instructions

Step 1: Scan for Documentation

Use Glob to search project root:

AGENTS.md, CLAUDE.md, AI.md, ASSISTANT.md,
GEMINI.md, COPILOT.md, CHATGPT.md, CODEIUM.md,
CURSOR.md, WINDSURF.md, VSCODE.md, JETBRAINS.md,
WARP.md, FIG.md, DEVCONTAINER.md, GITPOD.md

Step 2: Read All Found Files

Read complete contents of every documentation file found.

Step 3: Synthesize

Combine information into unified summary:

PROJECT DOCUMENTATION

Sources: [list files found]

RECOMMENDED AGENTS
  Primary: [agents for core work]
  Secondary: [agents for specific tasks]

KEY WORKFLOWS
  [consolidated workflows]

CONVENTIONS
  [code style, patterns]

QUICK COMMANDS
  [common commands]

Step 4: Offer Consolidation

If 2+ documentation files exist, offer to consolidate:

Create .doc-archive/ directory
Archive originals with date suffix
Generate unified AGENTS.md
Report what was consolidated

Step 5: No Documentation Found

If none found, offer to generate AGENTS.md based on:

Project structure and tech stack
Patterns observed in codebase

Priority Order

AGENTS.md (platform-agnostic)
CLAUDE.md (Claude-specific)
Other AI docs
IDE docs
Terminal docs

Additional Resources

For detailed patterns, load:

./references/file-patterns.md - Complete list of files to scan
./references/templates.md - AGENTS.md generation templates

When generating a NEW AGENTS.md, follow the entry-doc standard in rules/agentic-quality.md (Landmines section mandatory, ~150-line budget) — skeleton at the repo-doctor skill's assets/AGENTS-template.md. To AUDIT an existing doc set rather than generate one, hand off to repo-doctor.

---name: doc-scannerdescription: 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.license: MIT--- # Documentation Scanner Scan for and synthesize project documentation. ## When to Activate - User asks to review, understand, or explore a codebase - Starting work in a new/unfamiliar project - User asks about project conventions or workflows - Before making significant architectural decisions ## Instructions ### Step 1: Scan for Documentation Use Glob to search project root: ``` AGENTS.md, CLAUDE.md, AI.md, ASSISTANT.md, GEMINI.md, COPILOT.md, CHATGPT.md, CODEIUM.md, CURSOR.md, WINDSURF.md, VSCODE.md, JETBRAINS.md, WARP.md, FIG.md, DEVCONTAINER.md, GITPOD.md ``` ### Step 2: Read All Found Files Read complete contents of every documentation file found. ### Step 3: Synthesize Combine information into unified summary: ``` PROJECT DOCUMENTATION Sources: [list files found] RECOMMENDED AGENTS Primary: [agents for core work] Secondary: [agents for specific tasks] KEY WORKFLOWS [consolidated workflows] CONVENTIONS [code style, patterns] QUICK COMMANDS [common commands] ``` ### Step 4: Offer Consolidation If 2+ documentation files exist, offer to consolidate: 1. Create `.doc-archive/` directory 2. Archive originals with date suffix 3. Generate unified AGENTS.md 4. Report what was consolidated ### Step 5: No Documentation Found If none found, offer to generate AGENTS.md based on: - Project structure and tech stack - Patterns observed in codebase ## Priority Order 1. AGENTS.md (platform-agnostic) 2. CLAUDE.md (Claude-specific) 3. Other AI docs 4. IDE docs 5. Terminal docs ## Additional Resources For detailed patterns, load: - `./references/file-patterns.md` - Complete list of files to scan - `./references/templates.md` - AGENTS.md generation templates When generating a NEW AGENTS.md, follow the entry-doc standard in `rules/agentic-quality.md` (Landmines section mandatory, ~150-line budget) — skeleton at the repo-doctor skill's `assets/AGENTS-template.md`. To AUDIT an existing doc set rather than generate one, hand off to `repo-doctor`.

Frequently asked questions