Artifacts
Artifacts are the files generated by a skill run. They are separated from skill source, run logs, and local preferences.
Folder contract
.skills/
exports/
<skill>/
<run-id>/
manifest.json
receipt.json
generated-files...
runs/
<run-id>/
metadata.json
logs.jsonl
pins/
cache/
Manifest fields
| Field | Purpose |
|---|---|
runId | Stable id for the execution. |
skill | Registry skill name, without skill-. |
createdAt | Completion timestamp. |
inputs | Sanitized prompt and input metadata. |
artifacts | Relative paths, media types, and descriptions. |
receipt | User-visible price and billing result for paid work. |
Download behavior
Worker writes private storage
Remote workers upload artifacts to private storage and record checksums.
API issues controlled downloads
The API signs or proxies artifact reads only for the owning organization.
CLI materializes exports
The CLI writes files under .skills/exports/<skill>/<run-id>/ and stores local run metadata separately.
Common artifact sets
| Skill | Typical outputs |
|---|---|
logo-design | SVG, PNG, usage notes, manifest, receipt. |
pdf-to-markdown | Markdown, extracted images, tables, manifest. |
blog-article | Article markdown, SEO metadata, outline, manifest. |
landing-page-pack | Copy, wireframe, preview HTML, style guide, experiment plan. |
email-sequence | Sequence markdown, per-email HTML, subject lines, CTA variants. |