agentleFS
Sign inStart free
aurokinaurokin/skills-manager/skills/html-artifact/SKILL.md

html-artifact

Skill3 starsChanged 6 months agoMITView on GitHub

Create or update a self-contained HTML artifact for a plan, spec, report, findings, summary, comparison, or set of UI mock variants. Use when the user asks to communicate through an HTML document or artifact, or mentions HTML without a product implementation context. Do not use for HTML that ships as part of a product.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. BrainInBox/brain-in-a-box★ 16same name
    2. masaki69/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create one self-contained HTML file for communication and review, not product code.

    line 8
  2. Distinctive:

    Write it like a spec, not a landing page.

    line 12
  3. Distinctive:

    Keep visuals information-dense.

    line 14
  4. Very specific:

    Default to true black (#000), white primary text, and dark gray for secondary surfaces or accents.

    line 15
  5. Distinctive:

    Use semantic HTML, inline CSS, inline SVG, and data-URL images.

    line 17
  6. Distinctive:

    Only add feedback controls when the user explicitly asks to collect responses inside the artifact.

    line 21
  7. Distinctive:

    Place each input beside the section it refers to.

    line 25
  8. Distinctive:

    Keep feedback in memory only.

    line 26
  9. Distinctive:

    When the user asks for UI variants:

    line 32
  10. Distinctive:

    Keep one file across iterations.

    line 37
  11. Very specific:

    Write the HTML to the requested path.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HTML Artifact

Create one self-contained HTML file for communication and review, not product code. Use the material already in the conversation or the documents the user provides.

Build the document

  • Write it like a spec, not a landing page. Make it dense and scannable. Avoid heroes, decorative chrome, marketing copy, and em dashes.
  • Visualize information when it can make the material easier to understand or more compelling. Choose the form that best fits the content.
  • Keep visuals information-dense. Do not invent data or add visuals merely to decorate the page.
  • Default to true black (#000), white primary text, and dark gray for secondary surfaces or accents.
  • Make it mobile-readable with a responsive viewport and no fixed-width layout.
  • Use semantic HTML, inline CSS, inline SVG, and data-URL images. Use HTTPS images only when embedding them is impractical and the source is safe to disclose.

Receiving Feedback

Only add feedback controls when the user explicitly asks to collect responses inside the artifact. Otherwise, keep the artifact read-only.

When requested:

  • Place each input beside the section it refers to.
  • Keep feedback in memory only. Do not persist or transmit it.
  • Provide separate controls to copy all feedback and export it, with a selectable-text fallback when clipboard access is unavailable.
  • For a small amount of feedback, use lightweight inline controls rather than building a larger feedback system.

Render variants directly

When the user asks for UI variants:

  • Render real styled variants instead of describing them.
  • Label them A, B, C, and so on for easy selection.
  • Lay them out for direct comparison.
  • Keep one file across iterations.

Validate and deliver

  1. Write the HTML to the requested path. If none is given, choose a descriptive .html filename in a .tmp subfolder within the working directory.
  2. Report the local path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free