ClawHub

Oraclaw Ensemble

v1.0.0

Multi-model consensus for AI agents. Combine predictions from multiple LLMs, models, or sources into a mathematically optimal consensus. Auto-weights by hist...

⭐ 0· 48·0 current·0 all-time
by@whatsonyourmind
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
The skill claims to call an external ensemble service and only requests a single API key (ORACLAW_API_KEY), which is appropriate for a hosted ensemble/aggregation service. There are no unrelated environment variables, binaries, or config paths requested.
ℹ
Instruction Scope
SKILL.md stays on-topic (describes ensemble inputs, outputs, rules, and pricing). It does not instruct the agent to read arbitrary files, environment variables, or system paths. One missing detail: the doc does not show the network endpoints, request/response schema, or explicit guidance on how/when to transmit user data to the external service — so the agent will need to use ORACLAW_API_KEY to call some external API, but that call is not specified here.
✓
Install Mechanism
Instruction-only skill (no install spec, no code files). This is the lowest-risk install posture — nothing is written to disk by the skill itself.
✓
Credentials
Only a single credential (ORACLAW_API_KEY) is required and declared as the primary credential, which is proportionate for a hosted API. No unrelated secrets or broad system credentials are requested.
✓
Persistence & Privilege
always is false and the skill does not request system-wide persistence or modify other skills. It does permit normal autonomous invocation (platform default).
Assessment
This skill appears coherent for a hosted ensemble service but the SKILL.md omits implementation details about network calls and data handling. Before installing or enabling it for sensitive tasks: 1) Confirm where requests are sent (official oraclaw.dev API endpoints) and what data is transmitted/stored. 2) Use a least-privilege ORACLAW_API_KEY (scoped/revocable) and monitor its usage. 3) Verify billing details (USDC on Base address) if you expect production traffic. 4) Avoid sending highly sensitive PII/credentials to third-party ensemble services until you’ve confirmed their retention and privacy policies. If you want stronger assurance, ask the publisher for an example request/response format and a data handling/privacy statement.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cpmm7kpxq1689bx1qa3nvah83qdae

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🤝 Clawdis
EnvORACLAW_API_KEY
Primary envORACLAW_API_KEY

Comments