Team
v1.0.0The Autonomous Orchestration Framework (AOF). Defining the hierarchy, collaboration logic, and reward distribution for human-agent hybrid organizations and t...
⭐ 0· 358·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (autonomous orchestration framework) align with the SKILL.md content: a conceptual engine (role allocation, conflict resolution, reward routing). The lack of required binaries, env vars, or installs is consistent with an instruction-only design.
Instruction Scope
The SKILL.md contains only high-level architecture primitives and a lifecycle; it does not instruct the agent to read files, call external endpoints, or access secrets. However the instructions are intentionally vague (open-ended orchestration language) and would leave implementation choices to the agent, which may lead to broad or unexpected actions at runtime if the agent is permitted to act autonomously.
Install Mechanism
No install spec and no code files — lowest-risk delivery model (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill does not request any environment variables, credentials, or config paths. That is proportionate for a purely conceptual/orchestration spec, though real orchestration implementations would typically require additional service credentials which this skill does not request.
Persistence & Privilege
Flags show default behavior (user-invocable, agent may invoke autonomously). Autonomous invocation is normal, but combined with the skill's vague orchestration remit it could enable broad multi-agent behavior depending on the agent's other permissions — the skill itself does not request permanent/always-on placement or modify other skills.
Assessment
This skill is a conceptual framework and contains no code or external requests, so it appears coherent with its stated purpose. Before installing or enabling it, consider: (1) limit the agent's permissions (network, other skills, file system) so vague orchestration rules can't trigger broad actions; (2) do not provide financial or privileged credentials to any agent invoking orchestration without explicit need; (3) test behavior in a sandboxed environment to observe what the agent does when asked to 'recruit' or 'distribute rewards'; (4) require explicit human approval for any actions that involve external APIs, payments, or modifying other skills. If you need stronger assurance, ask the skill author for a concrete operational spec showing what APIs or other skills the orchestration will call and what safeguards are in place.Like a lobster shell, security has layers — review code before you run it.
collaborationvk97fg94swtpk33ftydykhmb9qd82hz9jlatestvk97fg94swtpk33ftydykhmb9qd82hz9jmgmtvk97fg94swtpk33ftydykhmb9qd82hz9jorgvk97fg94swtpk33ftydykhmb9qd82hz9jswarmvk97fg94swtpk33ftydykhmb9qd82hz9jteamvk97fg94swtpk33ftydykhmb9qd82hz9j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.