skill
Adom Wiki Skill Pack
Public Made by Adomby 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
← Commit history
wiki-bloat case study 2: the undelete loophole (2026-08-02) - an AI resurrected a soft-deleted standalone page to hold a skill that ALREADY shipped in the adom/adom core pack, dodging the hero gate and every create-time checkpoint; records the three failures and the rule that a soft-delete is a STOP sign with a reason behind it
2 files changed
+27−2
package.json+2−2@@ -1,7 +1,7 @@ { "slug": "adom-wiki-skillpack", "title": "Adom Wiki Skill Pack",- "version": "0.8.0",+ "version": "0.8.1", "type": "skill", "hero": { "path": "screenshots/hero.png"@@ -118,4 +118,4 @@ } ], "discovery_pitch": "Anything touching wiki.adom.inc: publishing, page archetypes, readmes, heroes, discovery, and the wiki-bloat rule (find where a thing already lives before creating any page)."-}+}
skills/wiki-bloat/SKILL.md+25@@ -60,6 +60,31 @@ And the counter-example, same day: a skill about wiki-bloat itself was requested home named ("add it to the wiki skillpack"). The right execution was exactly rule 1: fetch the pack, add one SKILL.md, extend the three list files, republish. Zero new pages. +## Case study 2 (real, 2026-08-02): the UNDELETE loophole++An AI was told to make a screen-takeover etiquette guide "an adom/core skill so all adom users+future ai threads know about this technique." Correct reading: add/extend a skill in the CORE PACK+(adom/adom). What the AI did instead: searched for a standalone page, found the slug existed but+was soft-deleted (it had already been cleaned up as bloat), ran `page undelete`, and pushed content+into the resurrected page. Founder: "oh my god. you created wiki bloat."++Three compounding failures, each independently avoidable:++1. **The content already had a home.** `adom/adom` ALREADY SHIPPED `skills/foreground-etiquette` -+ a ten-second pack-repo listing would have shown it. Rule 1 of this skill, not followed.+2. **"Make it a core skill" was read as "mint a page."** When a human names the pack ("adom/core",+ "the main skill pack all users get"), the task is the rule-1 mechanical sequence inside THAT+ pack. It is never a new slug.+3. **`page undelete` is a bloat backdoor.** A soft-deleted page is very often a page someone+ ALREADY JUDGED to be bloat. Resurrecting it dodges every creation checkpoint: the create-time+ conflict, the hero-in-front-of-a-human gate, the new-page lint. Treat an existing soft-delete as+ a STOP sign with a reason behind it: find out WHY it was deleted before even considering+ undelete, and never undelete just because your content needs somewhere to land.++(Tooling gap, filed the same day: the CLI reprimands on shared-identity publishes and placeholder+changelogs, but `page create` and `page undelete` ask no bloat question at all. Until they do, this+skill IS the gate.)+ ## Checklist before any POST /pages or new slug - [ ] Did a human actually ask for a NEW PAGE, or did they ask for the CONTENT? (Content