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. ACT includes supplier and subprocessor review records and proposed contract wording for local legal and procurement review. Your team verifies the evidence and resolves open issues.
When the assessment identifies control gaps, discuss the required scope and evidence with Move78. ACT includes an editable board oversight deck and written briefing, supported by intake, ownership, supplier and executive decision records. Your team gathers the evidence and records the next action.
See the editable ACT records 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 review dates are stated in the relevant guides. 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.