| name | ops-client |
| description | Use when directly operating or verifying a specified real desktop client, or collecting evidence for an already-isolated client-layer failure. Do not use for unexplained or cross-system root-cause diagnosis. |
Ops Client
Overview
Operate and verify real desktop client windows. Treat platform automation as adapter-specific: the current built-in evidence path is macOS-first, while Windows and Linux require an available platform adapter before equivalent claims can be made. Use implement-frontend for UI code changes.
Workflow
- Identify the specified client target: app name, repository path, package/app directory, process, PID, visible window, platform, and requested evidence.
- Run a capability preflight and record available/unavailable/unknown for:
- process enumeration and runtime-source inspection;
- window enumeration with stable window identifiers;
- window-specific screenshot capture;
- Accessibility/control-tree inspection and semantic actions;
- background-safe operation without stealing mouse/focus;
- app launch/restart and permission state.
- If working from a repository, confirm whether it contains a desktop/client app by checking manifests and source layout such as
src-tauri/, tauri.conf.*, Electron configs, native targets, package scripts, justfile tasks, or README run instructions.
- Confirm the startup command and runtime source before verification: dev command, debug bundle, release app, Electron/native run command, or
Not found/Not verified when unclear.
- Select the platform adapter:
- macOS: identify process/PID and matching
CGWindowID; capture with screencapture -x -l<CGWindowID> when available; use macOS Accessibility for semantic controls.
- Windows: require an available UI Automation/window-capture adapter and stable HWND/process evidence; otherwise use Degraded Evidence mode.
- Linux: require an available AT-SPI/window-manager capture adapter and stable window/process evidence; otherwise use Degraded Evidence mode.
- Identify the exact real window by process owner, PID, title, bounds, and platform identifier. Do not substitute browser preview evidence.
- Capture and inspect the real window using the selected adapter before making visual claims.
- Prefer background-safe Accessibility/control-tree actions on named controls over coordinate clicks.
- Rebuild/restart the intended client instance after relevant UI, bundle, native, or Accessibility changes before re-verifying.
- Report unsupported platform claims explicitly rather than emulating them with a browser page or cropped screenshot.
- Use Client Debug Evidence only when delegated by
diagnose or when the caller supplies an already-isolated client-layer reproduction whose requested output is direct client evidence. Otherwise route unexplained or cross-system root-cause requests to diagnose before operating the client. For an accepted evidence task, verify the real process/window/build source, collect direct client evidence, clean disposable task state, and return the evidence to diagnose or the caller.
Modes
- Capability Preflight: verify platform, permissions, process/window enumeration, capture, Accessibility, and restart support before operation.
- Launch Review: identify the repository-owned client app and startup command before running or verifying it.
- Window Evidence: prove process, runtime, real-window identity, platform adapter, and screenshot source.
- Interaction: use Accessibility/control-tree paths before coordinate clicks.
- AI-Operable UI Evidence: verify semantic controls and stable names so agents can identify critical actions reliably.
- Client Debug Evidence: only after
diagnose delegation or an already-isolated client-layer evidence request, reproduce on the verified real client instance, capture process/window/build/control evidence, test one client-layer hypothesis at a time, and return evidence to diagnose or the caller without owning the final cross-system root cause.
- Degraded Evidence: when the required platform adapter or permission is missing, report only process/repository evidence that can be proven and list exact blocked claims.
Do Not Use For
- Plain browser pages, web previews, form workflows, downloads, or browser console/network checks; use
ops-browser.
- Frontend implementation, desktop webview architecture, IPC layering, or design-system work; use
implement-frontend.
- Ordinary repository discovery unless the user asks for client launch review, real-window verification, or browser-preview invalidation.
- Browser preview evidence when the task requires proof from a Tauri, Electron, or native desktop runtime.
- Repository onboarding or context discovery; use
repo-context.
- Future implementation planning; use
code-planner.
- Local dirty-tree review or commit readiness; use
code-review.
- Security-only review; use
audit-security.
- Cross-system root-cause coordination for a frozen, stale, non-responsive, or dev-versus-release failure; use
diagnose, which may delegate real-client evidence collection here.
Hard Rules
- Do not claim cross-platform support from a macOS-only procedure.
- Do not treat browser previews, dev server pages, region screenshots, or app-like web tabs as desktop-client evidence unless the user explicitly asks for browser-only checking.
- Do not start or restart a client before confirming the startup command source and whether it could disturb an existing app instance, active window, unsaved state, or user workflow.
- Do not assume Accessibility or screen-capture permission. Verify the action succeeds or mark it unavailable.
- Do not steal the user's mouse, move the pointer, activate unrelated windows, or coordinate-click unless no stable control path exists, the target window is revalidated, and the risk is acceptable.
- Prefer semantic controls, accessible names, labels, roles, stable automation identifiers, and repository-supported test ids for critical controls.
- On macOS, verify
CGWindowID, owner/PID/title/bounds, and capture result before calling a screenshot real-window evidence.
- On Windows or Linux, require the platform adapter's stable window/process identifier and capture provenance; do not reuse macOS terminology or commands.
- If only a process can be proven, do not infer that the requested window is visible, current, or running the new build.
- For code changes that add accessibility or automation surfaces, use
implement-frontend or the relevant native implementation skill; return here for runtime verification.
- Re-verify the target process, runtime source, and window after rebuild/restart; stale windows do not prove current code.
- Confirm only direct client facts. Do not claim a final cause across frontend, IPC, Rust, database, packaging, or platform layers, and do not decide a permanent fix; return the evidence to
diagnose or the caller.
- Remove disposable task state such as temporary probes, injected instrumentation, test windows, and launched test instances when safe. Retain screenshots, logs, traces, and other handoff evidence until they are embedded, archived, or explicitly accepted by the handoff owner; report retained artifact paths/identifiers, embedded evidence, removed disposable state, and anything left running.
- Say
Not supported when no adapter exists for the requested platform capability and Not verified when the adapter exists but the check was not completed.
Output Contract
Report platform and selected adapter, capability preflight, specified client target, repository/client ownership evidence, startup command or Not found, target process/runtime, stable real-window identity, screenshot source/provenance, interaction method, Client Debug Evidence and handoff owner when relevant, permission or adapter gaps, restart/rebuild status, cleanup status, and all Not supported or Not verified claims.
Skill Maintenance
When maintaining this package, keep SKILL.md concise, move platform-specific procedures to references/ when they grow, update agents/openai.yaml, and run python3 scripts/validate-skills.py.
References
