Beszel
v1.0.0Deploy, secure, and troubleshoot Beszel monitoring with Docker agents, alert tuning, and upgrade-safe operations for self-hosted servers
⭐ 0· 268·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (deploy and operate Beszel with Docker agents) aligns with the declared requirement of the docker binary and the content of the docs. The metadata's config path (~/beszel/) matches the documented memory/storage location.
Instruction Scope
SKILL.md and supporting docs confine activity to planning, local notes (~/beszel/), and operational guidance. The skill repeatedly requires user confirmation before creating or updating files and explicitly warns against copying secrets into notes. It does not instruct reading unrelated system files or sending network data automatically.
Install Mechanism
Instruction-only skill with no install spec and no code to fetch or write to disk beyond the documented ~/beszel/ workspace. This is the lowest-risk install profile.
Credentials
No environment variables, credentials, or external API tokens are requested. The guidance cautions treating onboarding credentials as sensitive and not recording them, which is proportionate for a monitoring ops helper.
Persistence & Privilege
always is false and the skill stores files only under ~/beszel/ (its own workspace). It does not request or describe modifying other skills or system-wide settings. Model invocation is allowed (platform default) but that alone is not a concern.
Assessment
This skill is coherent and appears to do what it claims: planning and local operational notes for Beszel with Docker. Before installing: (1) confirm you’re comfortable with the skill creating and updating files under ~/beszel/ (the skill says it will ask for confirmation first), (2) never paste secrets or credentials into the notes — the docs explicitly warn against it, and (3) if you later configure external alerting destinations or provide onboarding credentials, treat those steps as separate and deliberate (verify endpoints and rotate credentials afterwards). Also ensure Docker is installed and that you control activation settings so the skill only becomes proactive when you want it to.Like a lobster shell, security has layers — review code before you run it.
latestvk978vbpf2zj9n9vqrq9a78eebx8247vr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📊 Clawdis
OSLinux · macOS · Windows
Binsdocker