file-server-guard

Scan directories recursively for exposed credential and configuration files.

147|11|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/CrawlScript/MMClaw --skill file-server-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-server-guard
Source: https://github.com/CrawlScript/MMClaw/tree/main/mmclaw/skills/file-server-guard
Command: npx skills add https://github.com/CrawlScript/MMClaw --skill file-server-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents the accidental exposure of sensitive files (like API keys, credentials, or private keys) when a directory is made accessible over HTTP.

Core Features & Use Cases

  • Sensitive File Detection: Scans a specified directory recursively for common sensitive file patterns.
  • Pre-Server Safety Check: Acts as a mandatory gatekeeper before using a file-serving skill.
  • Use Case: Before sharing a project folder via a temporary HTTP server, run this skill to ensure no .env files or private keys are inadvertently exposed to the network.

Quick Start

Use the file-server-guard skill to scan the directory '/path/to/my/project'.

Frequently Asked Questions about file-server-guard

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

FAQPage Schema
How do I scan a directory for sensitive files before serving over HTTP?

To scan a directory for sensitive files before HTTP serving, you can use this skill to recursively check for common credential, key, and configuration file patterns, ensuring directory safety by flagging potentially exposed sensitive data.

What types of sensitive files are detected during a directory scan?

The directory scan detects common sensitive files such as API keys, credentials, private keys, and configuration files by matching known sensitive file patterns recursively within the specified target directory.

Can I check a project folder for exposed .env files before starting a temporary HTTP server?

Yes, you can check a project folder for exposed .env files by running this scan as a mandatory pre-server safety check, preventing the accidental exposure of credentials when sharing directories over a network.

How do I prevent accidental exposure of private keys when sharing files over HTTP?

To prevent accidental exposure of private keys over HTTP, run a pre-server safety check that recursively scans the directory and flags potentially exposed sensitive data before the files are made accessible to the network.

What is the best way to ensure directory safety before making files accessible over a network?

The best way to ensure directory safety is to scan the specified directory recursively for common sensitive file patterns before serving, acting as a gatekeeper to flag potentially exposed credentials and configuration files.