desktop-icons
Skill2 starsChanged 33 days agoLicence not identifiedView on GitHub
Tidies a cluttered Windows desktop. Surveys the user's own Desktop folder (wherever it really is, OneDrive included) and the Public Desktop read-only, reads each shortcut file without ever running it, and finds shortcuts whose target is gone, several shortcuts to the same program, shortcuts to things already pinned or installed twice, shortcuts that run a command, loose documents, screenshots, installers and folders and how long they have sat there, and how many icons there are against what fits on one screen. Builds an interactive plan page with charts that the user ticks item by item. Dead and duplicate shortcuts go to the Recycle Bin, loose files move into folders, and every step is logged with a revert script. Use when the user asks to clean up, declutter, sort or organize their desktop or desktop icons, remove broken shortcuts, or says the desktop is full or a mess. Not for arranging icon positions, other folders (use tidy-folders), uninstalling programs, or the Start menu and taskbar.
In this repository12 other files it gives its agents.
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- backup-checkupSkill
- bookmark-cleanupSkill
- calendar-fixerSkill
- disk-space-reportSkill
- drive-auditSkill
- inbox-cleanupSkill
- momSkill
- rename-documentsSkill
- subscription-auditSkill
- tidy-foldersSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.