soliplex-concierge: room access / creation support
This project provides a Soliplex extension for LLM-driven, on-demand room requests: users chat with a self-serve "about" room to request access to a non-public room or the creation of a new room, and the concierge files each request as a tracking issue on a Gitea repository for an administrator to resolve.
📖 Full documentation: https://soliplex.github.io/soliplex-concierge/
Components
-
The Python library backs both the in-room issue-filing tool and the admin scripts that resolve filed requests (see the API reference).
-
Three Agent Skills under
skills/:soliplex-concierge-installer— wire the extension into a stacksoliplex-concierge-room— the in-room request formatter, installed into the about-roomsoliplex-concierge-admin— triage and resolve the filed requests
See Skills for where to find each one and how to install it.
Quick start
Installing the concierge onto a
soliplex-template-generated
stack is a job for an AI coding agent (e.g. Claude Code) running the
soliplex-concierge-installer skill — you point it at your stack rather
than running the wiring script yourself:
- Install the skill into your coding agent — download the latest
soliplex-concierge-installerrelease and unpack it into the agent's skills directory. - Ask the agent to wire up your stack, giving it the stack path and your
Gitea owner / repo. The skill runs its bundled
scripts/install_concierge.pyto apply what it changes, idempotently. - Bring up the stack — set real Gitea values in
.env, thendocker compose build backend && docker compose up -d.
The Gitea token's account must have Write access to the tracking repo, not
just Read — Gitea lets a Read-only account open issues but silently drops their
labels, so requests would be filed untagged (see issue #59). A fine-grained
token additionally needs the write:issue and read:repository scopes.
See Setup for the
full option list (version pinning,
--with-truststore for an enterprise / internal CA, …), running
install_concierge.py directly, and the
manual-wiring steps
for a non-generated installation.
Once the stack is up, users file requests through the about-room — and you
resolve them from your coding agent with the
soliplex-concierge-admin skill
(installed the same way as the installer). Its gitea_issues.py CLI lists and
filters open requests, follows up on them, and closes each with a comment and a
decision label. See Admin for the workflow.
1 maintainer
Metadata
1 maintainer
Release files for soliplex-concierge 0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| soliplex_concierge-0.11.tar.gz | 24.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| soliplex_concierge-0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.1 kB
Release files / soliplex_concierge-0.11.tar.gz
| Download URL | soliplex_concierge-0.11.tar.gz |
|---|---|
| Size | 24.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d72f6cd7ad25d5ecc950d8040acbad40c5eab43cdaa00d7c9bd56287993609d
|
|
BLAKE2b-256 checksum How to use checksums |
0a5729ef2df32271b46c51dde750a98a8dfdcc37cf3f36919c5603b4f261b53a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / soliplex_concierge-0.11-py3-none-any.whl
| Download URL | soliplex_concierge-0.11-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c06164066256024b854ca8ae2b0b27fcf5db49892c66859c7043965af038a46
|
|
BLAKE2b-256 checksum How to use checksums |
3fe346587d4c4f2d51346e76881ebb8ef24dcae061eb5e0186e66a52ec635813
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for soliplex-concierge 0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
