← ClaudeAtlas

verify-msp-skillslisted

Drive one msp-skills connector (skills/<slug>, any of the 84) the way a user does and prove it with evidence: install.sh, the <slug>-cli CLI, and the <slug>-mcp server over stdio and over HTTP, in an isolated HOME against a local fake vendor. Use to check a connector's user path before or after a reprint, to compare press versions across the fleet, or when a connector 'builds green' but nobody has watched it run.
Servosity/msp-skills · ★ 82 · AI & Automation · score 74
Install: claude install-skill Servosity/msp-skills
# verify-msp-skills Every connector in this repo is printed by cli-printing-press and shares one shape: a Go CLI `<slug>-cli` and an MCP server `<slug>-mcp` (stdio by default, `--transport http` optional) under `skills/<slug>/cli/`, installed by `skills/<slug>/install.sh`, configured by the env vars in `skills/<slug>/manifest.json`. So this is ONE skill, parameterized by slug. It drives the user path and records what happened. It does not repeat CI's gates; those stay with `tools/maintainer/verify_all.sh` (see Doctor). Read [features/README.md](features/README.md) before driving. It is the feature map: six features, each with the observable end state that proves it. ## Launch There is no long-lived app to start. One command does the whole cycle for a slug: build, install, drive, capture, clean up. ```bash python3 .claude/skills/verify-msp-skills/scripts/verify.py run --slug cipp ``` What it starts, in order, all owned by this run: 1. A scratch directory `$TMPDIR/verify-msp-<slug>-XXXX/` holding `home/` (the driven processes' HOME, with `XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME` inside it) and `build/`. 2. A fake vendor on `127.0.0.1:<ephemeral>` (in-process). Every base-URL and host variable from `manifest.json` points at it; every credential variable gets an inert stand-in value. It answers GET with `[]`, a JSON-RPC body with a JSON-RPC result, a token request with a stand-in token, a Synology DSM WebAPI call (a `/webapi/