azure-keyvault-secrets-ts

Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.

Quality

60%

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-keyvault-secrets-ts/SKILL.md

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill suffers from significant scope creep - it's described as a Secrets SDK skill but includes extensive Keys and Cryptography content that doubles its length unnecessarily. The code examples are generally good and executable (with one import bug), but the lack of validation workflows for destructive operations and the monolithic structure weaken it considerably.

Suggestions

Remove or split the Keys Operations, Cryptographic Operations, and Wrap/Unwrap sections into a separate keyvault-keys skill file, keeping this focused on secrets only.

Fix the Authentication section: remove the unused `KeyClient` instantiation or add the proper import from @azure/keyvault-keys.

Add a validation step after setSecret (e.g., immediately getSecret to confirm it was stored correctly) and a check before purgeDeletedSecret to confirm intent.

Remove the 'When to Use' section which adds no value, and trim the Best Practices to only secrets-relevant items.

Dimension	Reasoning	Score
Conciseness	The skill is significantly bloated - it includes extensive Keys and Cryptographic Operations sections that are unrelated to the stated purpose (Azure Key Vault Secrets SDK). The description says 'Manage secrets using Azure Key Vault Secrets SDK' but over half the content covers keys, encryption, signing, and wrapping. The 'Best Practices' section also explains obvious concepts. The 'When to Use' section is a meaningless tautology.	2 / 5
Actionability	The code examples are concrete and mostly executable. However, there's a bug in the Authentication section where `KeyClient` is used but never imported (only `SecretClient` is imported from keyvault-secrets). The examples cover common operations with copy-paste ready code.	4 / 5
Workflow Clarity	The delete operations show the poller pattern (soft delete -> poll -> purge), which is good. However, there's no validation or error-checking workflow for destructive operations like purge. The skill lacks guidance on verifying secret was set correctly or checking vault state before purging. Since purge is a destructive/permanent operation, the missing validation caps this at 3.	3 / 5
Progressive Disclosure	The content is a monolithic wall of code examples with no references to external files. The Keys and Cryptography sections (which don't belong in a Secrets skill) should either be removed or split into a separate file. There's no navigation structure beyond flat section headers, and the content that's included is far too much for a single SKILL.md.	2 / 5
	Total	11 / 20 Passed

Description

73%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.

This is a reasonably well-crafted description that clearly identifies its technology niche (Azure Key Vault Secrets SDK for JavaScript) and includes an explicit 'Use when' clause. Its main weaknesses are limited specificity in the actions it covers (only 'storing and retrieving') and missing some natural trigger terms users might use when needing this skill (e.g., 'credentials', 'API keys', 'sensitive data').

Suggestions

Expand the list of concrete actions beyond 'storing and retrieving' to include operations like listing, deleting, purging, updating secret properties, and setting expiration dates.

Add more natural trigger terms and synonyms such as 'credentials', 'API keys', 'passwords', 'sensitive data', or 'environment variables' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure Key Vault Secrets) and mentions two concrete actions ('storing and retrieving'), but doesn't list more specific operations like listing secrets, deleting, purging, updating properties, or setting expiration dates.	3 / 5
Completeness	Has both 'what' (manage secrets using Azure Key Vault Secrets SDK) and 'when' ('Use when storing and retrieving application secrets or configuration values'). The 'when' clause is present but could be more specific with additional trigger scenarios.	4 / 5
Trigger Term Quality	Includes good trigger terms like 'secrets', 'Azure Key Vault', '@azure/keyvault-secrets', 'application secrets', and 'configuration values'. However, it's missing natural variations like 'credentials', 'API keys', 'passwords', 'sensitive data', or 'secret management'.	4 / 5
Distinctiveness Conflict Risk	Very distinct niche — specifically targets Azure Key Vault Secrets SDK for JavaScript with the exact package name. Unlikely to conflict with other skills due to the precise technology and SDK specification.	5 / 5
	Total	16 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-keyvault-secrets-ts/SKILL.md
Commit: fbdfd63

Reviewed: 2 days 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.