Present.
Turn your notes into a browser presentation. Open the file, then refine it in the same conversation.
Create your first presentation ↗v1.0.0 · Unique design included · MIT
Create your first presentation.
Try complete fictional notes, or bring your own.
Horizon’s fictional notes are included. Nothing to prepare.
All routes await product testing. See evidence.
Use a ChatGPT surface that can retrieve the complete release, create an HTML attachment and inspect it. Copy the starter, then open ChatGPT.
Requirements & limitations
- Use a surface with skill access, URL retrieval or file attachments, and actual file creation.
- Current guidance distinguishes standalone desktop skills from web/mobile skills distributed through plugins.
- Workspace controls and available execution tools must permit the required workflow.
- No universal ChatGPT web ZIP-upload path or plan entitlement is asserted.
- The API's skill packaging rules do not certify ChatGPT installation or browser-presentation generation.
- URL retrieval does not guarantee linked resource retrieval or a downloadable HTML file.
Attach the candidate archive or extracted resources only where the chosen surface supports them; otherwise report the missing capability.
Enable code execution and file creation. In Customize → Skills, upload the complete Claude ZIP and enable Present. Then copy the starter.
Download Claude package ↓Requirements & limitations
- Enable code execution and file creation before adding a skill.
- Check organization policy on Team or Enterprise accounts.
- Upload the complete archive through Customize > Skills and enable it.
- Skill availability and successful HTML delivery must be tested on the actual account and surface.
- The documentation review does not establish Present output quality or offline behavior.
Use the URL entry point only if Claude can retrieve all required resources and create the presentation file.
Ask your administrator whether this chat can retrieve resources and create HTML attachments. Agent Builder is a separate setup; select it above if your tenant offers it.
Requirements & limitations
- Check the exact tenant, product entitlement, enabled tools, and ability to create an HTML file.
- Use Agent Builder separately if the tenant permits declarative agents with skills.
- Agent Builder documentation does not certify generic Copilot Chat URL execution or HTML-file delivery.
- Do not treat a text response or an accepted attachment as successful presentation generation.
Try the URL instructions only if this chat can retrieve every required file and create the output; otherwise state the limitation.
With a qualifying license and tenant permission, upload the complete Microsoft ZIP in Agent Builder → Configure → Skills → Add. Then copy the starter.
Download Microsoft package ↓Requirements & limitations
- A qualifying Microsoft 365 Copilot license or pay-as-you-go access.
- Tenant permission to add skills; Information Barriers tenants restrict end-user skill addition.
- Upload the complete ZIP in Agent Builder > Configure > Skills > Add, then try it.
- The script sandbox has no runtime internet access or package installation; required files must be bundled.
- HTML is a supported resource type, but usable Present file generation and revision still require end-to-end testing.
Ask the tenant administrator about the missing entitlement or policy; use another approved file-capable surface if unavailable.
Install the skill folder in the documented location for your Copilot agent surface. It needs file creation and browser inspection. Follow the setup guide before copying the starter.
Installation guide ↗Requirements & limitations
- Choose the actual Copilot agent surface and its documented skill location.
- The environment must permit local file creation and the required browser validation.
- GitHub Copilot is a separate development product, not Microsoft 365 Copilot Chat.
- A successful development-agent run would not certify any Microsoft 365 surface.
Use the URL entry point in a file-capable agent environment and check every retrieved release resource.
4. Create & open
Copy, paste in your assistant, then download its HTML attachment and double-click to open.
Read the assembled starter
Create a steering committee update for the leadership team, lasting about 10 minutes, in English. Assistant product: ChatGPT. Use the Present 1.0.0 workflow and all required pinned resources below, including the exact HTML template and bundled Unique design guidance. Workflow entry: https://skillsforbusiness.ai/skills/present/start.md Exact release: https://skillsforbusiness.ai/releases/present/1.0.0/manifest.json Keep this release and its pinned companion version fixed throughout the task. Preserve supplied labels, wording, figures, units, sources and qualifications. Translate only where the chosen language requires it; preserve the meaning and every numerical value. Use one parent workflow: brief → build → review → bounded correction. Consume the existing brief without restarting Direct. An Audit returns findings without editing; visual refinements must preserve approved content. Use this complete fictional source material. For Project Horizon, lead with the pilot approval and owner requirement, then show delivery, readiness and the next 90 days. Use warm paper, forest ink and one terracotta accent. Follow the selected presentation type, audience, duration and language above. - Q3 delivery: 8 of 10 milestones completed; two are scheduled for October. - Readiness: Product 84%, Operations 68%, Enablement 52%. These are illustrative readiness estimates, not audited measurements. - Next 90 days: validate in October, pilot in November, review in December. - Decision: approve a bounded pilot; sponsor to confirm the owner before launch. No customer or company records were used. These figures are fictional and must not be cited as business results. Create a self-contained HTML file using the actual Present template, attach it, and explain how to download it and open it in a browser. Render the actual artifact and check layout, navigation and offline behavior where tools permit. If you cannot retrieve the resources, create and attach the file, or inspect the result, state that limitation clearly. Mark unavailable checks unverified. A chat response alone is not a finished presentation. Keep the same conversation available for a revision.
No notes are uploaded here. Add private content only in your approved assistant.
5. Try one revision
On the readiness slide, make Enablement easier to identify. Preserve every label, percentage and qualification.
Use the same conversation. Download and open the revised attachment.
One file.
Ready to present.
Slides, speaker notes and keyboard navigation in one HTML file. Inspect the example.
Open, present & share
Download the HTML attachment and double-click it. Use arrows to navigate, F for fullscreen, O for the slide menu, N for notes and B to blank the screen. Speaker notes appear on the same screen. Share through your approved channel. Each final artifact needs an offline check.
Existing PowerPoint or PDF?
Present includes conversion guidance. Your assistant must read the source, extract content and assets, and create the HTML file. Inspect conversion fidelity. Native PowerPoint export is not implemented; a browser-printed PDF needs a separate visual check.
Only received a chat response?
Ask for a downloadable HTML attachment. If your assistant cannot create it or retrieve the complete workflow, the task is incomplete. Use an approved file-capable environment. Product workflows remain experimental until tested.
Privacy & content locks
This site receives no source notes or documents. Starter choices stay in this browser; supply confidential material only in your approved assistant. Visual revisions preserve approved wording, exact figures, units, sources and qualifications.