azure-appconfiguration-java

Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.

Quality

58%

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-java/SKILL.md

Quality

Content

58%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 skill body is highly actionable with executable Java examples across the full operation surface, but it is long, lacks validation checkpoints for destructive operations, and inlines a large API reference rather than using progressive disclosure via separate bundle files.

Suggestions

Add validation checkpoints and feedback loops for destructive/batch operations (e.g., verify a setting exists before delete, confirm snapshot status is 'ready' before archive/recover).

Move the bulk operation reference into separate bundle files (e.g., references/snapshots.md, references/feature-flags.md) and keep SKILL.md as a concise overview pointing to them.

Fix the snapshot example's missing imports (ArrayList, List, Duration) and replace the undefined 'connectionString' variable in async sections with the env var used elsewhere.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight section headers and minimal concept padding, but the body is ~470 lines and inlines a near-complete API reference (every CRUD, list, filter, snapshot, async, error pattern) that could be trimmed or offloaded, and a hardcoded version ('1.8.0') without a deprecation context penalizes conciseness.	3 / 5
Actionability	Nearly every section provides copy-paste-ready Java code with real method names and parameters covering common cases; minor gaps include a missing import for ArrayList/List/Duration in the snapshot example and an undefined 'connectionString' variable in async sections.	4 / 5
Workflow Clarity	Operations are grouped into clear sections, but destructive/batch operations (delete, setReadOnly, archive/recover snapshots) lack explicit validation checkpoints or feedback loops, and the snapshot creation flow omits status/ETag verification before proceeding, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	The body has good section structure, but no bundle files (references/, scripts/, assets/) exist and the bulk API reference is inlined in SKILL.md rather than split into separate one-level-deep reference files, so content that should be separate stays inline.	3 / 5
	Total	13 / 20 Passed

Description

58%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 distinct, clearly identifying the Azure App Configuration Java SDK and its core capabilities. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add a 'Use when...' clause naming natural user triggers, e.g., 'Use when working with Azure App Configuration in Java, managing feature flags, or centralizing app settings.'

Include common synonyms or file/artifact terms users might say (e.g., 'app config', 'feature flag management') to improve trigger-term coverage.

Optionally mention labels or secret references to round out the capability list from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure App Configuration SDK for Java') and several concrete capabilities — 'key-value settings, feature flags, and snapshots' — with only minor coverage gaps (e.g., labels, read-only, secret references).	4 / 5
Completeness	Clearly states what the skill does ('Centralized application configuration management with key-value settings, feature flags, and snapshots') but provides no 'when to use it' trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Uses relevant technical terms ('configuration management', 'feature flags', 'snapshots') but lacks the natural phrases a user would actually say and has no 'Use when...' clause; missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The Azure-specific Java SDK framing ('Azure App Configuration SDK for Java') carves a clear niche with minimal overlap risk against non-Azure or non-Java configuration 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/antigravity-awesome-skills
Path: skills/azure-appconfiguration-java/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.