# Publish Artifact > Publish a self-contained HTML artifact or page to a self-hosted static site with a project make publish-artifact target, then return its public URL. - Skill: `xakki/publish-artifact` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add xakki/publish-artifact` - Raw SKILL.md: https://api.skillmd.com/api/skills/xakki/publish-artifact/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: Xakki (https://skillmd.com/u/xakki) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/xakki/publish-artifact --- # publish-artifact Copies a complete/standalone HTML file into the configured project's artifact directory; that project's nginx serves it at `/artifact//`. No docker build/deploy involved — plain file copy, picked up immediately by an already-live static/alias location. ## Config Read from `~/.config/artifact-publish/.env` (chmod 600, not in any repo): ``` ARTIFACT_PROJECT_DIR=/path/to/project # the project whose Makefile has `publish-artifact` ``` ## Happy path (the one command) ```bash source ~/.config/artifact-publish/.env make -C "$ARTIFACT_PROJECT_DIR" publish-artifact ART= [SLUG=] ``` Capture the **last stdout line** — that's the public URL. Return it to the user. (Everything else the target/script prints goes to stderr, so the last stdout line is always exactly the URL.) ## Note on fragments vs. complete docs The target auto-wraps a headless Artifact-tool fragment (no ``/``/``) into a full HTML5 document (charset, viewport, title). A file that already contains `