Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bitjaru/ss-update
Update StyleSeed engine in your project — analyzes what's outdated and updates safely
Passed 16 of 19 test cases with the skill, and 7 of 19 without it.
and 11 more in the full report
11 fixed7 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
After re-resolving context files with resolve-context.mjs, we see updated files in .styleseed/. Do we need to run any check flags before concluding Step 5?
| Checked | Without skill | With skill |
|---|---|---|
| Executes resolve-context.mjs with the --check flag. | Passed | Passed |
| Requires an exit status of 0 from the check command. | Missed | Passed |
The instructions your model reads when the skill loads.
When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact-id>.md and .styleseed/manifests/<artifact-id>.json. Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective-rules.md only when no registry exists.
Update the engine payload, not the user's product UI. A release version describes a published
line; engineRevision identifies the exact maintained rules, skills, entry docs, and palette
engine. Two installs with the same release version are not proven equal until their revisions
match.
The checker verifies the payload for the active install channel. A repository/plugin checkout
uses the full core inventory; a project-local Agent Skills install uses the executable skills
inventory. The published endpoint must expose both the engine revision and, for a skills-only
install, skillsRevision. The project manifest continues to record the engine revision that
compiled its method bundle.
/ss-setup or $ss-setup./ss-build, /ss-page, or /ss-component.StyleSeed owns installed ss-* skill payloads and compiled .styleseed/effective-rules.md.
The project owns STYLESEED.md, application code, components, tokens, assets, and any existing
AGENTS.md, CLAUDE.md, or Cursor instructions. Never overwrite project-owned files merely to
update StyleSeed.
An update may change design-method behavior, especially across major versions. It is reversible through the user's version control, but it is not correct to promise that every update is additive or non-breaking.
From the user's project root, run the bundled checker by its installed path:
node <installed-ss-update>/scripts/check-update.mjs --project-root . --json
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.