prefer-second-monitor
Skill1 starsChanged 2 months agoMITView on GitHub
Place task-owned Windows application windows on a secondary display when available and practical.
In this repository16 other files it gives its agents.
- adversarial-refinement-loopSkill
- atomic-commitsSkill
- audio-verificationSkill
- build-without-fearSkill
- comfyui-assetsSkill
- diagnosing-bugsSkill
- finish-the-listSkill
- frontend-designSkill
- headless-terminal-workflowSkill
- parallelize-independent-workSkill
- require-external-communication-approvalSkill
- state-of-the-art-firstSkill
- try-it-firstSkill
- visual-verificationSkill
- web-design-guidelinesSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 8
Use the application's own monitor or window-position option when possible.
- Distinctive: line 12
If needed, use the placement helper on Windows with the exact process ID launched for this task.
- Distinctive: line 15
Run without -Apply first to inspect the proposed display and window handles.
- Distinctive: line 25
Keep a window on the primary screen when capture, input, fullscreen, a modal parent, or tool limitations make secondary placement …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Prefer a secondary display
Use the application's own monitor or window-position option when possible. Inspect current display topology; prefer a non-primary display, or the display the user named. Single-monitor systems use the available screen without a pause.
If needed, use the placement helper on Windows with the exact process ID launched for this task. Establish ownership from the launch record and current process identity before using -Apply. Run without -Apply first to inspect the proposed display and window handles. Pass -DeviceName explicitly when a particular display is required; its default is the first non-primary screen sorted by device name.
The helper preserves size and z-order and requests no activation. It positions windows relative to the working area's origin but does not guarantee DPI-aware fitting, centering, or containment of oversized windows. Inspect the actual result, especially with mixed DPI, portrait displays, or negative coordinates. A zero window_count means no window was placed, regardless of the status label.
Keep a window on the primary screen when capture, input, fullscreen, a modal parent, or tool limitations make secondary placement unreliable. Preserve unrelated user windows and all display settings. Move only task-owned windows. Headless processes have no placement requirement; placement itself is not evidence that the application works.
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.

