CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-appconfiguration-java

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

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-appconfiguration-java/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable and token-efficient, but it functions as a monolithic API catalog with no multi-step validation guidance for destructive ops and no use of separate reference files despite its length.

Suggestions

Add explicit validation/verification steps around destructive operations (e.g. confirm an ETag or check getConfigurationSetting returns null before delete) so workflow_clarity can exceed 3.

Move the bulk operation reference (CRUD, feature flags, snapshots) into a separate REFERENCE.md and have SKILL.md point to it one level deep, improving progressive_disclosure.

Complete the snapshot example by including the missing imports (java.util.List, java.util.ArrayList, java.time.Duration) so all code blocks are copy-paste ready.

DimensionReasoningScore

Conciseness

Prose is lean and almost entirely code-driven with no padding about basic concepts; the two installation methods and the Key Concepts table add minor redundancy that could be trimmed, so it sits above the midpoint but short of a fully lean 5.

4 / 5

Actionability

Provides concrete, copy-paste-ready Java across CRUD, feature flags, secret references, snapshots, async, and error handling; the snapshot example references List/ArrayList/Duration without their imports, a minor gap keeping it below 5.

4 / 5

Workflow Clarity

The body is a reference catalog rather than a sequenced workflow, and destructive operations (delete, archive) are shown without any validation or verification step, which caps workflow_clarity at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but roughly 465 lines of API reference are inlined entirely in SKILL.md with no bundle files and no split into separate reference files, matching the anchor for content that should be separate but is inline.

3 / 5

Total

14

/

20

Passed

Description

70%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, distinct, and uses third-person voice with good trigger terms, but it omits any explicit 'Use when...' guidance, leaving the 'when' half of completeness unaddressed.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working with Azure App Configuration in Java, managing key-value settings, feature flags, or configuration snapshots.'

Include a few more natural synonyms (e.g. 'config', 'App Configuration store', 'feature management') to broaden trigger-term coverage.

Optionally enumerate a couple more concrete actions (e.g. 'list and filter settings', 'optimistic concurrency with ETags') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('Azure App Configuration SDK for Java') and lists several concrete capabilities — 'key-value settings, feature flags, and snapshots' — which matches the anchor for several specific actions with minor coverage gaps; not a 5 because the action list is terse rather than comprehensive.

4 / 5

Completeness

Clearly answers 'what' ('Centralized application configuration management with key-value settings, feature flags, and snapshots') but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('application configuration', 'feature flags', 'snapshots', 'Java') with good coverage; not a 5 because synonyms/extensions like 'config', 'App Configuration store', or 'feature management' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'Azure App Configuration SDK for Java' framing carves a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.