somatic

Automate desktop UI clicks and keyboard input using YOLO-detected element IDs.

18|1|Updated May 18, 2026
One-click install
npx skills add https://github.com/Smyan1909/SoMatic --skill somatic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: somatic
Source: https://github.com/Smyan1909/SoMatic/tree/main
Command: npx skills add https://github.com/Smyan1909/SoMatic --skill somatic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SoMatic provides a framework to automate desktop UI tasks by targeting elements with YOLO-detected IDs rather than guessing at pixel coordinates, reducing errors and speeding up automation workflows.

Core Features & Use Cases

  • Full end-to-end automation of native desktop UI via mark IDs, including clicking, typing, scrolling, and movement.
  • Works with multiple surfaces (native apps, browsers, PDFs) and supports MCP-based integration for agents.

Quick Start

Initialize vision, capture an annotated screenshot, inspect the marks, and click the appropriate mark to operate the UI.

Frequently Asked Questions about somatic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate desktop UI tasks without relying on raw pixel coordinates?

You can automate desktop UI tasks by using YOLO-detected element IDs to target buttons and fields. SoMatic annotates GUI surfaces with numbered marks, allowing you to click or type via specific IDs rather than guessing coordinates.

Can I use YOLO object detection to automate native desktop applications and web browsers?

Yes, YOLO object detection can automate native desktop applications and web browsers. SoMatic works across multiple GUI surfaces including native apps, browsers, and PDFs by applying an ONNX model to detect and annotate interactive elements.

How does MCP-based integration work with YOLO-detected UI elements?

MCP-based integration connects agents to a locally running vision daemon that processes GUI screenshots with an ONNX model. The daemon returns annotated marks, which agents then use to perform clicks or keyboard input on the targeted elements.

Do I need a locally running ONNX model to capture annotated screenshots for UI automation?

Yes, a locally running ONNX model is required to capture annotated screenshots for UI automation. The vision daemon loads the ONNX model to detect elements, annotate them with numbered IDs, and enable the CLI operating loop.

What is the best way to click or type into native apps using detected element marks?

The best way to click or type into native apps using detected marks is through mark IDs, offsets, or direct coordinates. SoMatic lets you initialize the vision daemon, inspect the annotated screenshots, and execute actions based on the numbered element IDs.

Why does coordinate-based UI automation fail when dealing with varying desktop layouts?

Coordinate-based UI automation fails because it guesses pixel locations without understanding the actual elements. SoMatic solves this by using YOLO-detected element IDs, which reduces errors and speeds up workflows across changing GUI surfaces.