azure-ai-contentsafety-py

Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.

1.07x

Quality

70%

Does it follow best practices?

Impact

100%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-ai-contentsafety-py/SKILL.md

Quality

Content

64%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid API reference skill with excellent executable code examples covering the main Azure AI Content Safety SDK features. Its main weaknesses are the lack of error handling/validation workflows for API operations, some unnecessary explanatory content (harm category descriptions, generic best practices), and a monolithic structure that could benefit from splitting reference material into separate files.

Suggestions

Add error handling examples for common failure modes (authentication errors, rate limits, invalid content) with a try/except pattern showing how to recover or report issues.

Remove the Harm Categories description table (Claude already knows these concepts) and the meaningless 'When to Use' section to improve conciseness.

Add a brief workflow example showing the complete flow: authenticate → analyze → check severity threshold → take action, with explicit validation of the response before acting on results.

Move the reference tables (Severity Scale, Client Types, Harm Categories) to a separate REFERENCE.md file and link to it from the main skill.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples, but includes some unnecessary elements like the Harm Categories description table (Claude knows what hate speech and violence are), the 'When to Use' section is a meaningless tautology, and the Best Practices section contains generic advice that doesn't add much value.	2 / 3
Actionability	All code examples are fully executable, copy-paste ready with correct imports, proper client initialization, and realistic usage patterns. The examples cover authentication, text analysis, image analysis, blocklist management, and severity configuration with specific SDK classes and methods.	3 / 3
Workflow Clarity	The skill presents individual API operations clearly but lacks workflow sequencing for multi-step processes like blocklist creation → adding items → analyzing with blocklist. There are no validation checkpoints or error handling patterns for API calls that could fail (e.g., invalid credentials, rate limiting, malformed content).	2 / 3
Progressive Disclosure	The content is reasonably well-organized with clear section headers, but it's a monolithic document (~150 lines) where the blocklist management section and reference tables could be split into separate files. No external references are provided for advanced topics or the full API surface.	2 / 3
	Total	9 / 12 Passed

Description

75%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is functional and clearly identifies both what the skill does and when to use it, with a distinct niche around Azure AI Content Safety SDK. However, it could benefit from listing more specific actions (e.g., text analysis, image analysis, blocklist management) and including more natural trigger terms that users might use when seeking content moderation capabilities.

Suggestions

Add more specific concrete actions like 'analyze text for hate, violence, sexual, and self-harm categories, manage custom blocklists, process image content safety checks'

Include additional natural trigger terms users might say, such as 'content moderation', 'toxicity detection', 'hate speech detection', 'NSFW', or 'content filtering'

Dimension	Reasoning	Score
Specificity	Names the domain (Azure AI Content Safety SDK) and a key action (detecting harmful content with multi-severity classification), but doesn't list multiple specific concrete actions like configuring blocklists, analyzing specific harm categories, or handling async operations.	2 / 3
Completeness	Clearly answers both 'what' (Azure AI Content Safety SDK for Python, detecting harmful content in text and images with multi-severity classification) and 'when' ('Use for detecting harmful content in text and images') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure AI Content Safety', 'harmful content', 'text and images', and 'multi-severity classification', but misses common user variations like 'content moderation', 'toxicity detection', 'hate speech', 'violence detection', or 'NSFW filtering'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting Azure AI Content Safety SDK for Python specifically, which is unlikely to conflict with other skills. The combination of Azure, content safety, and SDK makes it distinctly identifiable.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-ai-contentsafety-py/SKILL.md
Commit: 0159794

Reviewed: about 1 hour ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.