agentleFS
Sign inStart free
pedrobarrettopedrobarretto/skills/skills/html-communication/SKILL.md

html-communication

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user asks to communicate through an HTML document.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 2

    1. connorch/skills★ 238% same
    2. Melv1C/skills★ 143% same

    Wrote their own version · 2

    1. ShlomiPorush/agent-skills★ 2same name
    2. Solly922/html-communication★ 0same 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 repository4 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 12

    Distinctive

    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:

    Use this skill when the user wants a plan, spec, write-up, findings, summary, report, comparison, or set of UI mocks presented as readable …

    line 15
  2. Distinctive:

    Do not use it for HTML that ships as part of a product.

    line 18
  3. Distinctive:

    Create one self-contained HTML file, capped at 512 KB.

    line 22
  4. Distinctive:

    Write it like a spec, not a landing page: dense, scannable, no hero, decorative chrome, marketing voice, or em dashes.

    line 24
  5. Distinctive:

    Before 18:00 in the user's local time, use a white or off-white background, near-black primary text, and light gray only for secondary …

    line 26
  6. Distinctive:

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

    line 32
  7. Distinctive:

    Use an inline classic script only when interactivity materially helps.

    line 33
  8. Very specific:

    Never include external or module scripts, inline event handlers, javascript: URLs, forms, frames, embeds, objects, applets, meta refresh, …

    line 39
  9. Distinctive:

    When the user asks for variants:

    line 45
  10. Distinctive:

    Keep one file across iterations so its Postplan URL stays stable.

    line 50
  11. Distinctive:

    Write the HTML file locally.

    line 58
  12. Very specific:

    If validation fails, fix the markup and retry.

    line 65
  13. Distinctive:

    Never open a browser or claim the document is hosted before upload succeeds.

    line 69
  14. Distinctive:

    Do not verify in a browser unless the user asks.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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 Communication

When to Use

Use this skill when the user wants a plan, spec, write-up, findings, summary, report, comparison, or set of UI mocks presented as readable HTML.

Do not use it for HTML that ships as part of a product.

Document

Create one self-contained HTML file, capped at 512 KB.

  • Write it like a spec, not a landing page: dense, scannable, no hero, decorative chrome, marketing voice, or em dashes.
  • Before 18:00 in the user's local time, use a white or off-white background, near-black primary text, and light gray only for secondary surfaces or accents. At 18:00 or later, use true black (#000), white primary text, and dark gray only for secondary surfaces or accents. If the user's timezone is unknown, use the system's local time.
  • Make it mobile-readable with a responsive viewport and no fixed-width layout.
  • Use semantic HTML, inline CSS, inline SVG, and HTTPS or data-URL images.
  • Use an inline classic script only when interactivity materially helps. Keep scripted pages useful without JavaScript; the sandbox blocks storage, fetch, workers, frames, forms, and popups.
  • In script-free files, give external links target="_blank" and rel="noopener noreferrer". If any script exists, omit target="_blank".

Never include external or module scripts, inline event handlers, javascript: URLs, forms, frames, embeds, objects, applets, meta refresh, linked stylesheets, secrets, private URLs, or local filesystem paths.

UI Mocks

When the user asks for variants:

  • Render real styled variants, not descriptions.
  • Label them A, B, C... for easy selection.
  • Lay them out for direct comparison.
  • Keep one file across iterations so its Postplan URL stays stable.

Publish

Pedro has given standing permission to upload every artifact created or updated with this skill. Upload is required, including in Auto mode. Do not ask for separate permission or stop at the local file.

  1. Write the HTML file locally.
  2. Run npx postplan upload <file path>.
  3. Report the local path and returned Postplan URL.

Re-upload the same absolute path to update the existing URL. Use npx postplan upload <file path> --new only when a new draft is wanted.

If validation fails, fix the markup and retry. If a scripted upload needs authentication, ask the user to run postplan auth login, then retry without removing the requested interactivity.

Never open a browser or claim the document is hosted before upload succeeds. Do not verify in a browser unless the user asks.

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