Orche
v1.0.1A multi-agent orchestration engine that systematically executes complex tasks in 4 phases (Query → Plan → Execute → Verify). Ensures high-quality deliverable...
⭐ 0· 86·0 current·0 all-time
by@reikys
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‑agent orchestration) align with the SKILL.md content: it defines Query→Plan→Execute→Verify phases, watchdog, debate/critic, hallucination checks, and state management. The skill is instruction‑only and requests no additional binaries or credentials, which is coherent for a behavior/coordination skill that relies on the hosting agent platform.
Instruction Scope
The SKILL.md includes install instructions (copy into ~/.agents/skills/orche) and describes writing/reading state files and running managed sub‑agents (parallel execution, execution phase, verification). This is expected for an orchestration skill but you should inspect the full SKILL.md to confirm it does not instruct the agent to read arbitrary sensitive files or exfiltrate data or to call unexpected external endpoints. The instructions appear scoped to orchestration tasks, but state file I/O and any runtime 'execute' steps could affect local files or external services depending on how the host agent executes actions.
Install Mechanism
No install spec or code is provided (instruction‑only). There are no downloads, extracts, or package installs. This is low risk from an installation footprint perspective.
Credentials
The skill declares no required environment variables, credentials, or special config paths. That aligns with the claimed behavior; nothing in the provided content requests unrelated secrets or system tokens.
Persistence & Privilege
Skill flags are default (not always:true). The SKILL.md indicates it writes state files and suggests placement into the user's skills directory (~/.agents/skills/orche). Writing state under the platform's skill directory is expected, but confirm exact paths and contents before running in production. Autonomous invocation is allowed by default (platform normal), which increases impact if orchestration steps can perform destructive actions — consider limiting agent permissions or testing in a sandbox.
Assessment
This skill appears internally coherent for a multi‑agent orchestration helper and does not request extra credentials or downloads, but proceed cautiously: (1) Inspect the complete SKILL.md for any commands that read system files, call external URLs, or instruct shell execution; (2) Confirm where state files are stored and what they contain (do not let it write secrets); (3) Run first in a sandboxed/test workspace and with limited agent permissions; (4) If you plan to use it with sensitive data or to perform actions with side effects (deployments, system changes), require explicit human confirmation points and/or restrict model autonomy. If you want, paste the full SKILL.md text (or the Execution/Watchdog/State Management sections) and I can point out any lines that look risky.Like a lobster shell, security has layers — review code before you run it.
latestvk972dhf5ymwjzy07qff3vzde6h83mmzv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎼 Clawdis