multi-role
v1.0.1将 AI 角色拆分为管理与技术层，分别负责协调、需求、编码与测试，实现任务路由、质量关卡和记忆管理。
⭐ 0· 119·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (multi-role governance) align with the files and runtime instructions: SOPs, role constitutions, memory routing, and task/log file management. Required env vars/binaries/config paths are none, which is proportionate for a purely governance/instruction skill that operates on files in its own directory.
Instruction Scope
SKILL.md is long and prescriptive: it instructs the agent to create sessions/ and templates/ directories, load constitution and SOP files (via Read tool), write structured task logs and a local metrics file, and follow strict routing/priority rules. These actions are consistent with the stated purpose. Two items to be aware of: (1) OUTPUT-RULES.md is declared highest priority and instructs terseness and to avoid exposing read/details in replies (it also says to answer truthfully if the user asks) — this reduces default transparency about what the skill read or wrote unless the user explicitly asks; (2) SKILL-VALUE-REPORT-SPEC includes examples with absolute user-paths (e.g. /Users/...), so implementations or other skills that copy the examples verbatim might write to those absolute locations if not adjusted to the actual installed path. Both are scope/behavior notes rather than contradictions.
Install Mechanism
Instruction-only skill with no install spec and no external downloads. Low risk from install mechanics because nothing is written to disk by an automated installer; runtime writes are confined to files in the skill repo as described.
Credentials
The skill requests no environment variables, no credentials, and no config paths. Its file operations are described to be limited to the skill directory (sessions/, templates/, references/, archives/). The metrics reporting mechanism is local-file based and optional for other skills to adopt; there are no requests for unrelated secrets or cloud credentials.
Persistence & Privilege
The skill persists data in its own directory (sessions/, task-logs/, archives/) and encourages other skills to append to sessions/.skill-metrics.jsonl. It does not set always:true. The only concern is that the OUTPUT-RULES policy promotes writing execution detail to logs rather than replies (reduces observational visibility) — and the metrics-write examples include absolute paths which could be misused if copied verbatim. Autonomous invocation is allowed (platform default) but not combined with broad credential access here.
Assessment
This skill appears internally coherent for a governance/multi-role framework and doesn't ask for secrets or external installs. Before enabling it: 1) Confirm the skill's installed path and that you are comfortable with it creating and writing files under that directory (sessions/, task-logs/, .skill-metrics.jsonl). 2) Review OUTPUT-RULES.md — by default the skill is told to be terse and record execution details in logs rather than replies; if you want more upfront transparency, ask the skill to always report file reads/writes in replies. 3) If you or other skills will follow the metrics examples, ensure example paths (like /Users/...) are adapted to the actual installation path so writes do not go to unexpected absolute locations. 4) If you need to limit file I/O, run the skill in a sandboxed environment or review the skill directory permissions first. If you want extra assurance, request a small test run and ask the skill to enumerate the files it will read/write before doing any changes.Like a lobster shell, security has layers — review code before you run it.
high efficiencyvk977fez3nrrv5qfz0re6xapyms839b2alatestvk977fez3nrrv5qfz0re6xapyms839b2amulti rolevk977fez3nrrv5qfz0re6xapyms839b2asave tokensvk977fez3nrrv5qfz0re6xapyms839b2a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.