--- name: company-presentation description: > Use this skill when the user wants to prepare an editable PowerPoint presentation based on a specified source, for example a document, PDF file, website, report, notes, transcript or set of links. Trigger it for requests such as "create a presentation from this document", "prepare slides based on the source", "turn the report into a presentation", "create a presentation from a PDF", "prepare a deck based on these materials" or "build a PPTX from the provided link". The skill first analyzes the materials, then prepares a slide plan, and creates the editable .pptx file only after the plan is explicitly approved. It uses only the company theme in assets/theme/ and the guidelines in references/brand-guidelines.md. It does not invent information that is not present in the sources. --- # Presentation based on a source ## Objective Transform materials provided by the user into a structured, readable and editable .pptx presentation. Preserve the meaning of the source materials, distinguish facts from editorial suggestions, and do not add unverified data. ## Package contents The skill uses only the following files: - `references/brand-guidelines.md` - brand and file-building guidelines: logo use, colors, fonts, text style, native PPTX construction, quality assurance and delivery. Read it before Step 6. - `assets/theme/` - company theme: - `design-system-dark.html` - colors, fonts and layouts for the Dark variant, - `design-system-light.html` - colors, fonts and layouts for the Light variant, - `export-rules.md` - rules for the canvas, shapes, fonts and export, - `template.pptx` - base template (fallback source of colors and fonts), - `DarkVersion.png`, `WhiteVerion.png`, `ColorVersion1.png`, `ColorVersion2.png` - variants of our company logo. The design-system files contain sample content: a quote, numbers, a phone number, a website address and fields such as "First Name Last Name". Treat them solely as a layout and style reference. Do not transfer this content into the presentation. Do not assume that any other files, folders or skills exist. If any of the above files are missing, say so explicitly and use the closest possible substitute without pretending that the missing material was used. ## Company data and confidentiality The presentation must be safe to present and share externally. - **The only permitted company element is our company logo** from the logo files in `assets/theme/` (`DarkVersion.png`, `WhiteVerion.png`, `ColorVersion1.png`, `ColorVersion2.png`). The rules for its use are in `references/brand-guidelines.md`. - **Apart from the logo, do not use any company data.** This applies to both our company and clients or partners: names and logos of other companies, contact details, personal data (first and last names, email addresses, phone numbers, photos of people), prices, margins, contract terms, non-public financial results, internal roadmaps and content marked as confidential. - Publicly available substantive information from sources (e.g. a description of a product feature, official vendor documentation) is presentation content, not company data, and may be used. - If the source contains prohibited data, omit it or replace it with a neutral label ("Client A", "a company from the logistics industry"). List it in the plan under "Omitted elements". - If the user asks to insert such data, restate this rule in one sentence and place "To be completed" there so the user can add it manually in the file. ## Source of truth Rely on the materials indicated or provided by the user. Do not invent numbers, names, quotations, dates, statuses or conclusions presented as facts. - Add incomplete, unreadable or contradictory information to the plan under "To be checked / source gaps". - Mark missing slide content literally as "To be completed". - If the narrative requires an addition (e.g. a recommendation), label it as "Editorial suggestion", not as information from the source. ## Workflow ### Step 0 - collect requirements Determine six parameters. First extract them from the user's message and attachments. Do not ask again for information the user has already provided. 1. Presentation objective. 2. Target audience. 3. Material language. 4. Approximate number of slides or presentation duration. 5. Visual variant: Dark or Light. 6. Material type: informational, sales, training, executive or technical. Do not block work because of missing parameters. Make a reasonable, neutral assumption, list it explicitly before the slide plan, and ask for confirmation together with approval of the plan. If the variant is not specified, use Dark and state that this is the default choice. ### Step 1 - inventory the sources List the materials you are using: uploaded files, documents, PDFs, websites, notes, transcripts and data provided in the conversation. If the user provided a link, use the available browsing tool. If the source cannot be read, state this explicitly and ask for the file or pasted content. Do not replace an unavailable source with the model's knowledge. ### Step 2 - analyze the material Extract: - the main objective and thesis, - the most important facts, numbers and quotations, - the logical sequence, - information suitable for visualization, - unnecessary elements, - data prohibited under "Company data and confidentiality", - gaps and ambiguities. For every important statement, preserve the ability to identify the source. ### Step 3 - propose the narrative Propose a story structure tailored to the objective and audience. Each slide should deliver one main message. Do not transfer entire paragraphs from the source - shorten the content without changing its meaning. ### Step 4 - prepare the slide plan Present the plan in the chat, not as a file. Start with a short summary of the sources and adopted assumptions. Then, for each slide, provide: - number and title, - main message (one sentence), - key points, - suggested layout and visualization type, - the source or part of the material on which the slide is based. Below the plan, add three sections: - "To be checked / source gaps", - "Omitted elements" - with a brief explanation, including data omitted for confidentiality reasons, - a question asking for approval of the plan and assumptions. ### Step 5 - approval gate Do not create the .pptx file until the user explicitly approves the plan. - Approval is an unambiguous agreement to build in response to the plan, e.g. "I approve", "approved", "yes", "OK, create the PPTX". - Corrections are not approval. Apply them, show the changed plan rows, and ask again. - A generally positive reaction without reference to the plan ("interesting", "looks good") is not approval. Ask briefly whether you may build the file. - If the user asks for a PPTX immediately, still show the plan first and explain in one sentence that this saves revisions to the finished file. ### Step 6 - build the presentation Read `references/brand-guidelines.md` and follow it. In summary: - Create a native, editable .pptx presentation according to the approved plan. If it turns out during construction that the plan needs to change (e.g. the content does not fit on a slide), ask instead of changing it silently. - Take colors, fonts and layouts from `design-system-dark.html` or `design-system-light.html`, depending on the variant. Apply `assets/theme/export-rules.md`. - Place our company logo in the variant matched to the background, according to the table in `brand-guidelines.md`. Do not insert any other logos. - Visually distinguish "To be completed" fields so they are easy to find. - Preserve full Polish characters in Polish-language materials. ### Step 7 - quality assurance Before delivering the file: 1. Check the slides against the sources and the approved plan. 2. Check that each slide has one main message. 3. Check that, apart from our company logo, the file contains no company data (including speaker notes and the file name). 4. Check hierarchy, margins, overflows and readability. 5. Check compliance with the selected theme variant and the presence of the correct logo. 6. Check Polish characters and language errors. 7. Run the validator and render the presentation as described in `brand-guidelines.md`, then review all slides. 8. Perform at least one revision round if the review reveals issues. ## Hard rules - Analysis and plan first, presentation second. - The .pptx file is created only after explicit approval of the plan. - Do not invent information missing from the sources. - Do not present editorial suggestions as facts from the source. - For company data, use only our company logo from `assets/theme/`. - Do not assume that files other than those listed in "Package contents" exist. - Do not launch other presentation skills. You may use the validation and rendering scripts specified in `brand-guidelines.md`. - If the source is unavailable, say so explicitly. - If a theme element is missing, use the closest substitute and clearly describe the deviation. - In Polish texts, use only a hyphen (-) as a dash in a sentence. ## Result The skill delivers, in order: 1. a short summary of the sources and adopted assumptions, 2. a slide plan for approval, 3. after approval, an editable .pptx file, 4. a short note about the applied theme variant, sources, "To be completed" fields and any simplifications.