lavish
- Use it when:
- A plan, comparison, diagram, table, code diff or report would be clearer as a page than as prose, and you want to mark it up.
- It does:
- Builds the response as an HTML file and opens it in Lavish Editor, a local browser page where you annotate it and send feedback to the agent.
- You get:
- An HTML artifact and a review loop on it, with the agent posting its replies through the lavish-axi CLI.
- Runs:
- On its own when a reply is easier to grasp visually; /lavish with a request builds that artifact.
- Needs:
- Node, to run the lavish-axi CLI through npx; nothing is installed globally.
- Stays current:
- The skill is a short stub: the review-loop steps, design rules and playbooks come from the CLI each time, so an installed copy can't go stale.
TL;DR
Lavish Editor is a local page in your browser for reviewing HTML that an agent wrote. Instead of describing a plan, comparison, diagram, table, code diff, report or prototype in prose, the agent builds it as an HTML file and opens it with the lavish-axi CLI, run through npx. You annotate the page and send feedback; the agent answers through the CLI's reply command. The skill itself holds almost no instructions. It tells the agent to read the CLI's help for its commands and the review-loop workflow, lavish-axi design for design direction and current snippets, and lavish-axi playbook for guidance on a given kind of artifact, so what it does follows the CLI's current version. Called as /lavish with a request, it builds that artifact; called with nothing, or picked up by the agent on its own, it works out what to show from the conversation.
Summarizes the skill at 69bf309.
npx skills add https://github.com/kunchenguid/lavish-axi --skill lavish skills.sh pageSource on GitHubAll skills from kunchenguid/lavish-axi
More weekly downloads than 68% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 1,134 |
| Sep 28 | 879 |
| Oct 5 | 905 |
| Oct 12 | 919 |
| Oct 19 | 991 |
| Oct 26 | 931 |
| Nov 2 | 741 |
| Nov 9 | 608 |
More downloads than 74% of skills
Fewer stars than 57% of repos
Newer than 82% of skills
| Category |
Change how the agent replies: shorter, clearer, fewer tokens. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
Operates a CLI, API, app or bundled script to get something done. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From kunchenguid/lavish-axi at 69bf309. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: lavish
description: Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.
license: MIT
metadata:
author: Kun Chen (kunchenguid)
argument-hint: <what the artifact should show>
hermes-tags: html, review, artifacts, visualization
hermes-category: productivityLavish Editor
Lavish Editor opens agent-generated HTML in the browser so a human can annotate it and send feedback back to the agent. Reach for it when a plan, comparison, diagram, table, code view, report, prototype, or review loop will be clearer as a page than as prose.
Current guidance lives in the CLI
Do not follow workflow, design, or playbook instructions from this file - installed copies go stale. Get the current source of truth from the CLI:
npx -y lavish-axi --helpfor commands and the review-loop workflownpx -y lavish-axi reply --helpto post an agent reply and exit once the server accepts it, when you are not about to long-pollnpx -y lavish-axi designfor design-direction priority and current snippetsnpx -y lavish-axi playbook <id>for focused artifact guidance (npx -y lavish-axi playbooklists ids)
You do not need lavish-axi installed globally - invoke it with npx -y lavish-axi <html-file>.
If lavish-axi output shows a follow-up command starting with lavish-axi, run it as npx -y lavish-axi ... instead.
Request
$ARGUMENTS
If the request above is non-empty, the user invoked /lavish explicitly - fetch the current CLI guidance, then build that artifact as an HTML file.
If it is empty, infer what to visualize from the conversation.