save-artifact
SkillDocs & knowledgeSave or move durable outputs (reports, slide decks, HTML, summaries, code snippets, logs) under artifacts/ for the dashboard Artifacts tab. Use when the user asks to save, move, or keep something as an artifact beyond the chat session.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the save-artifact skill
What this skill tells your AI
The instructions your AI receives, as published by ahmadrosid/nakama in packages/core/src/skills/bundled/save-artifact/SKILL.md and read by ahel’s review.
Use this skill to save durable deliverables the user may revisit later.
- Use
artifacts/{filename}paths relative to the profile workspace (e.g.artifacts/report.md). - Do not save soul files (
SOUL.md,STYLE.md,INSTRUCTIONS.md),MEMORY.md, or knowledge-base uploads here — those have their own locations and workflows. - This workflow is text-only. Images, PDFs, and other binary files are not supported here.
When to use
- Reports, summaries, generated code snippets, logs, or structured notes the user asked to keep
- Outputs they may download or review later in the profile Artifacts tab
Workflow
- Choose a short, descriptive filename with the correct extension under
artifacts/(use subdirectories when grouping related files, e.g.artifacts/weekly/report.md). write_filethe artifact content toartifacts/{filename}. If that name already exists, a date suffix is added automatically (e.g.report-2026-07-14.md).- Confirm the saved path returned by the tool. On web chat, saved artifacts also appear as attachment chips on the assistant message (with preview) in addition to the profile Artifacts tab.
Save only the deliverable; Nakama derives the file type, size, and timestamp automatically.
Signals
- GitHub stars
- 372
- Forks
- 66
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
save-artifact- Source
- github.com/ahmadrosid/nakama