Choose your assistant.

All five routes are experimental. A recommended route needs a completed presentation and revision in the actual product.

Build your starter ↗

Documentation reviewed 2026-10-28 · Present 1.0.0 · Product tests pending

ChatGPT · Experimental

Check this surface's capabilities first; use the URL instructions only if the complete workflow and template can be retrieved and a file can be created.

Setup
  • 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.

Candidate single-folder skill archive. The documented OpenAI API layout does not establish ChatGPT UI import support.

Limits
  • 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.

Official documentation ↗

Claude · Experimental

After checking capabilities and policy, try the Claude-specific native skill archive.

Setup
  • 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.

ZIP with one skill-named top-level folder containing SKILL.md and resources.

Limits
  • 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.

Official documentation ↗

Microsoft 365 Copilot Chat · Experimental

Check whether your organization offers Agent Builder; follow that separate route when available.

Setup
  • 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.

No generic chat attachment is treated as a native skill installation. Agent Builder is a separate setup surface.

Limits
  • 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.

Official documentation ↗

Microsoft 365 Copilot Agent Builder · Experimental

After checking licensing and tenant permission, try the Microsoft-specific complete native skill archive.

Setup
  • 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.

ZIP with SKILL.md directly at archive root, plus included resources.

Limits
  • 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.

Official documentation ↗

GitHub Copilot · Experimental

Use the advanced skill-folder route from your chosen GitHub Copilot surface's documentation.

Setup
  • Choose the actual Copilot agent surface and its documented skill location.
  • The environment must permit local file creation and the required browser validation.

Technical skill-folder installation; locations vary by app, CLI, IDE, and cloud surface.

Limits
  • GitHub Copilot is a separate development product, not Microsoft 365 Copilot Chat.
  • A successful development-agent run would not certify any Microsoft 365 surface.

Official documentation ↗

What a tested route
will establish.

Retrieve or import the resources, generate and open an HTML attachment, then make a successful revision. Record product, plan, settings, release, date, and any help required.

Current evidence

Documentation review only. No provider end-to-end workflow has been tested. Package validation is a separate local check. The example records distinguish the Codex workspace run from these product routes. Structural package checks and local browser checks do not establish provider execution.

A missing-capability trial must also show that the assistant reports unavailable retrieval or file creation accurately.

Inspect the examples ↗