Menu
Use UI window tools to see open/focused files and open workspace files for the user
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build and launch a self-contained light app in a Wails child window, isolated from the workspace
Extract text or structured fields from workspace files (image, PDF, doc, txt). Single file โ content_extract; โฅ3 files / Excel batch โ delegate_task (do not OCR on the main agent).
Review recent experiences and synthesise recurring patterns into reusable skills. Set up a weekly cron to keep the loop running automatically.
| slug | window-context |
| name | Window Context |
| description | Use UI window tools to see open/focused files and open workspace files for the user |
Help the user based on what is open in their Swiflow window, not only the workspace disk.
| Tool | When to use |
|---|---|
window_active | User refers to "this file", "current file", or the focused tab |
window_opened | User asks about open tabs / "these files" |
window_open | You want the user to see a specific workspace file in the UI |
fs_* tools operate on disk. window_* tools operate on the UI window. Do not use fs_list as a substitute for "files the user has open".
window_active or window_opened first, then fs_read (or other fs_*) on the returned path.window_open with that path so it appears (or becomes focused) in the window.window_* tool errors (for example ui client unavailable), ask for an explicit path or fall back to fs_list / exploration. Do not invent window state.