Ai Orchestration
v1.0.0Multi-agent AI orchestration, prompt engineering, and eval-driven development. Design, coordinate, and evaluate AI agent systems with structured communicatio...
⭐ 0· 40·0 current·0 all-time
byOptimize@pietjepuh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, and examples focus on multi-agent orchestration, prompt engineering, and eval-driven development. The allowed tools (Read, Write, Edit, Bash, Glob, Grep) are consistent with workflows like cloning repos, running tests, editing files, and coordinating agents.
Instruction Scope
SKILL.md contains broad patterns (parallel/ sequential workflows, repo cloning, file searches across directories, running tests) that are appropriate for orchestration but are somewhat open-ended. The instructions permit filesystem searches and shell execution; without explicit limits this could allow agents to read or modify many paths outside a project unless the runtime environment constrains them.
Install Mechanism
No install spec or external downloads—this is instruction-only, so nothing is written to disk by the skill itself during installation.
Credentials
The skill declares no required environment variables or credentials. That aligns with its role as a set of orchestration instructions. Note: example workflows reference git operations and calling models (call_model) which in practice require credentials; those are not requested or described by the skill.
Persistence & Privilege
always:false and no special persistence or cross-skill configuration modifications. disable-model-invocation:false is normal. The main privilege to be aware of is the skill's expectation to use file and shell tools at runtime.
Assessment
This skill is internally consistent for designing and running multi-agent workflows, but its runtime examples assume the agent can read/write files and run shell commands. Before installing or enabling it for an agent: 1) confirm what tool permissions (Read/Write/Edit/Bash/Glob/Grep) the agent runtime will grant and narrow those to project directories where possible; 2) do not provide broad host-level credentials or secret environment variables to agents using this skill (git push or model API access should be handled via least-privilege tokens and reviewed separately); 3) run unfamiliar multi-agent orchestration tasks in an isolated environment or sandbox until you verify behavior; and 4) if you need stricter limits, request or add explicit constraints in the SKILL.md (allowed paths, explicit credential requirements, or deny-lists) before using broadly.Like a lobster shell, security has layers — review code before you run it.
latestvk972y8qryx7fxcec8ehq21z1b58406br
License
MIT-0
Free to use, modify, and redistribute. No attribution required.