Run any Skill in Manus with one click

streamlit-private-access-requests

Stars0

Forks0

UpdatedJune 4, 2026 at 20:21

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".

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-access-requests
description	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".

streamlit-private: access-requests

List pending access requests and approve or reject them through the streamlit-private CLI / gateway. Approving adds the user to the organization (granting access); rejecting discards the request.

When to use

An admin wants to review who has requested access and act on it.
The user says "approve the pending requests", "who requested access?", or "let Sam in".

To proactively invite someone who hasn't requested access, use the streamlit-private-invite skill instead.

Hard rules

Admin-only actions with side effects. Approving grants real access; rejecting denies it. Confirm with the user before approving or rejecting, and show who the request is from.
Do not reimplement provider APIs. Use the streamlit-private CLI/gateway path; do not call the auth provider's raw API directly.
Default to listing first; never bulk-approve without explicit user confirmation.

Steps

Confirm the app is initialized and deployed, and the user is acting as an admin.
List pending requests:
```
uvx streamlit-private access-requests list
```
Show the user who is pending.
For each request the user wants to act on, confirm then run approve or reject, e.g.:
```
uvx streamlit-private access-requests approve <request-id>
uvx streamlit-private access-requests reject <request-id>
```
(If the exact subcommands/flags differ, consult uvx streamlit-private access-requests --help rather than guessing.)
Report the outcome: approved users are added to the organization and allowed through the gateway on their next visit; rejected requests are discarded.

Notes

Authorization is organization-membership-based: approval adds the user to the org via the provider, which equals access.

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-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-init

DecisionNerd/streamlit-private

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".

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-access-requests
description	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".

streamlit-private: access-requests

List pending access requests and approve or reject them through the streamlit-private CLI / gateway. Approving adds the user to the organization (granting access); rejecting discards the request.

When to use

An admin wants to review who has requested access and act on it.
The user says "approve the pending requests", "who requested access?", or "let Sam in".

To proactively invite someone who hasn't requested access, use the streamlit-private-invite skill instead.

Hard rules

Admin-only actions with side effects. Approving grants real access; rejecting denies it. Confirm with the user before approving or rejecting, and show who the request is from.
Do not reimplement provider APIs. Use the streamlit-private CLI/gateway path; do not call the auth provider's raw API directly.
Default to listing first; never bulk-approve without explicit user confirmation.

Steps

Confirm the app is initialized and deployed, and the user is acting as an admin.
List pending requests:
```
uvx streamlit-private access-requests list
```
Show the user who is pending.
For each request the user wants to act on, confirm then run approve or reject, e.g.:
```
uvx streamlit-private access-requests approve <request-id>
uvx streamlit-private access-requests reject <request-id>
```
(If the exact subcommands/flags differ, consult uvx streamlit-private access-requests --help rather than guessing.)
Report the outcome: approved users are added to the organization and allowed through the gateway on their next visit; rejected requests are discarded.

Notes

Authorization is organization-membership-based: approval adds the user to the org via the provider, which equals access.