azure-appconfiguration-ts

Centralized configuration management with feature flags and dynamic refresh.

Quality

57%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-appconfiguration-ts/SKILL.md

The canonical home for this skill is azure-appconfiguration-ts in sickn33/agentic-awesome-skills

Quality

Content

72%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 content is highly actionable with comprehensive executable code across all major features, and it is largely concise and code-driven. Its weaknesses are a lack of validation checkpoints around destructive operations and the absence of any progressive-disclosure file split for the sizable API reference.

Suggestions

Add validation/verification steps for destructive and batch operations (e.g., confirm a setting exists and back it up before delete; verify snapshot composition before archive) to lift workflow_clarity above 3.

Move the bulk API reference ("Key Types" and detailed method coverage) into a separate reference file and link to it one level deep to improve progressive_disclosure.

Tighten inline comments to only non-obvious values to push conciseness toward anchor 5.

Dimension	Reasoning	Score
Conciseness	The body is code-focused with minimal prose padding and helpful inline comments, fitting anchor 4 for efficient content with only minor instances that could be trimmed; it is not anchor 5 because the large inline API reference and some comments are not all strictly load-bearing.	4 / 5
Actionability	Every section provides complete, copy-paste-ready executable TypeScript covering CRUD, the provider, dynamic refresh, Key Vault references, feature flags, snapshots, and labels, matching anchor 5 for fully executable guidance across common cases.	5 / 5
Workflow Clarity	Sections are logically grouped but destructive and batch operations (delete, archive, list iteration) lack validation or verification checkpoints, so workflow clarity is capped at 3 per the rubric guideline for missing validation in destructive/batch contexts.	3 / 5
Progressive Disclosure	No bundle files exist and the full API reference is inlined in a single file with section headers, matching anchor 3 for some structure but bulk reference content that should be split remaining inline; it is not anchor 4 because there is no one-level-deep reference split.	3 / 5
	Total	15 / 20 Passed

Description

42%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 states a clear domain and two features but omits any natural trigger phrases and any "Use when..." guidance, capping both completeness and trigger-term quality. It is moderately specific but not distinctive enough to avoid overlap with similar configuration skills.

Suggestions

Add a "Use when..." clause naming concrete triggers such as Azure App Configuration, feature flags, app config, or dynamic config refresh.

Expand the capability list beyond two features (e.g., key-value CRUD, labels, snapshots, Key Vault references) to reach anchor 4-5 specificity.

Include natural user synonyms and the SDK/product name (Azure App Configuration) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ("Centralized configuration management") and two concrete features ("feature flags", "dynamic refresh"), matching anchor 3 for domain plus 1-2 actions, but the coverage is not comprehensive enough for anchor 4.	3 / 5
Completeness	The "what" is clear but there is no "Use when..." clause or trigger guidance, so completeness is capped at 3 per the rubric guideline for a missing explicit when.	3 / 5
Trigger Term Quality	Only technical jargon ("centralized configuration management", "feature flags", "dynamic refresh") with no natural user phrases like "Azure App Configuration", "app config", or "config refresh", matching anchor 2 for missing the natural phrases users say.	2 / 5
Distinctiveness Conflict Risk	"Centralized configuration management with feature flags and dynamic refresh" is somewhat specific to app config but lacks Azure-specific triggers and could overlap with other config skills, matching anchor 3.	3 / 5
	Total	11 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-appconfiguration-ts/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.