Production Agent Builder
v1.0.0Structured 8-step framework for building production AI agents. Use when designing a new AI agent, planning agent architecture, building an automated workflow...
⭐ 0· 122·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md and references/guide.md content: both provide an 8-step framework for designing production agents. The guidance about inputs, tools, memory, safeguards, interfaces, and testing is appropriate for an 'agent builder' skill.
Instruction Scope
The instructions stay within the stated purpose — they are a planning/design framework. They recommend connecting to external tools (email, Slack, DBs, vector stores) and logging tool calls, which is expected for a design guide but implies implementers will later need to attach credentials and tooling. The SKILL.md does not itself instruct reading system files, environment variables, or sending data to hidden endpoints.
Install Mechanism
No install spec and no code files are present (instruction-only). That minimizes risk because nothing will be written to disk or fetched automatically during install.
Credentials
The skill declares no required environment variables or credentials, which is proportional. However, its recommendations (attach data tools, action tools, vector stores, etc.) mean that any real implementation of the design will require external API keys/credentials; users should apply least-privilege and provide only the necessary credentials at implementation time.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent presence, system configuration changes, or access to other skills' configs. The default ability for an agent to invoke the skill autonomously is normal and not, by itself, a concern here.
Assessment
This skill is a guidance document (no code, no installs) and appears internally consistent with its stated purpose. Before using it in production: (1) verify the source/author (no homepage is provided), (2) when you implement the design, provide only the minimal credentials required for each connector (apply least privilege), (3) enforce the suggested safeguards — gate high-risk actions behind human approval and enable auditing/logging, and (4) review any platform-specific integrations (email, Slack, DBs, vector stores) for where data will be stored or transmitted to avoid unintended data exposure.Like a lobster shell, security has layers — review code before you run it.
latestvk97e6pqme5w41ez4ds7yq55nmh835y6g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.