LobeHub Interactive Prototype
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
A skill your agent uses 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…
$ npx skills add solo-agent/solo --skill solo-artifacts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install solo-agent/solo solo-artifacts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/solo-artifacts .claude/skills/solo-artifacts && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .claude/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/solo-agent/solo/tree/master/skills/solo-artifactsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add solo-agent/solo --skill solo-artifacts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install solo-agent/solo solo-artifacts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/solo-artifacts .agents/skills/solo-artifacts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .agents/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add solo-agent/solo --skill solo-artifacts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install solo-agent/solo solo-artifacts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/solo-artifacts .cursor/skills/solo-artifacts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .cursor/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/solo-agent/solo.git --path skills/solo-artifacts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add solo-agent/solo --skill solo-artifacts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install solo-agent/solo solo-artifacts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/solo-artifacts .gemini/skills/solo-artifacts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .gemini/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install solo-agent/solo solo-artifactsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add solo-agent/solo --skill solo-artifacts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/solo-artifacts .github/skills/solo-artifacts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .github/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add solo-agent/solo --skill solo-artifacts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install solo-agent/solo solo-artifacts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/solo-agent/solo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/solo-artifacts .opencode/skills/solo-artifacts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "solo-artifacts" agent skill from https://github.com/solo-agent/solo/tree/master/skills/solo-artifacts into .opencode/skills/solo-artifacts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solo-artifacts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
solo-artifactsA skill your agent uses 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 Artifacts is an agent skill from solo-agent/solo. 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.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `assets/interactions.js`, `references/comparison.md` and `references/progress-report.md`).
It sits in Frontend & Design, covering HTML artifacts. The repository describes itself as: Solo Agent — an open-source, local-first workspace where humans and AI coding agents collaborate through channels, tasks, teams, and persistent memory. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9d58e66. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (JavaScript), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Solo Artifacts loads about 961 tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from solo-agent/solo at commit 9d58e66, republished under its MIT licence (© solo-agent). 456 words, ~961 tokens.
.claude/skills/solo-artifacts/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.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.htmlYou 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.Embed everything: inline CSS/JS, embed media as data: URIs, no CDN or external requests.
Publish back to Solo:
solo artifact publish --task <task-id> --mode <latest|final> --file <path-to-html>assets/starter.html — the skeleton to copy.assets/base.css — class-compatible Solo Warm Archive design system.assets/interactions.js — optional vanilla-JS modules: print, tabs, tables, lightbox, copy, scrollspy, persist.references/*.md — work-canvas section order, component recipes, and guardrails.© solo-agent, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files (references, assets) in skills/solo-artifacts of solo-agent/solo.
Open the folder on GitHubat commit 9d58e66
Solo Artifacts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Solo Artifacts this skillsolo-agent/solo | 697 | — | ~961 | Automated safety check: Pass | MIT | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Paperclip Pagepaperclipai/paperclip | 99k | — | ~1k | Automated safety check: Pass | MIT | |
| Openkb Deck NeonVectifyAI/OpenKB | 4.7k | 1 repos | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Webhome Homepage Builderwebhtv/webhtv | 1.7k | — | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| Paper2htmlQuZhan51496/paper2anything | 468 | — | ~3.3k | Automated safety check: Notes | Apache-2.0 |
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
VectifyAI/OpenKB
A skill your agent uses when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow /…
webhtv/webhtv
Build, review, debug, reverse-engineer data sources for, and package FongMi/WebHome custom homepage single-file HTML.
QuZhan51496/paper2anything
Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.
plannotator/effective-html
Create or redesign self-contained single-file HTML artifacts with a visual direction shaped by the user's brief, project, and subject.
Categories
A skill your agent uses 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 Artifacts is an agent skill from solo-agent/solo. 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.
Solo Artifacts fits situations like: thread should become an interactive; self-contained HTML artifact for progress/status; review/decision; comparison/leaderboard work inside Solo.
Run `npx skills add solo-agent/solo --skill solo-artifacts -a claude-code`. Or copy the skill folder (skills/solo-artifacts in solo-agent/solo) into .claude/skills/solo-artifacts in your project. Claude Code loads it when a task matches its description.
Run `npx skills add solo-agent/solo --skill solo-artifacts -a codex`. Or copy the skill folder (skills/solo-artifacts in solo-agent/solo) into .agents/skills/solo-artifacts in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add solo-agent/solo --skill solo-artifacts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/solo-artifacts, .gemini/skills/solo-artifacts, .github/skills/solo-artifacts and .opencode/skills/solo-artifacts in your project.
Going by SKILL.md and its folder, Solo Artifacts needs JavaScript for the scripts in its folder. Our summary lists: Node.js.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Solo Artifacts is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 961 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Solo Artifacts: LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Paperclip Page (paperclipai/paperclip, 99k stars), Openkb Deck Neon (VectifyAI/OpenKB, 4.7k stars) and Webhome Homepage Builder (webhtv/webhtv, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
solo-agent (a GitHub organization) maintains it in solo-agent/solo, which has 697 GitHub stars. The repository was last updated on September 13, 2026.
Source: solo-agent/solo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.