Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rome-os/app-lifecycle
Install, reinstall, uninstall, enable, or disable Rome apps, including deployment after app edits and the first-party build and restart procedure.
Passed 20 of 22 test cases with the skill, and 7 of 22 without it.
and 18 more in the full report
13 fixed7 passed either way2 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
During boot startup, if Rome discovers that an installed lockfile entry has a non-system failure, will it crash the entire startup process or mark the entry and continue?
| Checked | Without skill | With skill |
|---|---|---|
| States that non-system failures are marked broken. | Passed | Passed |
| Explains that catalog events are replayed to load remaining runtime items. | Missed | Passed |
The instructions your model reads when the skill loads.
Read system:app_management with read_action before calling it through execute_action. For new app scaffolding, also read coding:app_creation.
An app can reach three separate states. Each one is a different decision. Do not treat one as another.
| Endpoint | Who can use it | How |
|---|---|---|
| Installed | Only the guardian, in this Rome dashboard | install (below) |
| Shared | Other people, through this Rome's public URL. A hosted Rome needs no extra hosting or domain. A desktop or local Rome may have no public URL. | Change the app's access mode. Read SHARING.md. |
| In the App Store | Anyone, who installs a copy into their own Rome | Publish a version. Read PUBLISHING.md. |
Installing does not share or publish. Sharing and publishing are visible outside this Rome, so do them only when the guardian asks for that app and that endpoint. When you describe how to release an app, name the endpoint first. Rome has no Apple App Store or Google Play path. Say that instead of improvising one.
Use this path for a custom app under ~/.rome/<profile>/projects/apps/<id>/ or another standalone checkout outside the Rome monorepo.
Call system:app_management with the app repository as the source:
{
"op": "install",
"source": { "mode": "source", "path": "<absolute app repo path>" }
}
Pass the same source object on every reinstall after edits. The daemon rebuilds and repacks each time.
After the call succeeds, validate the app immediately. Do not poll deployment files or the active symlink.
The daemon derives the app ID from app.yaml, runs the workspace's build, and packs it into <repo>/.rome/artifact. It installs the bundle and awaits the runtime reload before returning. The guardian can also use Install/Upgrade on the Apps dashboard.
The bundle source mode accepts an already-packed artifact, not a raw source workspace. A raw workspace fails with "not a packed artifact".
If an install error carries a native-build hint or ERR_PNPM_IGNORED_BUILDS, follow the hint and system:custom-dependencies.
For a Rome App Store install, discover the listing with system:app_store_search and follow the appstore source schema in system:app_management.
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.