Agent Team Orchestration
v1.0.0Set up and coordinate multi-agent teams with defined roles, task workflows, handoff protocols, and quality review checkpoints.
⭐ 0· 89·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 skill's name and description (agent team orchestration) match the content of SKILL.md: templates and process rules for defining roles, lifecycles, handoffs, and quality gates. It does not ask for unrelated binaries, environment variables, or cloud credentials, which is proportionate for a configuration/coordination guide.
Instruction Scope
SKILL.md is high-level guidance and templates describing how agents should hand off tasks, store shared state in files, and select models. The instructions do not ask the agent to read arbitrary system files or exfiltrate data, but they do give an agent discretion about where to write/read shared-state files and which models to use. That discretion is expected for an orchestration guide but is somewhat open-ended (no strict filepaths, no constraints on what gets written), so runtime behavior depends on the hosting agent's policies.
Install Mechanism
There is no install spec and no code to fetch or execute. As an instruction-only skill, it does not write new artifacts to disk during installation, which is low-risk from an install-mechanism perspective.
Credentials
The skill declares no required environment variables, credentials, or config paths. It references using different models but does not request model API keys or platform credentials itself. The lack of requested secrets is proportionate to the stated purpose of providing orchestration guidance.
Persistence & Privilege
The skill does not request always:true and is user-invocable (normal). It recommends storing shared state in files (survives restarts), which implies read/write file access at runtime; the skill does not declare where files should live. Users should ensure the agent's file storage is appropriately scoped and that sensitive data is not persisted unintentionally.
Assessment
This is an instruction-only template for organizing agents, and it appears coherent and low-risk as provided. Before installing or using it:
- Confirm where the agent will write shared-state files and ensure those locations are isolated and not world-readable or containing secrets.
- If the agent will select or call external models, verify how model API keys and endpoints are managed by your agent platform (the skill does not request keys itself). Ensure model access is limited by policy and audited.
- Consider requiring a human reviewer for any production-critical workflows the template enables (quality gates are recommended by the skill but enforce them in policy).
- If you want stronger constraints, ask the skill author (or edit the template) to specify safe file paths, retention policies, and explicit model-selection rules.
No scanner findings were available because this skill contains only SKILL.md; that lowers install risk but means runtime safety depends on your agent platform's ability to constrain filesystem and network actions.Like a lobster shell, security has layers — review code before you run it.
agentsvk9739w46n1e7bqwa03bj7v0yth83dmhelatestvk9739w46n1e7bqwa03bj7v0yth83dmheorchestrationvk9739w46n1e7bqwa03bj7v0yth83dmheteamsvk9739w46n1e7bqwa03bj7v0yth83dmhe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.