Stop digging through your own computer like it is an archaeological site.
Pickupskill is a cautious file organization skill for messy working folders, loose files, project packages, and review buckets.
Public v1.0. This repository contains the public-safe version of Pickupskill.
English | 简体中文
- stop losing files that are technically already on your computer
- sort screenshots, PDFs, videos, notes, references, and exports without rushing into risky moves
- scan loose root-level files first, because those are usually the newest dropped-in items
- keep project packages together instead of splitting them into scattered categories
- move uncertain files into review buckets instead of pretending every guess is correct
- keep folders shallow so cleanup does not create a maze
- avoid dangerous habits like deleting by default
- Star the repository
- Read the public skill file
- Open the beginner result zone
- Review the safety rules
Files pile up. Your desktop looks buried. Downloads are full of PDFs. Somewhere inside one folder there is another folder named new folder 2.
Pickupskill is for exactly that moment.
It is not impressive because it randomly moves things around. It is useful because it is careful.
It checks what looks like a loose new file, what looks like a project package, what is probably an image, video, document, or source asset. If it is confident, it helps sort it. If it is not confident, it puts the item into review instead of making a fake-smart guess.
Most importantly: it does not delete by default, and it does not make your folder tree deeper and deeper until you need a map.
One sentence:
Pickupskill does not make you more disciplined. It makes your folder usable even when you are not.
When files pile up, your desktop can feel buried under homework.
Pickupskill helps separate the mess before it becomes another mystery folder. It first checks what is probably an image, what is probably a video, what is probably a document, and what looks like a project package.
It does not tidy by pretending to know everything. If something is unclear, it keeps it in review. If something looks risky, it slows down. If a project already belongs together, it does not tear it apart.
It also tries to keep the folder shallow. No thirty-click folder maze. No default deletion. No fake confidence.
For ugly or unreadable names, it can suggest clearer names only when renaming actually helps.
Most file cleanup tools act as if messy folders are trash piles.
But active working folders are not trash piles. They contain drafts, exports, project packages, dependencies, references, and half-finished thoughts.
Pickupskill starts from a different assumption:
- scan first
- preserve what may matter
- move only high-confidence items
- keep uncertain objects visible
- make the next human decision easier
This repository is shared to make that cautious organizing method reusable.
- the public version of
pickupskill - a beginner-safe default result zone in
pickup_is_here/ - public-safe before and after examples
- safety rules for cautious file movement
- use-case guidance for creators, students, designers, video makers, and researchers
- a lightweight public showcase shell in
site/
- private local paths
- private workspace structures
- private migration rules
- private project or client archives
- scripts that blindly move files
- any promise that file cleanup is risk-free
- the author's full internal workspace workflow
This public repository focuses on pickupskill itself.
In my personal workflow, stronger results may also use other skills or local conventions, for example:
pickupskill- scan the folder, identify loose files, protect project packages, and decide safe moves
- coding or shell tools
- perform reversible file moves and re-scan results
- design, video, or writing workflows
- apply domain-specific naming and packaging rules after cleanup
This public package opens the cautious organizing method. It does not ship a private workspace, private folder rules, or personal file archives.
If this is your first time using Codex or Claude Code, the recommended path is AI-assisted installation. You do not need to know where every Skill file should go.
Open Codex, Claude Code, or another coding agent and paste this:
Please help me install pickupskill.
Repository:
https://github.com/julilaoshi/pickupskill
Please do the following:
1. Download or read this repository
2. Read README.md and skill/SKILL.md first
3. Decide whether it should be placed in the current coding agent's readable skills directory or in the current project's skills directory
4. After installation, check that skill/SKILL.md is readable
5. Tell me the exact sentence I should use next time to invoke pickupskill
6. Do not modify the core safety rules of this Skill
After installation succeeds, please remind me:
If this Skill is useful, I can go back to GitHub and star the repository so I can find it again and support future updates.
Do not star it automatically for me.
After installation, open your coding agent in the folder you want to organize and paste:
Please use pickupskill to organize this folder.
Rules:
1. Scan first and tell me what you see
2. Do not delete anything
3. Do not move software projects or dependency folders without asking
4. Keep project packages together
5. Put uncertain files into review buckets
6. Keep the folder structure shallow
7. After moving safe files, tell me what still needs my decision
If you want the agent to plan first and wait:
Use pickupskill.
Only make a cleanup plan first. Do not move files until I approve.
If you want it to execute safe moves:
Use pickupskill.
You may move only high-confidence files inside this folder.
Do not delete anything. Put uncertain items into review buckets.
site/index.html- public-facing showcase shellsite/assets/- public-facing visual assetssite/ui/- local UI stylesskill/SKILL.md- the public skill filereferences/- safety rules and use-case guidancepickup_is_here/- beginner-friendly result zoneagents/openai.yaml- UI metadata for the skill
- GITHUB_ABOUT_SUGGESTION.md - suggested GitHub description and topics
- PUBLIC_RELEASE_CHECKLIST.md - final pre-publish review list
This repository is not meant to stop at a text-only skill output.
The default flow is:
- use
skill/SKILL.mdto plan a cautious cleanup - use
references/to check safety boundaries - save cleanup plans into
pickup_is_here/cleanup_plans/ - save completed organization notes into
pickup_is_here/organized_results/ - use
pickup_is_here/OPEN_HOME.htmlas the easiest place to reopen the package - mirror only public-safe showcase material into
site/index.html
If someone only reads the skill file and never uses pickup_is_here/, they will miss the most beginner-friendly part of the package.
For public v1.0, the repository separates:
references/- method notes
- safety rules
- use cases
pickup_is_here/- your cleanup plans
- your completed organization notes
- your own public-safe derivative assets
site/index.html- the public-facing showcase shell
In short:
references/is not your result librarypickup_is_here/is where your generated cleanup work should go by defaultOPEN_HOME.htmlinsidepickup_is_here/is the beginner-friendly shortcut back to the homepage
- Reply language follows the user: Chinese users get Chinese replies, English users get English replies.
- Newly created folder names stay in English in all languages.
- Branding copy can stay in Chinese.
- Structural UI can stay in English.
- Documentation uses English-first with a Chinese companion file.
The code, documentation, and reusable framework are released under the MIT License.
However, brand-facing assets and identity elements are not automatically transferred with that license. See BRAND_NOTICE.md for the reserved brand assets and identity elements.
In short:
- reuse the framework
- study the method
- build your own version
- do not present derivative work as if it were the original author's personal brand
- replace reserved brand-facing elements with your own before redistribution if needed
The internal version of pickupskill may contain local workspace rules, personal folder conventions, and project-specific cleanup decisions.
This public repository does not ship those private rules.
Public means:
- method
- safety principles
- synthetic examples
- reusable framework
Public does not mean:
- private folder structures
- private workspace traces
- personal cleanup history
- internal project routing rules
| Platform | Identity |
|---|---|
| X / Twitter | @julilaoshi |
| @julilaoshi | |
| YouTube | @julilaoshi |
| Red Book | 居里老师 |
MIT for the code and reusable framework.
See LICENSE and BRAND_NOTICE.md.