CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-contentsafety-py

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/azure-ai-contentsafety-py/SKILL.md
SKILL.md
Quality
Evals
Security

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 actionability — all code examples are executable and cover the main SDK features well. However, it suffers from some verbosity (boilerplate sections, redundant imports, tables explaining concepts Claude knows) and lacks error handling/validation patterns for API operations. The monolithic structure could benefit from splitting blocklist management and reference tables into separate files.

Suggestions

Remove the boilerplate 'When to Use' and 'Limitations' sections, and trim the Harm Categories descriptions — Claude already knows what hate speech and violence are.

Add error handling examples for common failure modes (authentication errors, rate limits, invalid input) and show a validation pattern after API calls.

Reduce repeated import blocks by showing full imports once in the first example and using abbreviated forms (assuming client is already created) in subsequent examples.

Consider splitting blocklist management into a separate referenced file to keep the main skill focused on the core analyze text/image workflow.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with executable code examples, but includes some unnecessary content: the Harm Categories table descriptions are things Claude already knows, the 'Best Practices' section is generic advice Claude can infer, and the 'When to Use' and 'Limitations' sections are boilerplate filler that add no value. The repeated import statements across examples also add token bloat.

2 / 3

Actionability

All code examples are fully executable, copy-paste ready with correct imports, proper API usage patterns, and concrete demonstrations of text analysis, image analysis, blocklist management, and severity configuration. The examples cover the key use cases comprehensively.

3 / 3

Workflow Clarity

The skill presents individual 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 shown, which matters for API operations that can fail (invalid credentials, rate limits, malformed requests).

2 / 3

Progressive Disclosure

The content is reasonably well-organized with clear section headers, but it's a long monolithic file (~180 lines) where reference tables and blocklist management could be split into separate files. No bundle files exist to offload detailed content, and there are no references to external documentation for advanced topics.

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 well-structured with a clear 'Use for...' clause and a distinctive niche targeting the Azure AI Content Safety SDK. However, it could benefit from listing more specific actions beyond 'detecting harmful content' and including additional natural trigger terms users might use like 'content moderation' or 'toxicity detection'.

Suggestions

Add more specific concrete actions such as 'analyze text for hate, violence, sexual, and self-harm categories, configure custom blocklists, interpret severity levels'.

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

DimensionReasoningScore

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 concrete actions like configuring blocklists, analyzing specific harm categories, or handling API responses.

2 / 3

Completeness

Clearly answers both 'what' (Azure AI Content Safety SDK for Python, detecting harmful content with multi-severity classification) and 'when' ('Use for detecting harmful content in text and images'), with an explicit 'Use for...' trigger clause.

3 / 3

Trigger Term Quality

Includes relevant terms 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', 'NSFW', or 'content filtering'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific mention of 'Azure AI Content Safety SDK for Python' — this is a very clear niche that is unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
Reviewed

Table of Contents

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.