azure-appconfiguration-py

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

Quality

63%

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 a well-organized, mostly executable SDK reference that respects token budget better than most, held back by missing validation around destructive operations, inlined detail that belongs in reference files, and a few snippets with undefined variables. Boilerplate 'When to Use'/'Limitations' sections add tokens without value.

Suggestions

Add validation guidance around destructive and batch operations, e.g. get a setting and confirm its label before delete_configuration_setting, and check snapshot status before listing snapshot settings.

Move feature-flag JSON structure, snapshot workflows, and the async client into reference files (e.g. references/feature-flags.md, references/snapshots.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Fix minor executability gaps (import os, define endpoint and setting in the set_read_only/async examples) and remove the template 'When to Use' and 'Limitations' filler sections.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy with lean headers and almost no explanation of concepts Claude already knows, but the boilerplate tail ('This skill is applicable to execute the workflow or actions described in the overview' and the generic Limitations bullets) is filler that could be trimmed.	4 / 5
Actionability	Nearly all sections give concrete, runnable snippets (auth, CRUD, feature flags, snapshots, async), with minor gaps: 'os' is never imported in the connection-string example, set_read_only references an undefined 'setting' variable, and the async example uses an undefined 'endpoint'.	4 / 5
Workflow Clarity	Sections are clearly organized, but the skill documents destructive (delete_configuration_setting) and batch (list_configuration_settings) operations with no validation or verification steps, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and roughly 200 lines of API reference (feature-flag JSON details, snapshot operations, async client) are inlined in SKILL.md where they could live in separate reference files, fitting the 'content that should be separate is inline' anchor rather than the well-split structure of a 4.	3 / 5
	Total	14 / 20 Passed

Description

62%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 correctly identifies a distinct niche and includes both a what and a when clause, but it reads as a topic list rather than an action list and lacks concrete trigger phrasing and natural synonyms. It is serviceable but sits below the strong examples in the rubric.

Suggestions

Replace the capability noun phrases with concrete actions, e.g. 'Get, set, and delete configuration settings, manage feature flags, and create snapshots in Azure App Configuration from Python.'

Rewrite the when-clause with explicit trigger phrasing: 'Use when the user mentions Azure App Configuration, appconfig, feature flags, remote/centralized configuration, or appsettings in a Python project.'

Add natural synonyms and service-specific terms (app config, config store, .azconfig.io) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure App Configuration SDK for Python') and capability areas ('centralized configuration management, feature flags, and dynamic settings'), but these are noun phrases rather than concrete actions like get/set/delete settings or snapshot creation, so coverage is not comprehensive.	3 / 5
Completeness	'Azure App Configuration SDK for Python' answers what, and 'Use for centralized configuration management, feature flags, and dynamic settings' answers when, though the when-clause is purpose-scope rather than concrete trigger phrasing like 'Use when the user mentions...'.	4 / 5
Trigger Term Quality	'feature flags', 'configuration management', and 'dynamic settings' are natural terms, but common variations users would actually say — 'app config', 'remote config', 'config store', 'appsettings', '.azconfig.io' — are missing.	3 / 5
Distinctiveness Conflict Risk	'Azure App Configuration SDK' is a clear product niche, but the generic trigger phrases 'configuration management' and 'dynamic settings' create minor overlap risk with general configuration-tooling skills.	4 / 5
	Total	14 / 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/agentic-awesome-skills
Path: skills/azure-appconfiguration-py/SKILL.md
Commit: 7b534bc

Reviewed: 6 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.