CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-rust

Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.

58

Quality

68%

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

The canonical home for this skill is azure-identity-rust in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is well-structured and actionable with executable examples for the main credentials, but it lacks an explicit decision workflow and carries a low-value boilerplate section.

Suggestions

Replace the vague 'When to Use' boilerplate with a concrete credential-selection decision guide (environment → credential).

Add a brief end-to-end sequence (choose credential → instantiate → pass to client → handle token/error) with an explicit checkpoint for verifying authentication succeeded.

Provide code examples for the remaining high-use credentials (e.g., WorkloadIdentityCredential, ClientCertificateCredential) currently only listed in the table.

DimensionReasoningScore

Conciseness

The body is mostly lean with compact tables and clean code, but the vague 'When to Use' boilerplate and the restated intro sentence are minor padding that could be trimmed.

4 / 5

Actionability

Concrete, executable Rust snippets for three credentials plus env-var setup and a cargo command are copy-paste ready, though only 3 of the 9 listed credentials have code examples.

4 / 5

Workflow Clarity

The content is reference-style with a credential selection table and best-practices list, but there is no explicit end-to-end sequence or checkpoints for instantiating and using a credential.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and tables and no nested references, but at ~100 lines all credential deep-dives are inlined where splitting could help.

4 / 5

Total

15

/

20

Passed

Description

67%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 well-targeted with an explicit trigger clause, but its trigger vocabulary leans on credential type names and omits common natural synonyms a user might say.

Suggestions

Add natural-language triggers such as 'Entra ID', 'Azure AD', 'service principal', or 'managed identity' alongside the credential type names.

Make the 'when' clause scenario-oriented (e.g., 'Use when authenticating Azure SDK clients in Rust') rather than only listing credential types.

Mention the remaining common credentials (e.g., WorkloadIdentityCredential, ClientCertificateCredential) to reduce coverage gaps.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete credential types (DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential) plus token-based auth, but covers only 3 of ~9 credentials, leaving minor gaps.

4 / 5

Completeness

A clear 'what' (Azure Identity SDK for Rust authentication) is paired with an explicit 'Use for…' trigger, though the 'when' is tied to credential names rather than concrete usage scenarios.

4 / 5

Trigger Term Quality

The credential type names are relevant SDK-specific triggers, but common natural variations and synonyms (Entra ID, Azure AD, service principal, managed identity) are missing.

3 / 5

Distinctiveness Conflict Risk

The Azure Identity SDK for Rust niche with named credential triggers is mostly distinct, with only minor overlap risk against a broader azure-sdk-for-rust skill.

4 / 5

Total

15

/

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.