File and tool rules
An evaluation and evolution tool for Agent Skills.
npx -y skills add alibaba/skill-up --skill file-and-tool-rulesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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".
SKILL.md
1.5 KB, as published. Nobody here has run it
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
- Analyze directory structure: Use the
list_directorytool to scan the project root - Read key files: Use the
read_filetool to read README, config files, etc. - Generate report: Create
report.mdwith project overview and key findings - Generate summary: Create
summary.jsonwith 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:
{
"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