update SKILL.md skillA

update from lukaskellerstein/claude-my-marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add lukaskellerstein/claude-my-marketplace/update@git:20261107.629412d

Pins git:20261107.629412d in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

lukaskellerstein/claude-my-marketplace

Path

plugins/spex/skills/update/SKILL.md

Versions recorded

1

Latest version

git:20261107.629412d, committed Nov 7, 2026

Size

2,532 bytes

Repository stars

3

License

none declared

After a spex plugin update, bring the repo to the plugin's format — run spex update, which adds the keys the newer plugin needs with their defaults and comments, runs the format migrations (1 → 2 moves every record's verification and every task's verify commands into a tests.yaml per folder) and sets format, keeping every value and comment of yours — then have a test-analyst subagent complete each migrated proof plan, and show what changed. Use when the user says "spex update…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# spex update

`SPEX` = `node ${CLAUDE_PLUGIN_ROOT}/scripts/spex.mjs`, from the repo root.

## Steps

1. `SPEX update`. It changes `.spex/config.yaml`: the keys a newer plugin introduced, with
   their defaults and comments; the `format` line; and, when `format` is behind, the spec
   folders too. Every value and comment of yours stays. If it refuses, relay the finding and
   stop: no config yet means `/spex:init`; a repo newer than the plugin means the plugin
   must be updated first.
2. Format 1 → 2 writes a `tests.yaml` per folder from what was there: one script test per
   scenario, found in its file by name when the test exists, and one shell test per task
   that had `verify` commands. It is a start, not a plan. For every folder whose records
   are not all `built` or `retired`, say `Complete the plan → 1 test analyst` and start one
   `spex:test-analyst` with `<dir>. Complete tests.yaml: every claim spex show --plan
   lists, a name per script, a session where no script can judge.` Then `SPEX check <dir>`;
   a `TEST-*` error goes back to a fresh test analyst with the findings, once.
3. `SPEX check`. Fix nothing else yourself. Relay errors by their `fix` text. A new default
…

Read the whole file at its exact version.

How to install

mdr add lukaskellerstein/claude-my-marketplace/update@sha256:215d508f848f6c42

[![mdr](https://markdownregistry.com/badge/art_5cjwb67drfepf3rt.svg)](https://markdownregistry.com/a/art_5cjwb67drfepf3rt)

Versions

The registry has recorded 1 version of this file, committed on Nov 7, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_5cjwb67drfepf3rt
GET https://markdownregistry.com/api/v1/resolve?ref=lukaskellerstein/claude-my-marketplace/update
GET https://markdownregistry.com/api/v1/blob/215d508f848f6c42c471d95461de3ba9a44366cbcb54c7fe9026ac0e70f897ea

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from lukaskellerstein/claude-my-marketplace

Every file in lukaskellerstein/claude-my-marketplace

Other files named update

Browse by kind, by grade A, or by owner.