Bubbletea Code Review
v2.3.0Reviews BubbleTea TUI code for proper Elm architecture, model/update/view patterns, and Lipgloss styling. Use when reviewing terminal UI code using charmbrac...
⭐ 0· 75·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (BubbleTea code review) match the content: the skill is an instruction-only reviewer with multiple reference docs and checklists. It does not request unrelated binaries, credentials, or config paths.
Instruction Scope
SKILL.md is narrowly scoped to static code-review guidance (what to flag/ignore, checklists, examples). It does not instruct the agent to read environment variables, system config, or send data to external endpoints. It assumes the agent will be given the code to review, which is appropriate for this kind of skill.
Install Mechanism
No install spec and no code files that execute at install time — lowest-risk setup. All logic is prose and reference docs bundled with the skill.
Credentials
The skill declares no required environment variables, credentials, or config paths. Examples in the references mention network/file I/O only as sample code patterns to flag or avoid; they do not indicate the skill needs access to those resources itself.
Persistence & Privilege
always is false and there is no persistence or requests to modify other skills or system settings. The skill is user-invocable and may be invoked autonomously per platform defaults, which is expected for a review helper.
Assessment
This skill is an instruction-only BubbleTea/TUI code-review checklist and appears coherent and low-risk: it asks for nothing beyond the code you give it and has no install steps. Two practical suggestions before installing/using: (1) provenance — source/homepage are missing, so prefer running it in contexts where the agent is only given the repo or files you want reviewed (don’t grant broad system or secrets access); (2) when the agent returns suggestions, treat them as guidance and review suggested code changes yourself. If you plan to let the agent operate autonomously across multiple repositories or commit changes, restrict its file access and credentials accordingly.Like a lobster shell, security has layers — review code before you run it.
latestvk977jpp9z3zwmaapct0scjx8nn83csyz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.