agentsclimarketplace

Knowledge to slides

Skill erain/knowledge-publishing-skills/skills/knowledge-to-slides

Portable coding-agent skills for publishing HTML knowledge artifacts

Install
npx -y skills add erain/knowledge-publishing-skills --skill knowledge-to-slides

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

Turn what was learned from a coding session, repository, PR, incident, experiment, or technical conversation into a polished self-contained HTML slide deck with rich visuals, SVG diagrams, responsive layout, keyboard navigation, and local validation before publishing.

SKILL.md

2.3 KB, 453 tokens by cl100k_base, as published. Nobody here has run it

Knowledge To Slides

Create one complete HTML file that can be published as a static artifact. This skill is agent-neutral: follow the workflow from any coding agent that can read files, edit HTML/CSS/SVG, and run the bundled validation script.

Workflow

  1. Extract the story:
    • problem or question
    • constraints
    • system shape
    • key decisions
    • implementation details
    • sharp edges or failures
    • takeaways
  2. Build a 6-10 slide narrative. Prefer fewer dense slides over many shallow ones.
  3. Use assets/deck-template.html as the structural baseline when useful.
  4. Make visuals directly in HTML/CSS/SVG. Avoid external CDNs and localhost assets.
  5. Save the deck as index.html.
  6. Run scripts/validate_deck.py index.html from this skill directory, or pass the full path to the generated deck.
  7. Use browser validation when available:
    • desktop 1280x720
    • mobile around 390x844
    • at least one non-title slide
  8. If publishing is requested, use the publish-html-artifact skill after validation.

Deck Requirements

  • Single self-contained HTML file.
  • No remote JavaScript dependencies.
  • No localhost, file://, or absolute local paths.
  • 16:9 desktop-first slide composition with responsive mobile behavior.
  • Keyboard navigation with arrow keys.
  • Print stylesheet or acceptable browser print behavior.
  • Rich media must be inline SVG, CSS diagrams, or embedded data assets.
  • Display text must not overflow or overlap at desktop/mobile validation sizes.

Output Contract

  • Return the generated file path.
  • Summarize the story arc and any important validation notes.
  • If publishing is requested, hand the validated HTML path to publish-html-artifact.

Style Defaults

  • Professional, technical, slightly geeky.
  • Dense enough for engineers, clear enough for quick sharing.
  • Prefer system diagrams, terminal panels, timelines, matrices, and architecture maps.
  • Keep cards at 8px border radius or less.
  • Avoid decorative blobs, one-note palettes, and unnecessary animation.

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.