azure-appconfiguration-py

Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-appconfiguration-py/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is an efficient, code-heavy reference with strong actionability, but it is a monolithic inline document with no progressive disclosure and no validation steps around its destructive and batch operations.

Suggestions

Add validation/verification checkpoints around destructive operations (e.g. confirm a setting exists and check the affected label before delete) to lift workflow clarity above the cap.

Split the larger sections (feature flags, snapshots, async client) into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.

Remove the generic 'When to Use'/'Limitations' boilerplate and the redundant operations table, or replace them with concrete, skill-specific guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code examples with short section headers and assumes Claude's competence, but the 'Client Operations' table partly repeats the code above and the generic 'When to Use'/'Limitations' boilerplate ('applicable to execute the workflow or actions described in the overview') is filler that earns few tokens.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready code for get/set/delete/list/feature-flags/read-only/snapshots/async, but has minor gaps such as the async example referencing an undefined `endpoint` variable and missing `import os` in the auth snippets.	4 / 5
Workflow Clarity	Content is a collection of independent operations rather than a sequenced workflow, and destructive operations (delete_configuration_setting) and batch operations (list/snapshots) appear without any validation or verification checkpoints, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers are clear and well-organized, but the entire ~250-line API reference is inlined in SKILL.md with no bundle files or one-level-deep references for topics (feature flags, snapshots, async) that could reasonably live in separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 specific and clearly tied to a distinct Azure service, covering capability areas and a 'Use for' clause. Its main weakness is that the 'when' guidance restates capabilities rather than offering concrete natural trigger phrases.

Suggestions

Rewrite the 'when' clause as explicit trigger guidance, e.g. 'Use when the user mentions Azure App Configuration, app config, feature flags, remote configuration, or dynamic settings.'

Add a couple of natural synonyms ('app config', 'remote config') to broaden trigger-term coverage.

Consider phrasing capabilities as concrete actions (e.g. 'read, write, and label configuration settings') rather than capability nouns.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure App Configuration SDK for Python') and lists several specific capability areas ('centralized configuration management, feature flags, and dynamic settings'), though these are capability nouns rather than concrete verbs like 'extract' or 'fill'.	4 / 5
Completeness	Clearly states what the skill is and includes a 'Use for...' clause naming the applicable domains, but the 'when' restates capabilities rather than giving concrete user-facing trigger phrases like 'Use when the user mentions Azure App Configuration or feature flags'.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('Azure App Configuration', 'feature flags', 'configuration management', 'dynamic settings'), but missing common synonyms like 'app config', 'remote config', or 'config service'.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named Azure service SDK, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/azure-appconfiguration-py/SKILL.md
Commit: 1f67c44

Reviewed: about 15 hours 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.