From d931e9b81d8a0d417c154d50708f4a523b544537 Mon Sep 17 00:00:00 2001 From: Dannon Baker Date: Sun, 27 Sep 2026 17:31:32 -0400 Subject: [PATCH 1/3] export-hub: the hub page moved to /agents/plugins/ The Galaxy Hub moved its agent pages out of /tools/ into a top-level /agents/ section, so the plugin page now lives at /agents/plugins/ and Orbit at /agents/orbit/. Updates HUB_BASE, the Orbit link in the landing template, and the usage paths in the docstring and README. Rerunning the export against content/agents/plugins reproduces what's on the hub exactly. --- README.md | 6 +++--- scripts/export-hub.py | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index db05eda..5220b5c 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ scripts/ validate.py structural checks (run in CI) mcp_smoke.py starts galaxy-mcp over stdio and checks its tool list cursor-deeplink.py generates / checks the "Add to Cursor" link in docs - export-hub.py renders docs/ as Galaxy Hub pages (content/tools/ai-agents/) + export-hub.py renders docs/ as Galaxy Hub pages (content/agents/plugins/) .github/ ci-tools/ CI-only npm deps (Pi loader check); not part of the Pi package workflows/validate.yml per-harness CI jobs (see Testing) @@ -150,8 +150,8 @@ python3 scripts/validate.py # what CI runs Only `plugins/galaxy-mcp/`, `docs/` and the hand-written manifest fields are edited here; changes to skill content belong upstream. The Galaxy Hub pages -under `/tools/ai-agents/` are generated from `docs/` with -`scripts/export-hub.py /content/tools/ai-agents`; rerun it and +under `/agents/plugins/` are generated from `docs/` with +`scripts/export-hub.py /content/agents/plugins`; rerun it and open a hub pull request after changing a guide. A GitHub Action runs the sync every Monday and opens a pull request when anything changed. diff --git a/scripts/export-hub.py b/scripts/export-hub.py index 0bdbeba..eb2db15 100755 --- a/scripts/export-hub.py +++ b/scripts/export-hub.py @@ -1,14 +1,14 @@ #!/usr/bin/env python3 -"""Export docs/ as the Galaxy Hub page /tools/ai-agents/ (galaxyproject/galaxy-hub). +"""Export docs/ as the Galaxy Hub page /agents/plugins/ (galaxyproject/galaxy-hub). -Usage: scripts/export-hub.py /tools/ai-agents +Usage: scripts/export-hub.py /agents/plugins Writes ONE page, index.md, that combines: - the landing template below (hero + animated shells via ), - docs/galaxy-api-key.md as the "Get a Galaxy API key" section, - every harness doc as a panel inside , plus a redirect stub for each old per-harness URL (/index.md -> -/tools/ai-agents/#guide-) so existing links keep working. +/agents/plugins/#guide-) so existing links keep working. The docs remain the source of truth; rerun after editing them. Links between docs become in-page anchors, repo-relative links become GitHub URLs, each H1 is @@ -29,7 +29,7 @@ ROOT = Path(__file__).resolve().parent.parent DOCS = ROOT / "docs" REPO_URL = "https://github.com/galaxyproject/agentic-plugins" -HUB_BASE = "/tools/ai-agents" +HUB_BASE = "/agents/plugins" API_KEY_DOC = "galaxy-api-key.md" API_KEY_ANCHOR = "#get-a-galaxy-api-key" @@ -71,7 +71,7 @@
Looking for a complete AI research assistant built around Galaxy rather than a -plugin for the agent you already use? See Orbit. +plugin for the agent you already use? See Orbit.
## Before you start From 5a0cc1825d2fd98d966c31793f96f82777812dd7 Mon Sep 17 00:00:00 2001 From: Dannon Baker Date: Sun, 27 Sep 2026 18:58:04 -0400 Subject: [PATCH 2/3] export-hub: stop writing redirect stubs The stubs redirected the old per-harness hub URLs into the single page, but those URLs only existed briefly before the hub moved the page to /agents/plugins/, so every stub now points from a URL nobody ever used. Drops REDIRECTS and HUB_BASE (only the stubs used it); the export is just index.md. --- scripts/export-hub.py | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/scripts/export-hub.py b/scripts/export-hub.py index eb2db15..ffd51a3 100755 --- a/scripts/export-hub.py +++ b/scripts/export-hub.py @@ -6,9 +6,7 @@ Writes ONE page, index.md, that combines: - the landing template below (hero + animated shells via ), - docs/galaxy-api-key.md as the "Get a Galaxy API key" section, - - every harness doc as a panel inside , -plus a redirect stub for each old per-harness URL (/index.md -> -/agents/plugins/#guide-) so existing links keep working. + - every harness doc as a panel inside . The docs remain the source of truth; rerun after editing them. Links between docs become in-page anchors, repo-relative links become GitHub URLs, each H1 is @@ -29,7 +27,6 @@ ROOT = Path(__file__).resolve().parent.parent DOCS = ROOT / "docs" REPO_URL = "https://github.com/galaxyproject/agentic-plugins" -HUB_BASE = "/agents/plugins" API_KEY_DOC = "galaxy-api-key.md" API_KEY_ANCHOR = "#get-a-galaxy-api-key" @@ -44,9 +41,6 @@ # ("cursor.md", "cursor", "Cursor"), ] -# Old per-page slugs that now redirect into the single page. -REDIRECTS = {"api-key": API_KEY_ANCHOR, **{gid: f"#guide-{gid}" for _, gid, _ in GUIDES}} - LANDING = f"""--- title: "Galaxy for AI Coding Agents" tease: "Connect Claude Code, Codex, Antigravity or Pi to your Galaxy server with curated Galaxy skills, or add the Galaxy MCP server to Claude Desktop as a one-click bundle." @@ -170,11 +164,6 @@ def main() -> int: out.mkdir(parents=True, exist_ok=True) (out / "index.md").write_text(landing()) print(f"wrote {out / 'index.md'}") - for slug, anchor in REDIRECTS.items(): - page = out / slug - page.mkdir(exist_ok=True) - (page / "index.md").write_text(f'---\nredirect: "{HUB_BASE}/{anchor}"\n---\n') - print(f"wrote {page / 'index.md'} -> {HUB_BASE}/{anchor}") return 0 From c755b2a3230cd013247e2363297c3c331d0cf441 Mon Sep 17 00:00:00 2001 From: Dannon Baker Date: Sun, 27 Sep 2026 20:50:48 -0400 Subject: [PATCH 3/3] Wrap the hub page sections in the hub's band layout The hub is restyling its agent pages to share one look: full-width alternating bands under the hero. This wraps the generated sections in those ag-band divs and drops the intro paragraph and Orbit callout, which the new hero already covers, so the next export matches what's on the hub. --- scripts/export-hub.py | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/scripts/export-hub.py b/scripts/export-hub.py index ffd51a3..7e1fb28 100755 --- a/scripts/export-hub.py +++ b/scripts/export-hub.py @@ -4,7 +4,8 @@ Usage: scripts/export-hub.py /agents/plugins Writes ONE page, index.md, that combines: - - the landing template below (hero + animated shells via ), + - the landing template below (hero + animated shells via , + then the sections in the hub's full-width ag-band wrappers), - docs/galaxy-api-key.md as the "Get a Galaxy API key" section, - every harness doc as a panel inside . @@ -55,18 +56,7 @@ -Galaxy for AI coding agents installs the galaxy-mcp server, the galaxy-skills -and galaxy-dev-skills sets and the Workflow Foundry skills into Claude Code, -Codex, Antigravity or Pi; Claude Desktop gets the galaxy-mcp server as a -one-click bundle. Everything comes from the -[galaxyproject/agentic-plugins]({REPO_URL}) -repository, and everything you need is on this page: get an API key, then pick -your harness under [Set up your agent](#set-up-your-agent). - -
-Looking for a complete AI research assistant built around Galaxy rather than a -plugin for the agent you already use? See Orbit. -
+
## Before you start @@ -98,6 +88,10 @@ +
+ +
+ ## What the agent can do once connected Ask in plain language; the agent picks the Galaxy tools: @@ -117,6 +111,8 @@ - Skill content lives upstream in [galaxy-skills](https://github.com/galaxyproject/galaxy-skills) and [foundry](https://github.com/galaxyproject/foundry); the plugins mirror them weekly. + +
"""