Azure AI Content Safety for Python

The skill explicitly prefers DefaultAzureCredential, constrains production credential chains, and places endpoints, tokens, and API keys in environment variables; it also labels API keys as a legacy path and supports image URLs, logging, and blocklist management. Points are deducted because it does not require user confirmation before external Azure calls, adequately disclose that text, images, and URLs are sent to a cloud service, or address sensitive-content handling, log redaction, least-privilege Azure roles, rollback, or image-URL access risks.

The documentation is mostly consistent about synchronous client lifecycle, authentication preference, and separating sync from async usage, and it advises validating current API method names. However, an example uses an undefined endpoint variable, and the skill lacks exception, timeout, retry, quota, and network-failure handling plus skill-specific reproducible tests. Under static calibration, reliability is capped at 10, so it receives 7.

Triggers, Python SDK scope, text/image moderation, blocklists, and severity classification scenarios are fairly clear for coding agents using Azure AI Content Safety. It does not define non-fit boundaries, input limits, output contracts, exclusion triggers, Chinese-language quality, regional availability, or mainland-China network reachability.

The YAML metadata supplies name, MIT license, author, version, and package name. The material is organized into installation, authentication, core scenarios, best practices, and reference files. Points are deducted for the absence of a changelog, explicit maintenance owner and update path, dependency version constraints, FAQ, troubleshooting guidance, and cleanup/delete examples; some reference content is duplicated.

Examples cover text and image analysis, blocklists, severity levels, and client selection, providing directly usable guidance for common introductory implementations. Production error handling, a complete async path, threshold decisions, privacy handling, and cleanup paths remain incomplete, and example correctness is not supported by skill-specific execution evidence. Under static calibration, effectiveness is capped at 7, so it receives 6.

The skill provides limited Microsoft Learn attribution, a named package, and auditable code snippets. The repository also shows generic CI, Vally evaluation, and test-harness material, but the supplied evidence does not establish coverage of this skill's key paths or provide skill-specific test results or independent corroboration. Under static calibration, verifiability is capped at 5, so it receives 4.