stromy-org/databricks
Plugin for Databricks branded deliverables
Author ONE chart spec (bar, column, line, area, scatter, pie, doughnut, combo with a secondary axis, waterfall) and get a native, editable chart in brand colours inside a PowerPoint deck (build_pptx) or Excel workbook (build_xlsx). For HTML or PDF pages, and for exotic types (sankey, sunburst, treemap, funnel, gauge, heatmap), render a branded picture with render_chart from a Plotly figure instead. Use for any chart, plot, graph or KPI visual. Not for process flows, org charts or stakeholder maps (use format-diagram).
Draw process flows, architecture views, stakeholder maps, org charts, timelines, matrices, mind maps and sequence/state/ER/gantt diagrams from Mermaid text. Two modes: BRANDED (the server-side render_diagram tool returns an auto-laid-out, brand-themed SVG/PNG for PPTX, DOCX, PDF or deck deliverables) and MARKDOWN (plain fenced Mermaid for a README, wiki or any Markdown host that renders it). Use when asked to draw, map or visualize a process, structure, workflow or relationship. Not for numeric data charts (use format-chart).
DEFAULT skill for ANY Word or .docx request, branded or not: a memo, report, letter, brief or proposal; a document on the client's own template or letterhead; a table of contents, headers, footers and page numbers; editing an existing .docx in place with tracked changes, comments, find-and-replace, accept or reject; reading or extracting its text. Builds native, editable Word files server-side with build_docx (python-docx) and edits them with edit_docx, with a structural lint (styles, heading order, alt text, table fit, numbering, TOC) and a render-back of the finished file. Use format-docx-hd only when the user wants an art-directed, web-style layout authored as HTML. Not for PDFs (format-pdf), spreadsheets (format-xlsx) or Google Docs.
The ART-DIRECTED option for Word: a .docx authored as HTML and server-rendered by render_docx (Chromium parses the HTML, an OOXML layout lint and a LibreOffice render-back run inside the render). Use only when the user wants a web-style, designed layout that Word's own styles cannot express (bespoke motifs, magazine-style pages) and accepts a lossy HTML conversion. It ignores the client's Word template and has no TOC field. Triggers on: 'art-directed Word doc', 'designed .docx', 'HD docx', 'magazine-style Word document'. For a standard memo, report, letter or brief, a client template, a table of contents, or ANY edit, tracked change or comment, use format-docx (the default Word route).
Product guide for producing documents, decks, and other deliverables — what to ask for, which format to pick, how the skills hand off to each other, and where finished work lands. Use whenever someone asks "how do I make a document/deck/PDF", "how do I create a proposal/presentation", "which format should I use", or any orientation question specifically about producing a deliverable. For first-time install, switching on connectors, or a general "how do I get started", the getting-started skill is the entry point. Routes to the right renderer; does not render anything itself.
Author a premium branded HTML slide deck as ONE self-contained .html that opens offline, with the client's fonts and logos embedded: hand-written (16:9 stages, scroll-snap navigation, inline-SVG brand motifs) or in reveal mode, a reveal.js deck rendered by render_deck with a speaker view and speaker notes. Seeded variance keeps decks siblings, not clones. Use for an HTML, web or browser slide deck, a shareable single-file presentation, a reveal.js deck or web deck with speaker notes, an interactive presentation, or turning a brief or report into branded slides, even without saying 'HTML'. Not for an editable PowerPoint (use format-pptx) or a paginated PDF (use format-pdf-hd).
Use when asked to translate a deliverable, add a language version, check whether a translation is current, find out what changed since the last translation, or work out why a copy still has source-language text in it. Maintain a deliverable that exists in several languages without the versions drifting apart: reports which translation units are missing, stale, current, or obsolete; returns only what must be translated; validates a translated batch against protected tokens, placeholders, URLs, figures, and terminology; and hands back a replacement target state to persist. Works on structured translation units a producer supplies, not a raw file. Not for translating a finished Word, PowerPoint or PDF file in place (use that format's skill).
Use when someone wants animation in a deck or site: an animated reveal or transition, a line that draws itself, a counting KPI, a baked clip from web animation, advice on how much movement a deck should have, or a surface that feels alive without becoming gimmicky. Authors tasteful, brand-aware motion primitives (staggered reveal, line-draw, count-up, motion-path, scroll-reveal, element morph) under a restraint doctrine. Two modes: embed-live (inline a primitive into a deck or site) and bake (turn a self-contained HTML animation into MP4/GIF/PNG via render_motion, for PowerPoint or PDF). Brand-optional (not bake). Not for a narrated or voiced explainer video (format-video-hd), numeric data-viz (format-chart), or structural diagrams (format-diagram).
Work with PDFs: extract text and tables, merge or split documents, fill in fillable forms, and make a simple unbranded PDF from data or plain text. Use when a PDF form needs filling, or a PDF must be read, searched, split, merged, analysed or generated programmatically. Not for a branded or client-facing PDF deliverable: use format-pdf-hd, which designs HTML first and renders it behind a brand gate.
Create a high-fidelity branded PDF (proposal, executive brief, brand book, policy report, case study, white paper or one-pager), designed HTML-first with CSS, web fonts, SVG and paged media, and server-rendered by render_pdf behind a brand gate from the plugin's brand overlay. Use when someone asks for a branded, high-quality, HD or magazine-style PDF, or any visually polished client-facing paginated output. Not for filling forms, extracting text, merging or splitting PDFs, or a plain unbranded PDF (use format-pdf), nor for structuring a multi-section document with no agreed outline yet (start with format-prepare-document).
DEFAULT skill for ANY PowerPoint or .pptx request, branded or not: a new deck, a deck on the client's own template, editing or reviewing an existing deck, speaker notes, comments, reordering, adding slides. Builds native, editable slides server-side with build_pptx (python-pptx) on the client's template or a master synthesised from their brand, runs a fit lint (no overlapping or overflowing text) and a render-back of the finished file. Use format-pptx-hd only when the user wants web-style art direction authored as HTML.
HTML-crafted option for a new branded PowerPoint (.pptx): slides authored as HTML with bespoke art direction, converted and server-rendered by render_pptx behind a brand gate, with speaker notes, a fit lint and a render-back of the produced file. Use ONLY when the user wants web-style art direction in a .pptx (or render-anchors); every ordinary PowerPoint request, branded or not, including a client's own template and editing an existing deck, belongs to format-pptx (native, python-pptx). Not for a browser or offline HTML deck (use format-html-hd, which also covers a reveal deck with speaker notes) or a paginated print PDF (use format-pdf-hd).
Plan a multi-section document before rendering it: section plan, brand-aware structure, complementary charts and diagrams, sign-off, then handoff to the right format-* renderer. Use when someone asks for a proposal, pitch, report, white paper, executive brief or board deck and the structure is not yet decided, or says 'help me plan or outline the document'. Not for a one-page memo, a single slide, an edit of an existing file, or when an approved section plan or envelope already exists: go straight to format-pdf-hd, format-pptx, format-docx-hd or format-html-hd. Branding comes from the invoking plugin's brand overlay.
Author a premium branded explainer VIDEO — a server-rendered MP4 with animated titles, kinetic typography, animated process-flow diagrams, animated data (bars, KPI count-ups), image reveals, captions, and optional voiceover or music. Storyboard-first and accuracy-gated: a scene-by-scene shot list with citations, then a brand-gated render with a per-scene visual review. Brand-required. Use when someone wants a video, explainer, motion-graphics video, or a brief, plan, or report turned into a branded video — even without saying 'video'. Content stays accurate, never fabricated. Not for an HTML-to-MP4 deck/PDF clip (format-motion), generative AI footage (video-production), or an editable branded deck (format-pptx-hd).
DEFAULT skill for ANY spreadsheet request (.xlsx, .xlsm, .csv, .tsv): build a new workbook, a budget or model with inputs, calculations and outputs, a data table, an analysis of an existing file, or an edit that must keep the formulas. A new workbook is built server-side with build_xlsx (openpyxl): real formulas, Excel Tables, brand theme and named styles, a lint for errors and ##### after a LibreOffice recalculation, and a render-back of the finished file. Not for a Word document (format-docx), a deck (format-pptx) or a picture chart for a document (format-chart).
Day-0 setup and orientation for a Stromy plugin — install it, switch on the connectors it needs, confirm it worked, and find which guide answers your question. Use whenever someone is new, asks how to get started, how to install or set up the plugin, what they have available, or hits one of the two common snags: skills that look out of date after an update, or a tool that reads "Connected" but will not run in the chat. This skill ships inside the plugin and needs no connector, so it is the one that still answers when nothing else is switched on.