Skip to the rows

agentsclimarketplace

Openspec archive change

Skill TheSmuks/openspec-hermes/skills/openspec/openspec-archive-change

Use when working with OpenSpec in Hermes: archive one completed change, optionally syncing specs first.From its SKILL.md

Install

npx -y skills add TheSmuks/openspec-hermes --skill openspec-archive-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 376 tokens by cl100k_base, as published. Nobody here has run it

openspec-archive-change

Use this for OpenSpec's /opsx:archive workflow.

Hermes operating rules for OpenSpec

Work from the user's project root. If unknown, inspect the current directory first.
Ensure the OpenSpec CLI exists before using it: openspec --version. If missing, install with npm install -g @fission-ai/openspec@latest.
Initialize projects with openspec init --tools none unless the user also wants other AI-tool integrations. Hermes uses these skills, not OpenSpec-generated slash commands.
Prefer agent-compatible OpenSpec CLI calls with --json where available: openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate --all --json.
Read generated artifacts before editing or implementing. Do not invent OpenSpec state.
Run validation after changing OpenSpec artifacts: openspec validate <change> or openspec validate --all.
Keep changes focused. If user scope diverges, update the existing change only when intent is the same; otherwise create a new change.

Procedure

Identify the change.
Run openspec status --change <name> --json and inspect task completion.
Run openspec validate <name> unless explicitly skipped.
Prefer openspec archive <name> --yes so the CLI performs official merge and archive flow.
Use --skip-specs only for changes that genuinely do not alter specs.
Verify archived folder exists at openspec/changes/archive/YYYY-MM-DD-<name>/.
Run openspec validate --all after archiving.
Report archive path and validation result.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Read off the repository

Stars: 0
License: MIT

Last push to any branch: 48 days ago
We read these numbers: never
Most recent individual check: never

Filed under

Considered, nothing fired

Shipped alongside

Openspec apply change
15 owners ship both, 9 of them independently written
Openspec explore
15 owners ship both, 9 of them independently written
Openspec propose
12 owners ship both, 7 of them independently written
Openspec sync specs
7 owners ship both, each independently written
Openspec new change
4 owners ship both, each independently written
Openspec onboard
4 owners ship both, each independently written

Also from this repository

Not in a stack

Nobody has picked this yet, which is also why it sits where it does in the catalog ordering. It is a statement about our shelves rather than about the software.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.