headless-terminal-workflow
Skill1 starsChanged 2 months agoMITView on GitHub
Keep Windows commands and helper processes hidden during local execution and application testing.
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
- parallelize-independent-workSkill
- prefer-second-monitorSkill
- 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
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 11
Prefer browser automation, file/log inspection, and process-level diagnostics over opening a terminal window.
- Distinctive: line 12
Do not deliberately surface, focus, move, maximize, or reuse a visible terminal on the user's desktop.
≈ “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
Headless Terminal Workflow
Honor the user's quiet-workspace preference.
- Launch task-owned command work through noninteractive execution, hidden/background processes, redirected logs, or headless automation.
- Prefer browser automation, file/log inspection, and process-level diagnostics over opening a terminal window.
- Do not deliberately surface, focus, move, maximize, or reuse a visible terminal on the user's desktop.
- A visible terminal is allowed only when it is genuinely necessary for a task and no headless route can provide the needed capability. State that limitation before opening it.
- Preserve user-owned terminals and other windows. Stopping a task-owned headless process is fine when it is no longer needed.
- This preference is independent of monitor placement: if a GUI is necessary, apply the secondary-display policy separately.
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.