wo
Skill0 starsChanged 26 days agoMITView on GitHub
Ask the owner questions and read his answers in his preferred format. Use whenever you need decisions from the owner, and when he types /wo or "what's open" to list everything you are waiting on him for.
In this repository24 other files it gives its agents.
- codebase-designSkill
- improve-codebase-architectureSkill
- uv-pythonSkill
- bw-loginSkill
- project-iconSkill
- recover-mouse-inputSkill
- wizardSkill
- dispatching-parallel-agentsSkill
- handoffSkill
- hill-climbSkill
- opcSkill
- opnSkill
- personal-skillsSkill
- reassign-pmSkill
- repo-lessonsSkill
- trialSkill
- unstuckSkill
- sampleSkill
- find-docsSkill
- liteparseSkill
- tco-searchSkill
- browse-xSkill
- frontend-designSkill
- playwrightSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Put every decision the owner must make in one numbered list at the end of the reply, never scattered through the text.
- Distinctive: line 13
Update Claude Code to 2.1.299 on all hosts?
≈ “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.
Files
wo: what's open
Asking the owner
- Put every decision the owner must make in one numbered list at the end of the reply, never scattered through the text.
- One line per item, in plain words, answerable with a short reply: yes/no, a pick, or a value. State your recommendation in the line.
- Example:
- Update Claude Code to 2.1.299 on all hosts? I recommend yes.
- Trim old Codex backups on the PC (frees 7.5 GB)? I recommend yes.
- Plan: Free or Teams ($6/mo)? I recommend Free.
Reading his answers
- Short lines sent together answer the last numbered list in order: line 1 answers item 1, and so on.
- "ok", "k", "ye", "lgtm" mean yes. "no" means no. "ok but X" means yes with change X.
- A line ending in "?" is a question about that item. Answer it, then re-ask only that item.
- Fewer lines than items: the rest stay open. If the mapping is unclear, say how you read it in one line and act on the clear ones.
/wo
When the owner types /wo or asks what's open, reply with only the numbered list of items you are still waiting on him for, in your own scope, oldest first, with your recommendation each. Include deadlines. If nothing is open, say "Nothing open." Do not repeat status or finished work.
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.