Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

File Organizer

ASecurity

Clean up a messy folder with a dry-run plan before moving anything

147 stars
0 votes
2 copies
2 views
Added 9/3/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/3/2026

$npx -y skills add prapaa-ai/agav --skill file-organizer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of File Organizer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for File Organizer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/prapaa-ai-file-organizer/badge)](https://www.skillsdirectory.com/skills/prapaa-ai-file-organizer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: file-organizer
description: Clean up a messy folder with a dry-run plan before moving anything
version: 1.0.0
invocation: both
allowed-tools: read_file list_directory find_files run_command
tags:
  - files
  - organization
---

# File Organizer

Reorganize a messy folder (Downloads, Desktop, Documents) with user approval at every step.

## Instructions

1. List the target folder's contents (including file sizes and dates) and categorize: documents, images, spreadsheets, installers, archives, duplicates, and unknown.
2. Propose a move plan BEFORE executing anything: a table of source → destination grouped by category, using folders like `Invoices-2025/`, `Screenshots/`, or the user's existing structure if the folder already has one.
3. Rules for the plan:
   - Never move files the user is likely actively using (modified today) without asking.
   - Detect duplicates by name and size; list them for the user to decide, never delete on your own initiative.
   - Do not touch hidden files, dotfiles, system files, or anything outside the folder the user named.
   - Suggest installers (.exe, .msi, .dmg) and archives for deletion review rather than filing them.
4. On ambiguous files (no extension, cryptic names like `IMG_0001`), inspect content with read_file where possible and say what you found; otherwise ask.
5. Wait for explicit approval of the plan. Execute moves with `mv` (or `Move-Item` on Windows), one category at a time, so partial runs stay coherent.
6. After moving, print a summary: how many files moved where, and anything left in place and why. If a move fails (file in use, permission denied), report it and continue with the rest rather than aborting.
7. This skill moves files; it never deletes. If the user asks for deletion, propose the list and let them run it themselves or approve each step.

Attribution

prapaa-aiprapaa-ai
View sourceSee grades on GitHubMore from prapaa-ai →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →