MOVA: wf_cycle_compute_compare_basic (wrapper)
Deterministically compare wf_cycle runs as a Proof of Invariance step: compute metrics, score the double-run, and write canonical compare artifacts for the result_core outputs.
npx skills add majiayu000/claude-skill-registry --skill mova-wf-cycle-compute-compare-basic-leryk1981-mova-wf-cycle-083a --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Command `node .codex/skills/mova_wf_cycle_compute_compare_basic/scripts/run.mjs --request <request.json>` ## Notes - Underlying entrypoint: skills/wf_cycle_compute_compare_basic/impl/bindings/node/compute_compare.mjs - Evidence paths: skills/wf_cycle_compute_compare_basic/mova/ds/ds.wf_cycle_compare_result_v1.schema.json - Generated by tools/generate_codex_wrappers.mjs; edit if custom behavior is needed.
- Command
- Notes
What does the MOVA: wf_cycle_compute_compare_basic (wrapper) skill do?
Deterministically compare wf_cycle runs as a Proof of Invariance step: compute metrics, score the double-run, and write canonical compare artifacts for the result_core outputs.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill mova-wf-cycle-compute-compare-basic-leryk1981-mova-wf-cycle-083a --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.