← ClaudeAtlas

syncrolisted

Use when the user asks to list or triage Syncro tickets, find logged-but-unbilled time, check AR aging, see which assets are missing patches, rank RMM alert noise, pull a cross-entity customer profile, or run any Syncro PSA or RMM workflow. Wraps the Syncro API plus an offline SQLite mirror with cross-customer search and billing-leakage analytics. Trigger phrases: `list syncro tickets`, `show uninvoiced time in syncro`, `syncro ar aging`, `which syncro assets are missing patches`, `triage stale syncro tickets`, `Syncro + ChatGPT`, `Syncro + Claude`, `use syncro`, `run syncro-cli`.
Servosity/msp-skills · ★ 3 · AI & Automation · score 65
Install: claude install-skill Servosity/msp-skills
# Syncro Claude Code Skill ## Prerequisites: Install the CLI This skill drives the `syncro-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. macOS / Linux: ```bash bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/syncro/install.sh) ``` 2. Windows (PowerShell): ```powershell iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/syncro/install.ps1 | iex ``` 3. Verify: `syncro-cli --version` 4. Ensure `~/.local/bin` (macOS / Linux) or `%LOCALAPPDATA%\Programs\msp-skills` (Windows) is on `$PATH`. If `--version` reports "command not found" after install, the install step did not put the binary on `$PATH`. Do not proceed with skill commands until verification succeeds. syncro-cli mirrors your Syncro tenant into a local SQLite store so tickets, customers, assets, invoices, and RMM alerts become joinable, searchable, and fast. On top of full API coverage it adds reports Syncro never rendered: uninvoiced time, invoice drift, AR aging, customer profitability, SLA aging triage, and fleet-wide patch gaps. Built for agents with --json, --select, --dry-run, typed exit codes, and adaptive backoff for Syncro's 180-requests-per-minute limit. The cross-entity reports read the local store, so run `sync` first; some (uninvoiced, drift, margin, patch-gaps, aging) also need sub-resources like timer entries, patches, and comments t