Agent Templates System
v1.0.0OpenClaw Agent Templates system reference and workflow guide. Use when creating, editing, reviewing, debugging, or extending the built-in Agent Templates fea...
⭐ 0· 32·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/description match the included files: design notes, implementation map, schema, UI guidance, and an example template. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
SKILL.md and the references explicitly instruct readers to inspect repository source files and describe the create-from-template flow that writes config, workspace files, identity files, and seeds memory. That behavior is coherent for a template materialization feature, but it does mean using the feature will cause local file and config writes (into the OpenClaw state dir and target workspace).
Install Mechanism
This is instruction-only with no install steps, downloads, or code to write to disk as part of skill installation.
Credentials
The skill requests no credentials or env vars. However template definitions support optional clawhubUrl entries (example uses https://clawhub.ai/...), which implies that creating an agent could pull or reference remote skills — a reasonable capability for this feature but one you should review before materializing templates that reference external endpoints.
Persistence & Privilege
always is false and there is no install that persists or auto-enables the skill. The documentation explains components that will modify OpenClaw config and write workspace files when materializing templates — expected for this feature and scoped to the agent being created.
Assessment
This skill is a documentation-only guide for the Agent Templates feature and appears coherent with that purpose. Before using the create-from-template flow in production: 1) review any template JSON (especially workspace.files and memorySeeds) so you know exactly what files will be written and where; 2) verify the product's path-traversal protections and that workspace paths resolve where you expect (the docs state this check exists, but confirm in code/runtime); 3) inspect any included skills that have clawhubUrl or other external references — understand whether materializing the template will fetch or execute remote code; 4) test in a sandbox/non-production environment to confirm config updates and file writes behave as expected; and 5) be cautious with raw JSON editing (parser errors and malformed definitions can lead to unexpected materialization).Like a lobster shell, security has layers — review code before you run it.
agentsvk97136mf3mxazx64rw1zn1k991842v1glatestvk97136mf3mxazx64rw1zn1k991842v1gopenclawvk97136mf3mxazx64rw1zn1k991842v1gtemplatesvk97136mf3mxazx64rw1zn1k991842v1guivk97136mf3mxazx64rw1zn1k991842v1g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.