菜单
Use when finished work must be shown to the user—or when they ask to see/display a visual—artifact_present for files, inline markdown with remote image URLs, terminal preview, email or Telegram delivery.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when shell commands fail, npx/curl/git won't run, or you must choose run_shell vs web_fetch vs file tools in Nodebox vs host.
Use when the user says remember this, save a preference or API key, or you must pick memory_save vs session notes vs skill (action=manage) vs wiki_* tools.
Use when the input is an image, screenshot, diagram, PDF/DOCX, audio file, or YouTube link—extract metadata/text before reasoning.
Use when the user wants to discover, search, or install agent skills from online registries—top results by installs, stars, or votes. Or user sends /find_skills.
Use when calling REST or GraphQL APIs with web_fetch/web_post — auth headers, query params, GraphQL shape, Directus GraphQL mutations/relations, discovery order, and reading error bodies.
Use when the user or agent installs a skill from skills.sh or GitHub — map WebFetch, Bash, Python, Playwright, and MCP references to Web Agent built-ins.
| name | Artifact Delivery |
| description | Use when finished work must be shown to the user—or when they ask to see/display a visual—artifact_present for files, inline markdown with remote image URLs, terminal preview, email or Telegram delivery. |
| version | 1.1.0 |
| category | bundled |
| primary-tools | ["artifact_present","email"] |
| tags | ["artifact","delivery","presentation","email","telegram","output","image","thumbnail","secrets","redact"] |
| triggers | ["show me","show it","preview","display","thumbnail","image url","deliver","send via telegram","send email","attach","share result","package output","final output","redact","api key in report"] |
Ad-hoc delivery in a single turn — not scheduled jobs (see heartbeat-cron).
| Need | Tool |
|---|---|
| Persist deliverable file | write_file under projects/ or work/ — see project-scaffold |
| Show file / open View popup | artifact_present with title + path |
| ZIP bundle deliverable | run_python + zipfile → .zip under work/ or projects/, then artifact_present — see browser-runtime-map (no create_archive tool) |
| Inline markdown or remote image | artifact_present with markdown (e.g. ) |
| Email a result | email with subject + body — redact secrets first |
| Mermaid SVG in View popup | ```mermaid fence + artifact_present — see chart |
| Telegram (ad-hoc) | Configured channel side-effect; cron jobs use notifyChannel in heartbeat-cron |
Non-negotiable: User asked to show/see/display → call artifact_present same turn once ready. Never paste the full artifact body in chat after present. Never echo sk-…, bearer tokens, or .env contents in delivery surfaces.
Owns choice between inline reply, artifact_present, email, and cron delivery mode. Scheduled-job delivery semantics stay in heartbeat-cron.
task-execution writes work/task-execution/<slug>/report.md.chart. Durable facts (including credentials the user asked to store): memory-layers.write_file under projects/<slug>/ (durable) or work/<slug>/ (scratch).artifact_present with title and path or markdown.subject; redact secrets before send.create_archive tool. Stage files, zip with run_python + stdlib zipfile, write to work/<slug>/name.zip, verify with archive_list, present with artifact_present..env contents from artifact_present bodies and email text.artifact_present.read_file followed by inline paste when artifact_present is available.projects/ or work/..txt when the user asked for a zip — use run_python + zipfile instead.