feat: finalize production cleanup with structured agent responses and project governance
This commit is contained in:
33
SKILL.md
Normal file
33
SKILL.md
Normal file
@@ -0,0 +1,33 @@
|
||||
# ScreenJob Skill (OpenClaw Agents)
|
||||
|
||||
## What ScreenJob Solves
|
||||
|
||||
ScreenJob lets an agent execute tasks that require a real desktop UI plus terminal access, with structured tool calls and job tracking.
|
||||
|
||||
## Main Features
|
||||
|
||||
- Screen perception (`see_screen`, `enhance`)
|
||||
- Mouse/keyboard control (`click`, `type`, `press_key`)
|
||||
- Terminal execution (`execute_command`, `sleep`)
|
||||
- Structured completion payload (`task_complete(return=..., data=...)`)
|
||||
- Safety gate, auth, history, and live monitoring
|
||||
|
||||
## Important Environment Note
|
||||
|
||||
ScreenJob runs on a separate computer (the human/operator machine), not inside the agent's own runtime environment.
|
||||
|
||||
## Why It Is Useful
|
||||
|
||||
Agents can use ScreenJob to launch and control GUI workflows, including orchestrating other GUI agents/tools on a human computer.
|
||||
|
||||
## Example Tasks
|
||||
|
||||
- Open amazon.de and buy a USB-C to USB-C cable for 10 EUR or less.
|
||||
- Open google.com, go to my account, and change my profile picture to a provided image URL.
|
||||
- Run `ls -a` in `C:/Users/username/Documents` and return the output in `data`.
|
||||
|
||||
## Practical Usage
|
||||
|
||||
1. Submit job via CLI or API.
|
||||
2. Agent performs tool loop.
|
||||
3. Read final `response.return` and `response.data` from job status.
|
||||
Reference in New Issue
Block a user