Garage Assistant 4 Computer Control

VerifiedCaution

Interact with Garage Assistant 4, a FileMaker-based auto shop management system, through screenshots and precise clicks.

Sby Skills Guide Bot
ProductivityIntermediate
7/22/2026
Claude Code
#gui-automation#filemaker#computer-use#auto-shop#screenshot-driven

Recommended for

Automated summary

Drives Garage Assistant 4 (a FileMaker-based auto shop management system running on Windows inside Parallels) through screenshots and clicks using the garage-assistant MCP tools.

Strengths

  • Clear operating loop: screenshot first, locate coordinates, click, wait, then re-screenshot to verify
  • Practical FileMaker guidance: Find mode via ctrl+f, scrollable portals, dropdown fields, date field handling
  • Documented Windows keyboard shortcuts (ctrl+n, ctrl+d, ctrl+s, tab, escape)
  • Safety guardrails: no deletions without explicit confirmation, verify the active record, screenshot-based audit trail

Limitations

  • Tightly coupled to one application and a fixed screen size (1200 × ~820 px)
  • Relies on visually reading pixel coordinates, so it breaks if the FileMaker layout or theme changes
  • No described handling of Parallels/VM connection failures or unexpected dialogs beyond 'stop and ask the user'
When to use it

Use it whenever a task requires reading or entering data in Garage Assistant 4: looking up a vehicle, creating a repair order, or entering parts line items.

When not to use it

Avoid it for bulk edits or mass deletions, or when the same data can be moved through an export/import or API instead of clicking.

Security analysis

Caution
Quality score86/100

The skill uses only screenshot, mouse, keyboard, and window-inspection tools; it does not use shell, network, secrets, or obfuscated payloads. However, it grants direct control over a live FileMaker business application, so unintended clicks/typing could modify records. The included safety rules reduce risk, but the capability warrants caution rather than a purely safe rating.

Findings
  • •UI automation can modify or delete FileMaker records if coordinates or focus are wrong.
  • •Coordinate-based clicking is brittle and may act on unintended fields/buttons if the screen layout changes.
  • •The skill permits typing and keyboard shortcuts in a live business system, so incorrect input could alter customer/vehicle/repair-order data.
How this analysis is made

Examples

Vehicle lookup
In Garage Assistant 4, find the customer record for the 2016 Ford F-150 with plate ending in 4RT and show me their contact info and last three repair orders.
Create repair order
Create a new repair order in GA4 for Maria Delgado's 2018 Honda Civic, dated today, for a brake pad replacement, then screenshot it so I can confirm the details.
Enter parts
Add three line items to the open repair order in Garage Assistant 4: oil filter, 5W-30 oil (5 qty), and a drain plug gasket — verify with a screenshot when done.

allowed-tools: mcp__garage-assistant__screenshot, mcp__garage-assistant__click, mcp__garage-assistant__double_click, mcp__garage-assistant__right_click, mcp__garage-assistant__type_text, mcp__garage-assistant__press_key, mcp__garage-assistant__scroll, mcp__garage-assistant__get_window_info, mcp__garage-assistant__wait when_to_use: When the user wants to interact with Garage Assistant 4, GA4, FileMaker, the garage software, vehicle records, repair orders, customer records, parts, invoicing, or anything related to the auto shop management system running in Parallels/Windows

Garage Assistant 4 — Computer Control

You can see and control Garage Assistant 4 (a FileMaker-based auto shop management system running in Parallels on Windows). Follow these rules carefully.

Core Workflow

  1. Always screenshot first — before any action, take a screenshot to see the current state
  2. Identify coordinates — look at the screenshot to find buttons, fields, tabs, menus
  3. Click precisely — use the coordinates you identified (relative to the VM window)
  4. Wait after actions — FileMaker can be slow. Wait 500-2000ms after navigation
  5. Screenshot to verify — after every action, take another screenshot to confirm it worked

Coordinate System

  • Screenshots are captured directly from the VM at 1200 × ~820 pixels
  • Coordinates for clicking correspond to pixel positions in the screenshot image
  • (0, 0) = top-left corner of the screenshot, (1200, 820) = bottom-right
  • The coordinate mapping is automatic — just click where you see things in the screenshot
  • Screenshots work even if other Mac windows are covering Parallels

FileMaker-Specific Tips

  • Navigation: FileMaker uses a tab/layout-based UI. Look for navigation bars, tabs, or sidebar menus
  • Fields: Click directly on a field to focus it, then use type_text. If the field has existing text, use ctrl+a to select all first, then type to replace
  • Records: Use arrow buttons or navigation controls (usually at top/bottom) to move between records
  • Portals: Scrollable lists within a layout — scroll inside them with the scroll tool
  • Dropdown fields: Click the field, wait for the dropdown to appear, then click the option
  • Date fields: Click, select all (ctrl+a), type the date in the expected format
  • Find mode: FileMaker uses ctrl+f to enter Find mode, then Enter to perform the find
  • Save: Records usually auto-save on navigation, but ctrl+s works too

Keyboard Shortcuts (Windows/Parallels)

  • ctrl+n — New record
  • ctrl+f — Find mode
  • ctrl+d — Duplicate record
  • ctrl+s — Save / Commit record
  • ctrl+z — Undo
  • ctrl+p — Print
  • tab — Next field
  • shift+tab — Previous field
  • escape — Cancel / Exit current mode
  • return or enter — Confirm / Execute find

Safety Rules

  • Never delete records unless the user explicitly asks and confirms
  • Always verify you're on the correct record before modifying data
  • Take a screenshot before and after any data modification to create an audit trail
  • If something looks wrong or unexpected, stop and ask the user before proceeding

Common Tasks

Looking up a vehicle/customer

  1. Screenshot to see current state
  2. Navigate to the appropriate layout (Customers, Vehicles, etc.)
  3. Enter Find mode (ctrl+f)
  4. Type search criteria in the relevant field
  5. Press Enter to perform the find
  6. Screenshot to show results

Creating a repair order

  1. Navigate to the Work Orders / Repair Orders layout
  2. Create new record (ctrl+n or click New button)
  3. Fill in fields: customer, vehicle, date, description
  4. Tab between fields
  5. Screenshot to verify

Entering parts/line items

  1. Navigate to the line items area (usually a portal at the bottom of an RO)
  2. Click in the first empty row
  3. Enter part number, description, quantity, price
  4. Tab to move between columns

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/garage-assistant-4-computer-control-mrwakasw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/garage-assistant-4-computer-control-mrwakasw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/garage-assistant-4-computer-control-mrwakasw/download' --output '.skill-downloads/garage-assistant-4-computer-control-mrwakasw/SKILL.md.part' && mv '.skill-downloads/garage-assistant-4-computer-control-mrwakasw/SKILL.md.part' '.skill-downloads/garage-assistant-4-computer-control-mrwakasw/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): mcp__garage-assistant__screenshot, mcp__garage-assistant__click, mcp__garage-assistant__double_click, mcp__garage-assistant__right_click, mcp__garage-assistant__type_text, mcp__garage-assistant__press_key, mcp__garage-assistant__scroll, mcp__garage-assistant__get_window_info, mcp__garage-assistant__wait

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/garage-assistant-4-computer-control-mrwakasw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills