| name | tower-artifact |
| description | Open the tower's artifact picker to link an existing artifact into this session. Invoke as /artifact. |
| version | 1.0.0 |
/artifact
Call the Tower MCP tool open_picker(kind:"artifact"). This asks the tower UI to open the link-artifact picker for the current session; the human picks. Do nothing else.
Authoring HTML artifacts (co-location rule — §4b)
When you (or the html-over-md skill) write a multi-file HTML artifact, co-locate every
referenced asset inside the same artifact slug dir ($TOWER_ARTIFACTS_DIR/<slug>/):
the entry index.html and the style.css / images / fonts it links must all live under
that one dir, and asset refs should be relative (href="style.css",
src="assets/x.png") — not root-absolute (/style.css). Promotion moves the whole dir
into the first-class store, so any sibling/nested file the entry references then serves
from /api/artifacts/file/<id>/... and resolves in the preview iframe. (As a safety net
the server injects a <base href="/api/artifacts/file/<id>/"> and rewrites leading-slash
local refs into the artifact dir, but co-located relative refs are the right authoring
shape and never need rewriting.)