Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →solo-agent/solo-artifacts
Use when a Solo task or thread should become an interactive, reviewable, self-contained HTML artifact for progress/status, review/decision, or comparison/leaderboard work inside Solo.
Passed 2 of 12 test cases with the skill, and 2 of 12 without it.
and 2 more in the full report
4 fixed0 passed either way14 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Publish the final HTML deliverable `./reports/final.html` for task-3456 as the definitive task result.
| Checked | Without skill | With skill |
|---|---|---|
| The publication command specifies mode set to final. | Missed | Passed |
The instructions your model reads when the skill loads.
Warm Archive fork of work-canvas: produce or publish one self-contained HTML file that renders a Solo task/thread for a human to understand and act on. Prefer the real deliverable over a summary page.
Publish Existing Deliverable if the current task/run names one.
Trust only explicit current-task evidence, such as:
Deliverable: ./path/to/result.html
You may also use a file path named in the current task/thread, or a file you personally created for this task now. Do not scan the workspace by newest file, mtime, or vague filename match; old workspace files can be stale. If several files are named, prefer the product/final deliverable over review/report/panel files unless the user explicitly asks for the review page. Do not switch to review-decision just because the task is in_review.
Existing .html: publish it directly.
solo artifact publish --task <task-id> --mode <latest|final> --file <path-to-html>
Existing .md, .txt, .json, .csv, or other text/data: create a small self-contained HTML viewer that renders the exact source content, labels the source file near the top, then publish that wrapper. Do not summarize or rewrite the content.
Multiple deliverables or a directory: create a small index artifact with explicit links/file names and a short note about what each file is.
If a real deliverable exists, stop here.
Pick the artifact type and read its reference:
| The task needs to... | Type | Read |
|---|---|---|
| Show where long/messy work stands, what broke, what's next | Progress / status report | references/progress-report.md |
| Review analysis or implementation and decide accept/reject/next step | Review / decision memo | references/review-decision.md |
| Weigh options head-to-head and pick a winner | Comparison / leaderboard | references/comparison.md |
If blended, lead with the primary type and borrow blocks from the other.
Assemble from the template. Copy assets/starter.html, then:
[[PASTE base.css]] with the full contents of assets/base.css.[[PASTE interactions.js]] with only the needed modules from assets/interactions.js; pasting the whole file is fine because modules self-guard.test cases passed, vs 2 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.