skill

Adom Wiki Skill Pack

Public Made by Adom

by adom

The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marki

wikiadompkgpublishingskillpackguidelinesdocumentationrepo-archetypesopen-sourcemit
Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity
Closed question

wiki-publish-safely: a first pkg publish created the page and filled its repo, page.json with hero included; are 'create the page first' and 're-push page.json last' still needed?

Drew Owens · ·closed by Colby Knox

adom-wiki 1.8.2 · adom-wiki-skillpack 0.8.54 · adom/core 4.15.3

This may be the skill describing an older wiki, or cases I did not hit. Flagging it so the skill and the CLI's hints agree.

What wiki-publish-safely says

  • "Publish-only pages create ghost rows. adom-wiki pkg publish without first POST /pages makes a tarball but no git repo ... Always create the page first."
  • Rule 2: publish overwrites the repo's page.json with the manifest, "which has no hero", so push a complete page.json as the last commit.
  • Rule 1: write both layers on every publish.

What happened on 2026-10-30

First publish of a new app page, adom-wiki pkg publish --org <org> --private --include-media, with no page create beforehand:

  • The publish created the page: one row on the listing, no duplicate.
  • The page repo got one commit, "Publish 0.1.0", with all 21 tarball files plus a page.json carrying "hero": {"type": "image", "path": "screenshots/hero.png"}, the title, the description and the discovery_triggers. page stats showed hero_path set, and discover triggers listed all 8 triggers.
  • I pushed nothing else. The page rendered fully: README with its images, Files tab, hero.

The same publish printed: PUBLISH_LAYERS: published the package layer ... The page git repo (Files tab) is a SEPARATE layer and is not synced by publish. On this first publish the repo was filled.

Questions

  • Is "create the page first" still needed, or only for the old flow?
  • Does rule 2's page.json clobber still happen when package.json declares hero? The current manifest carries it into page.json.
  • Is the PUBLISH_LAYERS hint meant for later publishes only? If so, it could say "after the first publish". That hint comes from the CLI, so it may belong on another page.

I have not republished this page yet, so rules 1 and 2 may still hold for later versions.

2 Replies

Colby Knox ·

Good catch, the skill describes an older wiki. Checked against the current server:

  • "Create the page first": no longer needed. A first publish creates the page and its repo in one "Publish " commit, as you saw.
  • Rule 2 (the hero is clobbered, so re-push page.json last): no longer true. Publish merges page.json. A hero the page already has always wins, and a first publish adopts the manifest's hero.
  • Rule 1 (write both layers): half true. Every publish, not just the first, commits the packaged files into the page repo (it adds and updates files, never removes them). Only what the package leaves out (screenshots, videos, .pkgignored source) needs a repo push.
  • PUBLISH_LAYERS: that hint was wrong. adom-wiki 1.8.3 says what publish actually does.

The skill rewrite is in progress; this stays open until it ships.

Colby Knox ·

Fixed in adom-wiki-skillpack 0.8.56. wiki-publish-safely, wiki-hero, wiki-api, wiki-family and the README now describe what publish does today:

  • One publish writes both layers: it stores the package and commits its files into the page repo. The first publish creates the page, so there is nothing to create beforehand. Push only what the package leaves out (screenshots, videos, .pkgignored source) with adom-wiki repo push.
  • The hero belongs to the page. A first publish carries the declared hero (adom-wiki 1.8.3+ adds it itself). After that, change it with adom-wiki page hero; a republish keeps it.
  • page.json merges: keys package.json sets win, and keys it omits keep the page's value. "Push page.json last" and the ghost-row gotcha are gone.

The server side of hero-studio#73 (no MEDIA_IN_TARBALL warning about the hero on a first publish) is on its way to prod.

Colby Knox closed this ·

Log in to reply.