agentleFS
Sign inStart free
databricks-industry-solutionsdatabricks-industry-solutions/hls-skills/skills/presentation-builder/SKILL.md

presentation-builder

Skill6 starsChanged 19 days agoLicence not identifiedView on GitHub

Presentation builder that turns a finished HLS artifact — a cohort, de-identified dataset, model, measure catalog, or analysis in Unity Catalog — into a polished, shareable, self-contained HTML deck. Triggers on "make a deck/slides", "present this", "share this out", "turn this cohort/model/analysis into a presentation". Renders onto a frozen 1920x1080 framework (keyboard/click nav, Save-as-PDF, Databricks branding) so every deck looks identical. GROUNDS every figure in the real artifact via scripts/ground.py (counts, distributions, numeric summaries, each cited to source) and never types a number by hand. Delegates PHI handling to the phi-deidentifier skill: de-identify the source first and build from its governed view; if it is not available, asks whether to include or exclude PHI. Run the vetted entrypoints in scripts/build_deck.py and scripts/ground.py — do not hand-write deck HTML. For building the cohort use cohort-builder; to de-identify first use phi-deidentifier.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 12 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.

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