azure-appconfiguration-ts

Centralized configuration management with feature flags and dynamic refresh.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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.

Highly actionable, executable TypeScript reference with good conciseness, but it inlines a large amount of API material in one file rather than splitting it into one-level-deep references, and destructive operations lack validation checkpoints.

Suggestions

Split the heavier reference sections (Snapshots, Labels, Feature Flags) into separate files under references/ and link to them from SKILL.md, leaving a lean overview with quick-start examples inline.

Add explicit validation/verification steps around destructive operations, e.g. confirm a setting exists before deleteConfigurationSetting, and verify setReadOnly took effect by re-reading the setting.

Trim the inline 'Key Types' import catalog, which mostly restates package surfaces, or move it into a dedicated reference file.

Dimension	Reasoning	Score
Conciseness	The body is dense and code-forward with brief comments and almost no conceptual padding Claude already knows, but a large inlined API reference (CRUD, provider, feature flags, snapshots, labels) could be trimmed or split, keeping it just short of the lean anchor at 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript covering the common cases (CRUD, optimistic concurrency, dynamic refresh, feature flags, snapshots, labels), matching the comprehensive executable anchor.	5 / 5
Workflow Clarity	Sections are well organized but destructive/batch operations (delete, setReadOnly) lack explicit validation checkpoints; per the guidelines, missing validation for destructive operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single ~350-line file inlines substantial API reference that belongs in separate reference files, and no references/scripts/assets bundle exists; structure is present but content that should be split is inline, matching the anchor at 3.	3 / 5
	Total	15 / 20 Passed

Description

50%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 'what' with two concrete capabilities but omits any 'when to use' trigger guidance, capping completeness at 3. Trigger terms are relevant but lack natural synonyms users would say.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when managing Azure App Configuration, feature flags, or dynamic app settings').

Include natural synonyms a user might say, such as 'app config', 'feature toggles', and 'configuration settings', not just technical terms.

Mention 'Azure App Configuration' explicitly to sharpen distinctiveness and reduce overlap with generic config skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('configuration management') and two concrete capabilities ('feature flags' and 'dynamic refresh'), but coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the several-action anchor at 4.	3 / 5
Completeness	Provides a clear 'what' but no 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant technical keywords ('feature flags', 'dynamic refresh', 'configuration management') but misses natural user phrasings and synonyms (e.g. 'app config', 'feature toggles', 'config settings') and any file/extension cues.	3 / 5
Distinctiveness Conflict Risk	'Centralized configuration management' is somewhat specific but, without naming Azure or a distinct niche, could overlap with other configuration-management skills.	3 / 5
	Total	12 / 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-ts/SKILL.md
Commit: 1f67c44

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