Agent Training System
v1.0.0Agent培训系统 - 用于培训多Agent团队。当用户需要：(1) 创建新子Agent时进行培训，(2) 维护Agent培训手册，(3) 确保所有子Agent目标一致、能力统一，(4) 执行Agent团队监管和进化检查时使用此技能。触发词：培训agent、agent培训手册、新agent培训、team trai...
⭐ 1· 944·10 current·10 all-time
by@zlim5
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (agent training, maintaining training manual, auditing/evolving agents) match the instructions and included template. There are no unrelated env vars, binaries, or install steps that would be disproportionate to this purpose.
Instruction Scope
SKILL.md directs the Main agent to create and read files under agents/{agent_id}/ (IDENTITY.md, SOUL.md, MEMORY.md, HEARTBEAT.md, USER.md) and to maintain AGENT_TRAINING.md. That is coherent for training/oversight, but it means the Main agent will consolidate agent state and user-related data (MEMORY.md, USER.md). This centralization is expected for the skill's purpose but increases privacy/aggregation risk and should be governed by access controls and retention policies.
Install Mechanism
Instruction-only skill with no install spec and no code files. Lowest install risk — nothing will be downloaded or written by an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths. The SKILL.md's file-access expectations are limited to project-local agent files described in the template and are proportional to the training function.
Persistence & Privilege
always:false and normal model invocation are used (expected). The skill assumes the ability to read/write agent files and to act as a coordinator with final-decision authority for child agents; this is consistent with its role but grants operational centrality — ensure the Main agent's actions are auditable and appropriately scoped.
Assessment
This skill appears to do what it says: coordinate and train child agents using local agent files and a training manual. Before installing, confirm: (1) where agents/{agent_id} files will be stored and who/what can read them (MEMORY.md and USER.md may contain private user data); (2) retention and access control — enforce least privilege and audit logs for Main-agent actions; (3) whether automated (autonomous) actions by the Main agent need explicit human approval in your environment; and (4) that AGENT_TRAINING.md and templates follow your privacy/compliance rules. If you plan to use this on production data, consider encrypting sensitive files and restricting the Main agent's write/read permissions accordingly.Like a lobster shell, security has layers — review code before you run it.
latestvk971wvynv2kqr5rswj0cw866s181nfse
License
MIT-0
Free to use, modify, and redistribute. No attribution required.