Microservice Gen
v1.0.0A cloud-native Go microservices framework with cli tool for productivity. go zero, go, ai-native, ai-native-development, cloud-native, code-generation.
⭐ 0· 80·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe a local Go microservice devtools workflow; the packaged behavior is a POSIX bash CLI that records, lists, exports, and searches user-provided entries. The requested permissions (none) and files present are consistent with a local devtools utility.
Instruction Scope
SKILL.md and the script keep all activity local and limited to logging, listing, exporting, searching, and simple reporting. However, the CLI records any user-provided input verbatim to local log files (e.g., check.log, generate.log, etc.) without sanitization, so if a user inadvertently pastes secrets (API keys, passwords, private snippets) into commands those will be persisted locally. Also the JSON export implementation does not escape values safely and has minor formatting bugs which may corrupt exports.
Install Mechanism
There is no install spec; the skill is instruction-only with a single included bash script. No network downloads, package installs, or archive extraction are present.
Credentials
No environment variables or credentials are required. The script uses HOME to derive a data directory, which is expected for a local CLI. No unrelated secrets or config paths are requested.
Persistence & Privilege
The tool writes persistent data to the user's home directory (~/.local/share/microservice-gen). This matches the stated behavior but is a persistent footprint: logs, history, and exported files will remain on disk. The skill does not request elevated privileges nor modify other skills or system settings.
Assessment
This skill is coherent and appears benign, but review before installing: 1) It stores every command input verbatim under ~/.local/share/microservice-gen — avoid passing secrets or credentials as command input, because they will be logged. 2) Inspect the script if you plan to run it; it has minor bugs in JSON export/formatting and does not escape logged values. 3) Ensure the data directory permissions are acceptable (it will create files under your HOME). 4) If you want to avoid persistent logs, run the script in a sandbox or remove/redirect the DATA_DIR in the script before use.Like a lobster shell, security has layers — review code before you run it.
latestvk974gxn4v2nvyd1hm9da0m5xan838wzk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.