Run any Skill in Manus with one click

streamlit-private-init

Stars0

Forks0

UpdatedJune 4, 2026 at 20:21

Initialize a Streamlit app for private deployment with streamlit-private — scaffold a new app or wrap an existing Streamlit repo, adding a gateway, deployment assets, and a manifest without touching application code. Use when the user wants to "make my Streamlit app private", "set up streamlit-private", or "add auth to my Streamlit app".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DecisionNerd

DecisionNerd/streamlit-private

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	streamlit-private-init
description	Initialize a Streamlit app for private deployment with streamlit-private — scaffold a new app or wrap an existing Streamlit repo, adding a gateway, deployment assets, and a manifest without touching application code. Use when the user wants to "make my Streamlit app private", "set up streamlit-private", or "add auth to my Streamlit app".

streamlit-private: init

Initialize a repository for private Streamlit deployment by running the streamlit-private CLI. This skill drives the CLI — it does not scaffold files itself.

When to use

The user wants to make a Streamlit app privately deployable.
The user says "set up streamlit-private", "add authentication to my Streamlit app", or "wrap my app".
A repository has no streamlit-private.yaml yet.

If the user instead wants to change providers on an already-configured repo, use the streamlit-private-configure skill. If they want to ship it, use streamlit-private-deploy.

Hard rules

Never edit, move, or rewrite the user's application files. init only adds infrastructure (gateway, manifest, Dockerfiles, host config). If you ever feel tempted to modify a .py page or business logic, stop — that is out of scope.
Do not reimplement the CLI. Always run the streamlit-private command; do not hand-write the gateway, manifest, or Dockerfiles yourself.
init is idempotent. If the repo is already configured, do not force changes — report that and offer streamlit-private-configure instead.

Steps

Confirm the working directory is the user's Streamlit repository (or an empty directory for a brand-new project).
Run:
```
uvx streamlit-private init
```
Interpret the result:
- Empty directory → a new Streamlit app + gateway + assets + manifest are created.
- Existing Streamlit repo → infrastructure is added; the user's app is left untouched.
- Already configured → the CLI reports streamlit-private already configured. Use --force to reconfigure. Relay this and suggest the streamlit-private-configure skill rather than passing --force blindly.
- Non-Streamlit, non-empty repo → the CLI refuses with This repository does not appear to contain a Streamlit application. and changes nothing. Relay this; do not try to force it.
Tell the user what was created and what to do next: set provider secrets (see .env.example) and then deploy with the streamlit-private-deploy skill.

Notes

Provider selections (auth, hosting) are written to streamlit-private.yaml, which is the source of truth for later commands.
The CLI may prompt for auth/hosting provider choices; surface those prompts to the user rather than guessing.

More from this repository

same repository

streamlit-private-deploy

DecisionNerd/streamlit-private

Deploy a streamlit-private project to a managed host (Railway first; Render/Fly.io later) and return the private, authenticated URL. Use when the user wants to "deploy my Streamlit app", "ship it", "put it online privately", or "deploy to Railway".

2026-06-050

streamlit-private-access-requests

DecisionNerd/streamlit-private

List and act on pending access requests for a privately deployed Streamlit app — approve (add the user to the organization) or reject them via streamlit-private. Use when the user (an admin) wants to "approve access requests", "see who's requested access", or "let someone in".

2026-06-040

streamlit-private-configure

DecisionNerd/streamlit-private

Reconfigure an existing streamlit-private project — switch the auth provider (e.g. Clerk → WorkOS) or hosting provider (e.g. Railway → Render), or regenerate deployment assets, while preserving the user's application code. Use when the user wants to "change auth provider", "switch hosting", or "regenerate my streamlit-private config".

2026-06-040

streamlit-private-invite

DecisionNerd/streamlit-private

Invite a user to a privately deployed Streamlit app's organization via streamlit-private, so they become a member and gain access. Use when the user (an admin) wants to "invite someone", "add a user", or "give my colleague access" to the app.

2026-06-040

streamlit-private-troubleshoot

DecisionNerd/streamlit-private

Diagnose a failed streamlit-private deployment or broken private access — missing provider secrets, proxy/WebSocket issues, auth/membership problems, or a misconfigured manifest. Use when the user says "my deploy failed", "the app won't load", "sign-in is broken", or "the page is blank / keeps reconnecting".

2026-06-040

name	streamlit-private-init
description	Initialize a Streamlit app for private deployment with streamlit-private — scaffold a new app or wrap an existing Streamlit repo, adding a gateway, deployment assets, and a manifest without touching application code. Use when the user wants to "make my Streamlit app private", "set up streamlit-private", or "add auth to my Streamlit app".

streamlit-private: init

Initialize a repository for private Streamlit deployment by running the streamlit-private CLI. This skill drives the CLI — it does not scaffold files itself.

When to use

The user wants to make a Streamlit app privately deployable.
The user says "set up streamlit-private", "add authentication to my Streamlit app", or "wrap my app".
A repository has no streamlit-private.yaml yet.

If the user instead wants to change providers on an already-configured repo, use the streamlit-private-configure skill. If they want to ship it, use streamlit-private-deploy.

Hard rules

Never edit, move, or rewrite the user's application files. init only adds infrastructure (gateway, manifest, Dockerfiles, host config). If you ever feel tempted to modify a .py page or business logic, stop — that is out of scope.
Do not reimplement the CLI. Always run the streamlit-private command; do not hand-write the gateway, manifest, or Dockerfiles yourself.
init is idempotent. If the repo is already configured, do not force changes — report that and offer streamlit-private-configure instead.

Steps

Confirm the working directory is the user's Streamlit repository (or an empty directory for a brand-new project).
Run:
```
uvx streamlit-private init
```
Interpret the result:
- Empty directory → a new Streamlit app + gateway + assets + manifest are created.
- Existing Streamlit repo → infrastructure is added; the user's app is left untouched.
- Already configured → the CLI reports streamlit-private already configured. Use --force to reconfigure. Relay this and suggest the streamlit-private-configure skill rather than passing --force blindly.
- Non-Streamlit, non-empty repo → the CLI refuses with This repository does not appear to contain a Streamlit application. and changes nothing. Relay this; do not try to force it.
Tell the user what was created and what to do next: set provider secrets (see .env.example) and then deploy with the streamlit-private-deploy skill.

Notes

Provider selections (auth, hosting) are written to streamlit-private.yaml, which is the source of truth for later commands.
The CLI may prompt for auth/hosting provider choices; surface those prompts to the user rather than guessing.