PL Agent Orchestration
v1.0.0Multi-agent orchestration patterns for production deployments. Covers sub-agent QC workflow, model staggering across 5+ models, cross-validation patterns, fa...
⭐ 0· 97·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 and description match the SKILL.md content: it documents multi-agent orchestration, QC loops, model staggering, routing, and cost tradeoffs. All required resources referenced are models and orchestration patterns, which are appropriate for this purpose. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md contains patterns, examples, and pseudocode (call_model calls) that stay within orchestration and routing concerns. It does not instruct reading local files, scraping unrelated system state, or exfiltrating data to unknown endpoints. It does assume the availability of multiple model APIs, which is expected for this skill.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, so nothing will be written to disk or installed by the skill itself.
Credentials
The skill declares no required env vars or credentials, which is reasonable for an instruction-only orchestration guide. In practice, using these patterns will require API keys/credentials for each model provider; that is expected but correctly left to the host environment rather than embedded in the skill.
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges or indicate it will modify other skills or system-wide settings.
Assessment
This skill is an instruction-only orchestration guide and appears internally consistent. Before using it: ensure your agent environment provides the necessary model API credentials (the SKILL does not request them), set quotas/limits to control cost, review privacy policies for every model provider you call (sensitive data will be sent to multiple third parties), test the patterns in a safe sandbox, and monitor/autopsy agent actions and billing when you enable autonomous runs.Like a lobster shell, security has layers — review code before you run it.
latestvk97bf85sqa5yyqq1n7bw4nsr9x8343e7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎭 Clawdis
