ClawHub

fullstack-dev-engineer

v0.0.1

提供全栈开发架构设计、技术栈选型、前端开发、后端开发、运维部署指导；当用户需要架构设计、技术选型、前端开发、后端开发、运维部署或最佳实践咨询时使用

⭐ 0· 336·2 current·2 all-time
by@zuoanco
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (full‑stack dev guidance) matches the included SKILL.md and the several local reference documents (architecture, devops, frontend, best practices, etc.). There are no unrelated requirements (no external credentials, no unrelated binaries) that would be inconsistent with a developer guidance skill.
✓
Instruction Scope
Runtime instructions are purely procedural guidance for analyzing requirements, designing architectures, selecting stacks, producing code, and producing deployment artifacts. They reference only the bundled reference files and do not instruct reading system files, environment variables, network exfiltration, or contacting hidden endpoints.
✓
Install Mechanism
No install spec and no code files that would be written/executed on disk. Instruction‑only distribution is low risk and appropriate for a documentation/guidance skill.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. All recommendations in the documents are about typical dev/devops secrets handling (e.g., using Kubernetes Secrets) but the skill itself does not request access to them.
✓
Persistence & Privilege
Skill is not flagged always:true and does not request persistent system modifications. It can be invoked by the agent (default) but that is consistent with its purpose; nothing in the package indicates it would autonomously persist credentials or alter other skills.
Assessment
This skill is an instruction-only full‑stack engineering advisor and appears internally consistent. Before using: (1) review any generated code and configuration before running it in production (validate secrets handling, resource limits, and network rules); (2) if you plan to have the agent apply generated deployments or run scripts, ensure those actions happen in a sandbox or CI pipeline you control; (3) because the agent can generate code/config that references credentials or secrets, never paste sensitive keys into prompts — use placeholders and inject secrets via your own secure CI/CD or secret management systems.

Like a lobster shell, security has layers — review code before you run it.

latestvk978hsqywpyjk74bsng057ka3d82c3g4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments