--- name: Use Artifacts slug: use-artifacts category: Automation description: Use Artifacts teaches when to publish work as a shareable HTML or Markdown artifact, and how to update it as a task progresses. It also covers the deferred tool flow for creating and revising artifacts. github: "https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/use-artifacts" language: Rust stars: 163 forks: 30 install: "npx degit https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/use-artifacts ~/.claude/skills/use-artifacts" installs_to: ~/.claude/skills/use-artifacts source_path: peri-middlewares/src/skills/builtin/skills/use-artifacts/SKILL.md collection_size: 20 category_size: 2226 collection_url: "https://dirskills.com/collections/KonghaYao/peri" added: 2026-09-08T05:35:47.816Z last_synced: 2026-09-08T05:35:47.816Z canonical_url: "https://dirskills.com/skills/use-artifacts" --- # Use Artifacts Use Artifacts teaches when to publish work as a shareable HTML or Markdown artifact, and how to update it as a task progresses. It also covers the deferred tool flow for creating and revising artifacts. **Install:** ```bash npx degit https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/use-artifacts ~/.claude/skills/use-artifacts ``` ## README # Using Artifacts Artifacts are public HTML pages you upload to a hosting service. They have stable URLs that you can share with the user or open in a browser. Use them to surface work-in-progress, summaries, and reports. ## When to use artifacts **Good artifact content:** - Progress panels / kanbans (task list with status) - Research reports and analysis (data + findings + recommendations) - Design docs / decision records (with context and rationale) - Data visualizations (tables, SVG charts, flow diagrams) - Final deliverables (the "thing the user asked for" rendered as HTML) **Do NOT use artifacts for:** - Code snippets — use files directly - One-line answers — keep them in chat - Internal debug logs — keep them in chat - Large data dumps — link to source files instead ## Cadence — when to upload - **Task start**: if the task is complex (multi-step, research, deliverable), upload a skeleton artifact first as scaffolding (placeholder sections). - **Milestones**: when you complete a phase (research done / implementation done / tests pass), update the artifact. - **User asks**: upload immediately. - **Task end**: ship the final artifact as the deliverable. **Do NOT upload:** - After every tool call (noise) - Mid-step with no meaningful change (e.g. fixed a typo) ## How to invoke (deferred tool) `artifact` is a deferred tool. The first call requires two steps; subsequent calls one step. **First upload (creates a new artifact):** ``` 1. Use the Write tool to write HTML (.html) or Markdown (.md) to a local file (location is your choice). 2. SearchExtraTools({ query: "select:artifact" }) // loads the tool schema 3. ExecuteExtraTool({ tool_name: "artifact", params: { file_path: ".html|.md" } }) 4. Save the returned `id` from the tool result — this is the hash. ``` **Subsequent updates (overwrites in place, URL stays stable):** ``` 1. Update the local file. 2. ExecuteExtraTool({ tool_name: "artifact", params: { file_path: ".html|.md", hash: "" } }) ``` The URL returned on every call is the same when you pass the same `hash`. The user can open it at any time to see the latest version. ## Choosing HTML vs Markdown - **Markdown (.md)** — preferred for text-heavy reports, design docs, research notes. The tool converts it to a styled HTML page (GFM tables, fenced code blocks, blockquotes, headings). You write content, not chrome. - **HTML (.html)** — preferred when you need bespoke layout, custom CSS, embedded SVG, or interactive `