kestral-scan-folder

Scan local directories to inventory and categorize project documents and media.

4|Updated May 26, 2026
One-click install
npx skills add https://github.com/Kestral-Team/kestral-plugins --skill kestral-scan-folder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kestral-scan-folder
Source: https://github.com/Kestral-Team/kestral-plugins/tree/main/skills/kestral-scan-folder
Command: npx skills add https://github.com/Kestral-Team/kestral-plugins --skill kestral-scan-folder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual effort of organizing and identifying relevant project documentation, media, and context files when onboarding a new project into Kestral.

Core Features & Use Cases

  • Automated Inventory: Scans local directories to identify documents, images, and media while automatically filtering out noise like build artifacts and hidden files.
  • Evidence Signal Detection: Analyzes file paths and content samples to categorize documents by purpose, such as architecture, requirements, or runbooks.
  • Use Case: When starting a new project, use this skill to quickly scan a folder of legacy documentation to identify which files are critical for the AI agent to understand the project's history and requirements.

Quick Start

Ask the agent to scan the current project folder to identify and categorize all relevant setup evidence.

Frequently Asked Questions about kestral-scan-folder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory local files for project onboarding and context gathering?

Automated file scanning inventories local directories by filtering out build artifacts and hidden files, then categorizes remaining documents and media by analyzing file paths and content samples to support project onboarding workflows.

What is the best way to scan a folder for project documentation without including build artifacts?

Automated file scanning inventories local directories by filtering out build artifacts and hidden files, then categorizes remaining documents and media by analyzing file paths and content samples to support project onboarding workflows.

Can I categorize legacy documents by purpose like architecture or requirements during file scanning?

Yes, evidence signal detection analyzes file paths and content samples to categorize legacy documents by purpose such as architecture, requirements, or runbooks during the directory scanning process.

Do I need read access to the target directory for automated file inventory?

Yes, automated file inventory requires read access to the target directory to scan directory structures, extract metadata signals, and identify relevant project documents and media for AI context ingestion.

How does automated file scanning handle dependency artifacts and hidden files?

Automated file scanning excludes dependency artifacts and hidden files by utilizing glob patterns to identify relevant file types, ensuring only project-related documents and media are inventoried for context gathering.