$ welcome --to emblema-marketplace
Templates for Emblema Workspaces
// Discover pre-built workflows and building blocks.
// Use complete workspace solutions or individual nodes.
$ ls ./latest_workspace_templates
view all →export Presentazione PPTX dalla Libreria Layout
// Crea una presentazione PowerPoint sul master del cliente dai documenti di una cartella Drive (o da un singolo file). Il nodo Libreria Layout legge la libreria di layout che il curatore ha pubblicato con un nodo Brand Master; l'agente sceglie il layout di ogni slide dalla libreria, scrive i contenuti, e il PPTX Builder compila il master vero, con anteprime PNG; il PDF Builder ne fa anche un PDF da condividere o stampare. Se il workspace ha già il suo Brand Master, usa quello (modalità locale). Niente viene pubblicato fuori dal workspace. Builds a PowerPoint deck on the customer's own master from the documents in a Drive folder (or one file). The Layout Library node reads the layout library a curator published with a Brand Master node; the agent picks every slide's layout from that library, writes the content, and the PPTX Builder fills the real master, with PNG previews; the PDF Builder also turns it into a PDF to share or print. A workspace with its own Brand Master uses that one (local mode). Nothing is published outside the workspace.
export Libreria Layout del Brand
// Crea e gestisce la libreria di layout PowerPoint di un brand, anche partendo da zero. Senza un master: l'agente progetta i layout come slide (copertina, agenda, sezione, testo e immagine, elenco, tabella, numeri chiave, chiusura e altri) con i colori, i caratteri e il logo del brand, li trasforma in un master PowerPoint, lo salva nella cartella Drive scelta e lo pubblica come libreria con il nodo Brand Master. Con un master già pronto (.pptx o .potx in Drive) lo pubblica direttamente. Poi si curano i layout (nomi, descrizioni, attivi o no), se ne aggiungono o se ne cambiano i colori; le presentazioni si fanno in altri workspace con il template "Presentazione PPTX dalla Libreria Layout". Scrive solo il file del master nella cartella Drive scelta. Il controllo visivo dei layout richiede un modello con visione potente: funziona con Claude Opus 5.5, mentre Qwen 3.6 può dare per buoni layout illeggibili. Creates and manages a brand's PowerPoint layout library, from scratch if needed. Without a master, the agent designs the layouts as slides (cover, agenda, section, text and picture, bullets, table, key numbers, closing and more) in the brand's colours, fonts and logo, turns them into a PowerPoint master, saves it to the Drive folder you choose and publishes it as a library with the Brand Master node. With an existing master (a .pptx or .potx in Drive) it publishes that one. Then you curate the layouts (names, descriptions, on or off), add layouts or change the colours; decks are made in other workspaces with the "Presentazione PPTX dalla Libreria Layout" template. It writes only the master file, into the Drive folder you choose. The visual check of the layouts needs a strong vision model: it works on Claude Opus 5.5, while Qwen 3.6 can report unreadable layouts as fine.
export Traduzione PDF di una Cartella
// Traduce tutti i file di una cartella Drive in un'altra cartella e mantiene le sottocartelle: sorgente/a/b/c/d.pdf diventa destinazione/a/b/c/d.<lingua>.pdf e d.<lingua>.bilingual.pdf, con ogni pagina originale accanto alla sua traduzione. Ogni file conserva l'impaginazione e passa i controlli del Traduttore PDF (nessun testo lasciato non tradotto, nessun numero cambiato); Word, PowerPoint e testo vengono tradotti dal PDF che Drive ne ha fatto. Prima di tradurre l'agente mostra l'elenco dei file e chiede conferma, poi crea sul canvas una sezione per ogni file e li traduce tutti con un solo avvio, in parallelo: un file non riuscito ferma solo la sua sezione. Alla fine riporta l'esito di ogni file. Translates every file of a Drive folder into another folder and keeps the sub-folders: source/a/b/c/d.pdf becomes destination/a/b/c/d.<lang>.pdf and d.<lang>.bilingual.pdf, with each original page beside its translation. Each file keeps its layout and passes the PDF Translator's checks (no text left untranslated, no number changed); Word, PowerPoint and text files are translated from the PDF Drive made of them. Before translating, the agent shows the file list and asks to confirm, then builds one section per file on the canvas and translates them all in one run, in parallel: a file that fails stops only its own section. At the end it reports every file's outcome.
export Presentazione PowerPoint
// Crea una presentazione su qualsiasi argomento nel tema Emblema: dai documenti di una cartella Drive, da un singolo file (PDF, Word, la trascrizione di un video o di un audio) o, senza documenti, dalla richiesta stessa. Sceglie i topic, genera slide HTML (con o senza immagini) e le assembla in una presentazione. Su richiesta la pubblica con un link condivisibile, ne fa il PDF e il file PPTX. Builds a presentation on any subject in the Emblema theme: from the documents in a Drive folder, from one file (a PDF, a Word document, a video or audio transcript) or, with no documents, from the request itself. It picks the topics, generates HTML slides (images optional) and assembles the deck. On request it publishes a share link and makes the PDF and the PPTX file.
export Vibe Coding
// Build software in your GitHub repository: a landing page, a website, a web app, an API or a new feature in an existing product. Plan it the way gstack does, then build it in parallel coding lanes. An office-hours interview in the chat produces a design doc; gstack's reviews (spec, CEO, design, developer experience, engineering) settle every decision with you; the approved tasks become up to 4 coding lanes, each on its own branch of your GitHub repository, each opening a draft pull request. The pull requests you pick are merged into one working branch, which opens as a single pull request for you to merge on GitHub. Nothing touches GitHub until you approve — you can also create the lanes without starting them. Needs a GitHub connection with write access to the repository. Costruisci software nel tuo repository GitHub: una landing page, un sito web, una web app, un'API o una nuova funzionalità di un prodotto esistente. Pianificalo come fa gstack, poi costruiscilo in lane di codice parallele. Un'intervista in chat produce un design doc; le review di gstack (spec, CEO, design, developer experience, engineering) fissano ogni decisione con te; i task approvati diventano fino a 4 lane, ognuna su un proprio branch del tuo repository GitHub, ognuna con una pull request in bozza. Le pull request che scegli vengono unite in un unico branch di lavoro, che si apre come una sola pull request da unire tu su GitHub. Nulla tocca GitHub prima della tua approvazione. Richiede una connessione GitHub con accesso in scrittura.
export Keyword Research
// Trasformare un input grezzo (un URL, un elenco di prodotti, un argomento) in un pacchetto di keyword pronte all'uso — classificate per intento, priorità e raggruppate in cluster tematici
$ ls ./latest_node_templates
view all →export Drive File Reader
// Reads one Drive file exactly as it was uploaded (a PDF, a PowerPoint or Word file, an image, an archive or any other type) and outputs it as a File, for nodes that take the file itself rather than its text: e.g. Snapshot, to turn a PDF into page images. Also outputs its MIME type and size. For the text of a document or a transcript, use Drive Content Reader instead.
export Brand Master
// Publishes a customer PowerPoint master (.pptx or .potx from Drive) as this workspace's layout library. Extracts every layout with its slots, capacities and theme, applies the curator's layout curation, renders each layout's background through document-render, and outputs the library handle, the enabled layouts as a compact text list for choosing each slide's layout, the catalog, the master normalized to .pptx, and the background and thumbnail images. A deck in this workspace wires Library, Master and Backgrounds straight to its slide nodes; a deck elsewhere reads the library through a Layout Library. The library is this node's latest completed run; a failed run keeps the previous one. One Brand Master per workspace.
export Layout Library
// Reads the layout library a Brand Master node publishes in another workspace: that node's latest completed run. Outputs the library handle (the enabled layouts with their slots and capacities, plus the library CSS) for Slide Generators, the Presentation Composer and the PPTX Builder, the master as a .pptx file, the layout backgrounds, and the enabled layouts as a compact text list for choosing each slide's layout. Run it again to pick up the curator's latest publication.
export save-file
// Save a workspace file or text into a Drive folder
export Drive Folder Reader
// Reads all documents from a Drive folder recursively. Returns document references that can be passed to a Drive Content Reader. Also returns every file with its sub-folder path, so a loop can save results into the same sub-folders elsewhere.
export PDF Translator
// Translates one Drive document into another language keeping its page layout (columns, tables, figures) and returns a translated PDF, a bilingual PDF for review (each original page beside its translation, on by default), and a report. Word, PowerPoint and text uploads are translated from the PDF Drive made of them, so they also come back as a PDF, never as an editable file. The run succeeds only when every passage is translated and the result passes the checks for leftover untranslated text and changed numbers; otherwise it fails with a clear message naming the problem and the pages, and returns no PDF. An optional Style says in your own words how the translation should read (formal, plain language, technical). Scanned PDFs (no text layer) are refused. Text inside pictures is not translated. For a text-only reading copy, use the Drive Translate menu instead. To keep the result in Drive, connect it to Save File.