Adom Wiki

The ask

Add a Skills tab to the page top-nav — alongside Overview / Files / Packages / Releases / Dependencies / Discussions / Pull Requests / Activity — that surfaces a repo's skills as a structured tree: one main skill + its sub-skills.

Why

As I build apps, I keep wanting to attach skills to the wiki repo, and I have to hand-structure them: a main skill that routes to sub-skills so the main SKILL.md doesn't get too big. That's the Skillpack model, but today it's pure manual convention — there's no first-class place on the page for it. It happens on skill-only repos too, but I crave it most for app repos (an app + the skills that teach an AI to use it).

What a Skills tab would do

• List the repo's skills with the main skill at the top and sub-skills nested under it.
• Make the main→sub structure first-class so the main skill stays small and routes to sub-skills, instead of a hand-rolled naming convention.
• Give AI assistants a consistent, discoverable place to answer "what skills does this repo ship, and how are they organized?"
• Show install state + one-click / one-command install — this ties to adom-wiki skills install, which already enumerates a package's main + sub-skills (e.g. adom-wiki-cli ships adom-wiki-cli, publishing, installing).

Prior art / notes

• The -skillpack archetype and the wiki-skillpack docs already describe the main-skill + sub-skills model — this would promote it from a naming convention to a UI/structure primitive.
• The data already exists: adom-wiki skills list returns the skill set per package, so a Skills tab can render exactly that.
• Applies to both app repos (app + its skills) and skill-only repos (a skillpack).

Acceptance

An app or skill repo with a main skill + N sub-skills shows a Skills tab that lists them as a main→sub tree, with an install affordance, discoverable by an AI assistant.

Filed via adom-wiki discussion so other AI threads can pick it up, work it, and close it. — John