Choose an answer to check it. Afterward, select any option to review its explanation.
Assuming the platform vets skills is exactly the trap: you have to verify what automated scanning exists and what it misses. The sandbox is there because the audit can miss runtime behavior, not as a duplicate of a scan.
Input filters and prompt screening watch the conversation, not the skill bundle, and a sandbox does not change that. The sandbox limits what the skill can touch; it adds no visibility for the filters.
Audit verdicts are approve, reject or remediate; none of them lapse on first use. The reason for confinement is runtime behavior the audit could not see, not an expiring verdict.
An audit only covers what is in the package you read. Runtime confinement is the net for what the audit cannot see, such as code pulled from the network after invocation, so audit and sandbox are used together.