agentsclimarketplace

Publish html artifact

Skill erain/knowledge-publishing-skills/skills/publish-html-artifact

Portable coding-agent skills for publishing HTML knowledge artifacts

Install
npx -y skills add erain/knowledge-publishing-skills --skill publish-html-artifact

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Publish a completed static HTML page or slide deck into the erain/knowledge-pages hosting repository, supporting public and unlisted visibility, updating artifact metadata, running the site build, committing, pushing, and returning the final URL.

SKILL.md

1.9 KB, 384 tokens by cl100k_base, as published. Nobody here has run it

Publish HTML Artifact

Use this skill after an HTML artifact has been created and validated. This skill is agent-neutral: any coding agent with shell access, Git, and a checked-out hosting repository can follow it.

Inputs To Determine

  • source HTML path
  • title
  • slug
  • kind: deck or page
  • visibility: public or unlisted
  • summary
  • tags
  • target repo path, default /home/ubuntu/src/knowledge-pages
  • base URL, default https://knowledge.11tech.xyz

Workflow

  1. Confirm the source file exists and is a complete HTML document.
  2. Run any artifact-specific validator first, such as knowledge-to-slides/scripts/validate_deck.py.
  3. Run scripts/publish.py from this skill with explicit args. Use --repo and --base-url when the defaults do not match the environment.
  4. Inspect the diff in the hosting repo.
  5. Commit and push the hosting repo changes.
  6. Wait for deployment when possible.
  7. Return the published URL and commit URL.

Visibility Semantics

  • public: copies to content/public/decks/<slug>/index.html or content/public/pages/<slug>/index.html, appears in the gallery.
  • unlisted: copies to content/unlisted/<slug-or-token>/index.html, deploys under /u/<slug-or-token>/, does not appear in the gallery. This is not security; anyone with the URL can view it.

For private previews, use a future Vercel/Cloudflare integration instead of treating unlisted URLs as secrets.

Output Contract

  • Return the final URL.
  • Include the hosting repository commit hash or commit URL when available.
  • State whether the artifact was published as public or unlisted.

Gives 0 of the 12 instructions most slides presentations skills give in 384 tokens

Counted across 568 of the 571 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 52 of 568, across 21 files
  • put one idea per slidein 50 of 568, across 42 files
  • state the design approach before writing codein 38 of 568, across 8 files
  • validate XML immediately after each editin 37 of 568, across 7 files
  • rasterize gradients and icons as PNG images before referencing themin 37 of 568, across 7 files
  • generate and inspect thumbnails to validate layoutin 37 of 568, across 7 files
  • commit to a single visual motif across every slidein 37 of 568, across 12 files
  • use web-safe fonts onlyin 36 of 568, across 7 files
  • keep 0.5 inch minimum marginsin 35 of 568, across 9 files
  • use two-column layout for slides with charts or tablesin 34 of 568, across 5 files
  • save a template inventory analysis to a filein 33 of 568, across 4 files
  • use subagents to visually inspect rendered slidesin 33 of 568, across 9 files

Said here and by no other author read

  • confirm source file is a complete HTML document
  • run any artifact-specific validator first
  • run the publish script with explicit args
  • use repo and base-url args when defaults mismatch
  • inspect the diff in the hosting repo
  • commit and push the hosting repo changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.