The audit and its limits

Understand what release audits check, how findings inform review and why a clean report does not prove a skill is safe.

Prelaunch concept guide

Hosted access and public packages are not open yet.

Find known patterns

Static rules check format, routing descriptions, secrets, risky instructions, portability, size and other known patterns. Findings identify a severity, rule and location. Repository policy can block publishing on findings at or above its chosen severity.

Read what was examined

Deep scans and model-assisted reviews can add findings after a release is created. Their availability depends on configuration and edition. An incomplete scan is not a clean scan. A model finding requires human review.

Keep human review

The auditor does not prove that a skill is safe. No findings does not mean no risk. Read the guide and scripts, review changes, and pin the release you chose.

How SKaaS works