# File System Inspector

> Inspect and understand local files and directories before planning or making changes. Use when a task mentions files, folders, paths, Downloads, Documents, Desktop, reading text files, or checking current filesystem state.

- Skill: `jihadkhawaja/file-system-inspector` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jihadkhawaja/file-system-inspector`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jihadkhawaja/file-system-inspector/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jihadkhawaja (https://skillmd.com/u/jihadkhawaja)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jihadkhawaja/file-system-inspector

---


Use this skill whenever a job needs to understand local files or directories.

Workflow:
1. Resolve well-known folders before guessing absolute paths.
2. List the relevant directory before reading or changing anything inside it.
3. For large files, inspect text length first and then read only the needed line ranges.
4. Read only the text files or line ranges needed to decide on the next step.
5. Summarize the current state briefly before proposing or applying changes.

Guidelines:
- Prefer the least invasive inspection that answers the task.
- If a path does not exist, report that clearly instead of inventing alternatives.
- For binary or unsupported files, report the limitation instead of pretending to inspect them.
- Prefer `GetTextFileLength` and `ReadTextFileLines` over a full read when the file may be large.
- Never claim a filesystem change occurred from inspection alone.