Claude to plan a private NAS document reorganization
Patrick Frey had accumulated 25 years of documents on a Synology NAS. The storage system worked, but its folder structure made documents difficult to find. He used Claude Code to analyze the organization and suggest a clearer structure while placing a specific limit on what the agent could read.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Analyze this document archive using only filenames, folder paths and metadata. Do not open file contents. Produce an organization report and proposed top-level structure for me to review before any moves.
Reach people exploring AI agents
See placements →What happened
The archive received a structured organization review and selected changes, including a numbered top-level approach; no timed savings are reported.
Reported by Patrick FreyHow the agent did it
- Limit the archive review to filenames, folder paths and metadata.
- Generate an organization report and proposed top-level structure.
- Apply selected recommendations yourself and repeat the review as needed.
Where a person stepped in
Frey selected and applied changes himself, keeping document contents outside the agent's review.
Patrick Frey had accumulated 25 years of documents on a Synology NAS. The storage system worked, but its folder structure made documents difficult to find. He used Claude Code to analyze the organization and suggest a clearer structure while placing a specific limit on what the agent could read.
The review used filenames, folder paths and metadata, not document contents. That boundary mattered because the collection included financial and medical information. Claude created a Python-based workflow and a reusable directory-organization skill to examine the structure and report recommendations.
One suggestion was a numbered top-level folder system. Frey considered the report and applied selected changes himself, returning to the agent iteratively rather than accepting a wholesale rearrangement of the archive. He also constrained where generated outputs belonged and avoided extra Markdown files appearing throughout the document tree.
The account therefore describes an analysis-and-decision workflow, rather than an unattended cleanup. The agent worked on the archive's organization, while the owner decided which recommendations suited his way of finding information. The source reports the resulting review and adopted suggestions, without measuring search-time savings or claiming that all 25 years of documents were automatically reorganized. A reader could copy the narrow metadata boundary and the report-first approach before making changes to their own archive.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: patrickfreyleanpm.com · Patrick Frey
Frequently asked questions
Did Claude read financial or medical documents?
The author's stated boundary restricted the analysis to filenames, paths and metadata rather than file contents.
Did the agent rearrange the whole archive?
The author considered the recommendations and applied selected changes himself.
What kept generated files from cluttering the archive?
The workflow constrained outputs to the working location and avoided extra Markdown files across the document tree.
More details
About this account
Claude wrote a metadata-based analysis workflow and produced organization recommendations through a reusable skill.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Patrick Frey
Source published 27 Jul 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Python · Synology NAS · Organize directory skill
Document organization · NAS files · Metadata-only review
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.