Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tutti-os/tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow.
Passed 20 of 22 test cases with the skill, and 6 of 22 without it.
and 22 more in the full report
14 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are creating the source tutti.app.json manifest file for 'code-editor'. What exact schemaVersion string must be specified in the source and packaged manifest files, and what schemaVersion is used for catalog.json?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies schemaVersion tutti.app.manifest.v1 for source and package manifests | Missed | Passed |
| Explains that catalog.json uses schemaVersion tutti.app.catalog.v1 | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when an external app repository publishes a remote Tutti workspace app into App Center release metadata.
The external repository calls the reusable workflow from the Tutti/Tutti repository:
uses: tutti-os/tutti/.github/workflows/publish-tutti-app-release.yml@main
That workflow builds one app package, runs @tutti-os/app-release-tools, uploads immutable release files plus mutable latest.json and versions.json, and can optionally merge that app into the shared catalog.json.
Inspect before acting:
tutti.app.json, package script, and recent GitHub Actions runs.For catalog publication:
publish_catalog: false. This uploads a new app version and updates apps/<appId>/latest.json and versions.json; App Center will see it the next time catalog.json is published.publish_catalog: true. This uploads the app release, then immediately merges that release into catalog.json.catalog_only: true. Use this after a release already succeeded when the user forgot to publish catalog, wants to validate first, or wants to refresh catalog without bumping or uploading a new version.catalog_only, use that. If it does not, use the Tutti catalog workflow directly or add the caller input when the user wants that repo to support catalog-only dispatch.For versioning:
release_bump (patch, minor, or major); the reusable workflow calculates the next version from the greater of the packaged manifest version and existing release tags, then creates the tag after the S3 release verifies.release_bump empty. The workflow uses manifest.version+<short git sha> from the packaged manifest and does not create a release tag.For reusable workflow changes:
min_tutti_version explicitly. Use 0.0.0 only for releases that are safe for every legacy Tutti client.test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.