菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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".
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".
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".
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.
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".
| name | streamlit-private-deploy |
| description | 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". |
Deploy the gateway-fronted Streamlit app to the managed host recorded in the manifest by
running the streamlit-private CLI, then report the private URL.
streamlit-private.yaml exists) and the user wants it live.If the repo is not yet initialized, run the streamlit-private-init skill first.
railway CLI must be installed
and authenticated (railway login, or a RAILWAY_TOKEN environment variable for
headless/CI use). deploy checks this first and prints guidance if it's missing — surface
that to the user rather than working around it.streamlit-private.yaml; deploy to that host. Do not invent infrastructure or deploy by
hand outside the CLI.streamlit-private deploy; do not script raw host API
calls yourself.Confirm streamlit-private.yaml exists. If not, switch to streamlit-private-init.
Determine the hosting provider from the manifest (e.g. railway).
Ensure required secrets are configured (see .env.example); if any are missing, ask the
user to set them on the host rather than guessing values.
Run:
uvx streamlit-private deploy railway
(substitute the manifest's hosting provider for railway).
Report the returned private URL to the user, and explain the access model:
If the deploy fails, switch to the streamlit-private-troubleshoot skill.
streamlit-private-invite and streamlit-private-access-requests skills.