Eo Ability Multi Expert

v1.0.0

多专家编排能力(Multi-Expert Orchestrator),协调多个专家并行/串行工作,结果自动汇流

0· 60·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (multi-expert orchestrator) align with the instructions: splitting tasks, scheduling experts, merging results, checkpointing. The skill declares no extra binaries, env vars, or config paths, which is proportionate to an instruction-only orchestrator.
Instruction Scope
SKILL.md contains orchestration logic and usage examples (/dream, Team Manager). It does not instruct the agent to read local files, system paths, or unrelated environment variables, nor does it instruct exfiltration or calls to unexpected external endpoints. It does reference EO sessions API and eo-workflow-* callers as integration points, which is expected for an orchestrator.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes on-disk execution and supply-chain risk.
Credentials
The skill requests no environment variables or credentials. This is proportionate to the stated purpose. Note: actual integrations with an EO plugin or sessions API (mentioned in the doc) could require credentials in a concrete implementation—those are not present here.
Persistence & Privilege
always is false and default autonomous invocation is allowed (normal). The skill does not request permanent presence or claim to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and internally consistent, but before installing or enabling it: 1) Verify the skill's source and trustworthiness (homepage/source unknown). 2) If you pair it with an actual EO plugin or eo-workflow-* integrations, inspect those implementations—they may request network access or credentials not present here. 3) Watch for any runtime prompts that ask for API keys or system credentials and avoid granting unrelated secrets. 4) Prefer least-privilege for any EO/session integrations and enable auditing/logging so you can review what agents actually do.

Like a lobster shell, security has layers — review code before you run it.

latestvk971ffx82yjz0c590wr1n42y0h84dh1s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments