EvoAgentX Workflow
PassAudited by ClawScan on May 1, 2026.
Overview
The skill appears to be a straightforward EvoAgentX helper, with normal cautions around installing a third-party Python package and reviewing generated workflows before running them.
Before installing, verify the EvoAgentX package source and use a virtual environment. If you build workflows from the examples, keep web/browser/file tools narrowly scoped, require approval for sensitive actions, and review generated Python files before running them.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the dependency means code outside this skill package can run in the user's Python environment.
The skill instructs users to install the external EvoAgentX framework without a pinned version or hash. This is central to the skill's purpose, but it means the user must trust the external package/source.
pip install evoagentx ... git clone https://github.com/EvoAgentX/EvoAgentX.git
Install from a trusted source, preferably in a virtual environment, and pin or verify the EvoAgentX version before using it for important workflows.
A workflow built from this pattern could choose network or file operations automatically if the user grants those tools.
The documentation shows auto-selecting tools that can browse the web or access files. This is purpose-aligned for agent workflows, but users should notice the breadth of tool authority if they implement this pattern.
workflow = AgentWorkflow(
tools=["web_search", "browser", "file_io"],
auto_select=True
)Limit tool lists to what the workflow truly needs, require review for file/network actions, and avoid giving broad file I/O access to self-evolving workflows.
Using unsafe names or running the command in the wrong directory could create or overwrite local Python files.
The CLI generates a Python file from user-supplied workflow name and description. It does not execute the file automatically, but the generated code is intended to be reviewed and run by the user.
filename = f"{workflow_name.lower()}.py" ... with open(filename, 'w') as f:
f.write(content)Use safe workflow names, run the generator only in the intended project directory, and review generated Python files before executing them.