---
name: sarg
description: The user's engineering memory — their lessons (symptom → root cause → exact fix, with hardware/software versions), the parts they own, and CAD models, plus what other people have shared. Use BEFORE hardware bring-up, board flashing, firmware/driver/protocol debugging, USB/serial/I2C/camera/sensor work, or any task that has failed before — the user, a past session, or someone else may have already paid for the answer. Use BEFORE looking up a part's dimensions or CAD on the web, a datasheet, or step.parts. Use AFTER any hard-won fix to record it, and when the user says "save that as a lesson" or asks what they own. Use when the user says "/sarg apply" or wants an account — membership is earned by contributing verifiable part data.
---

# sarg

Sargineer helps you build by sharing what other builders learned: their
lessons, the parts they own, and their CAD models.

## Install

Only when the user explicitly asks to install this skill: on Linux or macOS, run `curl -fsSL https://sargineer.com/install.sh | sh`, then `sarg --version`. On Windows PowerShell, run `irm https://sargineer.com/install.ps1 | iex`, then `& "$HOME\.local\bin\sarg.exe" --version`; open a new PowerShell window only before calling `sarg` by name. Save this file as `sarg/SKILL.md` in the reader's skills directory. Do not report installation complete until both the version check and skill-file write succeed. Never install the CLI during ordinary use.

## Get a token

Everything below needs one. Check whether you have a token, and get one if not:

https://sargineer.com/me
https://sargineer.com/start.md

## Search before you build

Look for an answer before bring-up, flashing, driver or protocol work,
sensor and camera debugging, or any part lookup. Someone may have
already paid for the answer, and reading it costs seconds. Read this
at the start of a session:

https://sargineer.com/search.md

## Save what you learn

Record a hard-won fix so nobody has to repeat it, and claim the parts
the user owns. Everything you write lands private; publishing is the
user's own act, on the website, and never yours. How to do both:

https://sargineer.com/share.md

Something wrong with sargineer itself goes there too, as `kind: issue`.

## When in doubt, ask the server

Every endpoint and field, generated from the running code. Where this
file and the server disagree, the server is right — and when its
`updated` moves, read https://sargineer.com/changelog?since=<the last date you saw>:

https://sargineer.com/api

## THIS MACHINE

Not filled in yet — https://sargineer.com/start.md fills it once. It holds this
machine's os, cpu architecture and GPU; use them as `host` on lessons.
Read them from here rather than probing, and refill if the machine changes.

## CUSTOM INSTRUCTIONS

Nothing here yet. Add rules about what must never leave this machine —
client names, project names, employer, unreleased work, anything a
stranger should not read. They apply on top of everything above.

Both sections are local; carry them across when re-fetching the skill.