artifact-server

# Artifact Server Use one skill for Artifact Server work. Route the request before loading detailed instructions. ## Route the request - For publishing, updating, opening, sharing, commenting, tagging, comparing, restoring an artifact version, or managing projects, read [artifact operations](references/artifact-operations.md). Read [target selection](references/target-selection.md) when the server or project is not already exact. - For an explicit request to install, deploy, upgrade, reconfigure, back up, restore, inspect, repair, or delete an Artifact Server installation, read [server operations](references/server-operations.md). Do not load or follow administrator instructions for routine artifact work. - Read [failures and compatibility](references/failures-and-compatibility.md) only after a failure, incompatibility, authentication problem, or ambiguous target. If a request includes both artifact work and server administration, keep the steps separate and state which installation is affected before changing it. ## Keep these boundaries - Use the installed `artifactserver` CLI for files on the user's machine. Use the connected Artifact Server MCP for work that needs only server data. - Never replace a real file with inline HTML, base64, invented bytes, or a local path sent to a remote MCP server. - Never read, print, request in chat, or write bearer tokens, API keys, cookies, or refresh tokens. - Keep public sharing off unless the user explicit...