Decide in under 4 minutes whether an OpenClaw skill belongs in sandbox, production review, or the reject pile.
This is a governance gate for skills, connectors, and MCP-style integrations. It is not a malware scanner, static code analyzer, or signature-based security verdict.
This is a governance gate for skills, connectors, and MCP-style integrations. It is not a malware scanner, static code analyzer, or signature-based security verdict.
Use this to classify a proposed OpenClaw skill or connector as approvable with standard controls, sandbox-only, hold for governance review, or reject.
This section classify the governance posture quickly, highlight the biggest gaps, and surface governance gaps and recommend an appropriate implementation path.
This assessment evaluates whether a proposed OpenClaw skill or connector is governable from a supplier-review standpoint, including provenance, testing, access, rollback, and approval workflow discipline.
Sandbox only does not automatically mean the skill is malicious. It means the evidence and control posture are too weak for normal enterprise rollout.
The missing value is a repeatable supplier-review workflow, retained evidence, approval logic, and policy linkage. That implementation depth sits in AI Controls Professional.
When the assessment reveals structural control gaps requiring policy, procedure, evidence, and implementation ownership, AI Controls Professional provides the full implementation evidence pack.
See the full implementation evidence pack for supplier review, evidence, and agentic governance.
Use the broader governance checklist alongside this approval gate.
Read the related due-diligence article that supports the approval workflow.
It evaluates provenance, maintainer trust, sandbox testing, permissions, data exposure, rollback, logging, ownership, and approval workflow maturity for a proposed OpenClaw skill or connector.
No. It means the evidence or control posture is not strong enough for standard enterprise rollout. The right next step is controlled testing, not automatic trust.
Because a skill with weak provenance and no reliable rollback path can expand blast radius faster than teams expect, even before formal production approval exists.
Because marketplace enthusiasm is not an enterprise control. A formal workflow creates retained evidence, owner accountability, and consistent decisions across skills and connectors.
No. The assessment runs entirely in the browser. Answers are not stored, synced, or submitted to a server.
Source and review note: This page was last reviewed on 6 May 2026 against the current Move78 public site baseline and relevant official or authoritative sources where laws, standards, frameworks, cybersecurity controls, product scope, pricing, support policy, or implementation guidance are discussed. It provides operational implementation guidance and product information only; it is not legal advice, tax advice, audit assurance, certification assurance, conformity-assessment advice, buyer-approval assurance, or security assurance. Validate legal, regulatory, contractual, tax, audit, and security decisions with qualified professionals.