Agent skill · AI & Agents

file-organizer

Triggered when the user needs to organize project files, analyze directory structure, or generate a project report. Use MCP tools to read file contents and produce a structured organization report. Trigger phrases include "help me organize this project", "look at the directory structure", "generate a project summary".

Alibaba76,861★ · +800/wk · 4 repos on radarProfile →
claude-codeships scriptsApache-2.0
Install
npx skills add alibaba/skill-up --skill file-and-tool-rules --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 13
SKILL.md size: 1 KB
Bundled scripts: yes
Path: e2e/testdata/file-and-tool-rules/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 374
Language: Go

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# File Organizer Assistant You are an efficient project file organization assistant. You use MCP tools to analyze project structure, read key files, and generate clear project reports and summaries. ## Workflow 1. **Analyze directory structure**: Use the `list_directory` tool to scan the project root 2. **Read key files**: Use the `read_file` tool to read README, config files, etc. 3. **Generate report**: Create `report.md` with project overview and key findings 4. **Generate summary**: Create `summary.json` with structured project information ## Output Files ### report.md The project report should include: - Project name and description - Directory structure overview - Key file descriptions - Improvement suggestions ### summary.json Structured summary containing: ```json { "project_name": "...", "total_files": 42, "languages": ["go", "yaml"], "has_tests": true, "has_ci": true } ``` ## Notes - Do not modify or delete any existing files - Use relative paths for file paths in the report - Skip content reading for binary files - Temporary files (e.g. temp.log, .cache) must not appear in the output

What's inside
Steps it walks through
  1. Workflow
  2. Output Files
  3. report.md
  4. summary.json
  5. Notes
Ships with 12 files
  • README.md
  • evals/cases/organize-project.yaml
  • evals/eval.yaml
  • evals/evals.json
  • evals/fixtures/golden/expected-report.md
  • evals/fixtures/workspace/README.md
  • evals/fixtures/workspace/src/main.go
  • fixtures/expected/organize-project-grading.json
  • fixtures/golden/expected-report.md
  • fixtures/judge-inputs/organize-project.json
  • fixtures/workspace/report.md
  • fixtures/workspace/summary.json
More from skill-up
All skills →
About this skill
What does the file-organizer skill do?

Triggered when the user needs to organize project files, analyze directory structure, or generate a project report. Use MCP tools to read file contents and produce a structured organization report. Trigger phrases include "help me organize this project", "look at the directory structure", "generate a project summary".

How do I install it?

Run `npx skills add alibaba/skill-up --skill file-and-tool-rules --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alibaba/skill-up, a repository with 374 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going