Slidesfly integrations and examples

Public, reproducible integration assets for Slidesfly, the publishing layer for existing HTML presentations.

The Best Practices badge links to the project's self-certified passing assessment. The Scorecard badge reports the current automated repository checks. Neither badge is an endorsement by OpenSSF.

This repository intentionally excludes the private Slidesfly SaaS application, infrastructure, credentials, customer data, and billing implementation. It contains only integration surfaces that developers can inspect, test, and reuse.

Contents

Path	Status	Purpose
action.yml	Public beta; production-smoke verified	Marketplace-ready root Action for publishing or updating an HTML deck
gemini-extension.json	Installable	Gemini CLI extension with the Skill and hosted MCP
actions/publish	Backwards-compatible	Existing subdirectory entry point for the publish Action
skills/slidesfly	Installable	Official Slidesfly Agent Skill
claude/slidesfly	Package-ready	Claude Code plugin with the Skill and hosted MCP
cursor/slidesfly	Submitted; review pending	Cursor plugin with the Skill and bundled CLI runner
examples/plain-html	Live-verified fixture	One self-contained HTML deck
examples/codex-generated	Live-verified fixture	Agent-generated single-file deck
examples/frontend-slides	Live-verified fixture	Pinned Frontend Slides single-file compatibility fixture
examples/revealjs	Live-verified fixture	Reveal.js 6.0.1 multi-file build
examples/slidev	Live-verified fixture	Slidev 52.18.1 static build
examples/marp	Live-verified fixture	Marp CLI 4.5.0 single-file export
examples/quarto	Live-verified fixture	Quarto 1.10.18 self-contained Reveal.js export
mcp/server.json	Published v0.1.0	Active official MCP Registry metadata for the hosted server
mcp/server-card.json	Discovery metadata	Static capability card for auth-walled scans

Start here

• GitHub Marketplace Action
• Publish an HTML presentation
• Framework compatibility matrix
• CLI documentation
• Hosted MCP documentation
• npm CLI package
• npm MCP package
• Gemini CLI extension manifest
• Claude Code plugin package
• Cursor plugin package
• Security architecture
• Canonical Slidesfly Skill

Install the public Skill source with:

npx skills add rare/slidesfly-integrations --skill slidesfly

Install exact public npm versions with:

npm install --global @slidesfly/cli@0.1.3
slidesfly --version
npx -y @slidesfly/mcp@0.1.0

The registry tarball URLs, npm integrity values, and independently computed SHA-256/SHA-512 checksums are recorded in releases/npm-packages.json. Verify the live registry artifacts with node scripts/verify-npm-release.mjs before mirroring or auditing them.

Install the Gemini CLI extension from the public repository:

gemini extensions install https://github.com/rare/slidesfly-integrations --ref v0.3.1

Gemini CLI requests SLIDESFLY_API_KEY as a sensitive setting and stores it in the system keychain. Create a key in the Slidesfly dashboard when you are ready to use the hosted MCP; never commit the key to this repository.

The Cursor package intentionally does not bundle the API-key-only hosted MCP. Cursor Marketplace plugins currently have no stable install-time secret-input flow for that configuration, while the bundled Slidesfly runner already supports anonymous publishing and the user's existing CLI login. See the package README for the exact boundary. The package was submitted on 2026-08-01 and has not been accepted or published by Cursor.

Publish a deck from GitHub Actions with:

- id: deck
  uses: rare/slidesfly-integrations@v0.3.1
  with:
    file: deck.html
    api-key: ${{ secrets.SLIDESFLY_API_KEY }}
    visibility: unlisted

The root Action is the Marketplace entry point. The existing rare/slidesfly-integrations/actions/publish@v0.1.1 path remains available for workflows already using it.

Current boundaries

• The website installer and @slidesfly/cli@0.1.3 are supported public CLI distributions.
• The hosted MCP endpoint is https://slidesfly.com/api/mcp and requires a Slidesfly API key.
• The stdio MCP package is @slidesfly/mcp@0.1.0; its local config remains separate from hosted MCP bearer authentication.
• Multi-file zip publishing requires an eligible authenticated plan.
• Every example marked live links to a reader URL; each fixture records its own verification date and evidence boundary.

Releases

Integration releases use semantic version tags. The root Action is released from the same public repository as the MCP, Skill, and framework fixtures. Pin a commit SHA for the strongest supply-chain stability, or use a reviewed release tag when a moving major tag is not available. Release assets mirror the verified npm tarballs and include SHA256SUMS and SHA512SUMS; the registry remains the canonical package source.

The manual release-attestation workflow can add a Sigstore-signed in-toto release attestation after re-verifying both the npm artifacts and GitHub release assets. See release attestation verification for the exact claim boundary and consumer command. A release is not signed merely because the workflow exists; check the release assets and verify the bundle before relying on it.

See MAINTENANCE.md, CONTRIBUTING.md, and SECURITY.md before relying on a public-beta integration in production. The OpenSSF Best Practices passing status and evidence records the current public evidence, assessment scope, and ongoing maintenance boundaries.

License

MIT