CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-resource-manager-durabletask-dotnet

Azure Resource Manager SDK for Durable Task Scheduler in .NET.

53

Quality

60%

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-claude/skills/azure-resource-manager-durabletask-dotnet/SKILL.md

The canonical home for this skill is azure-resource-manager-durabletask-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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.

The body is a strong, highly actionable ARM reference with executable examples across the common operations. Its main weaknesses are the lack of explicit validation checkpoints around destructive deletes and the absence of any file-based progressive disclosure for the large reference material.

Suggestions

Add an explicit validation/verification step before and after destructive deletes (e.g. confirm the scheduler has no task hubs, then verify deletion succeeded) to lift workflow_clarity above 3.

Move the Key Types reference table and full API/extension-method reference into a separate references file (e.g. REFERENCE.md) and link to it from SKILL.md to improve progressive disclosure.

Trim the Complete Example or convert it to a cross-reference to the numbered workflow steps to reduce redundancy with sections 1, 3, and 7.

DimensionReasoningScore

Conciseness

The body is code-driven with little concept over-explanation, but the Complete Example repeats steps from sections 1, 3, and 7, a minor redundancy that fits anchor 4 rather than the lean anchor 5.

4 / 5

Actionability

Copy-paste-ready, executable C# covers create/list/get/update/delete/retention/private-endpoints/error-handling for the common cases; the only minor gap is the retention example's placeholder comment, still matching anchor 5.

5 / 5

Workflow Clarity

A clear numbered 1-9 sequence with error handling is present, but the destructive delete workflow (section 7) has no explicit validation or verify checkpoint, which the rubric caps at 3 for destructive operations.

3 / 5

Progressive Disclosure

There are no bundle files and ~430 lines are inlined, including a 20-row type table and full API reference that could be split out; section headers give structure but nothing is disclosed to separate files, fitting anchor 3.

3 / 5

Total

15

/

20

Passed

Description

48%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 about the product niche but is essentially an identifier rather than guidance: it states what the SDK is without listing concrete actions or a 'Use when' trigger clause. Adding explicit capabilities and trigger phrases would lift specificity and completeness.

Suggestions

Add concrete actions to the description, e.g. 'Provision and manage Azure Durable Task Scheduler resources — create schedulers, task hubs, and retention policies via ARM.'

Append an explicit 'Use when...' trigger clause such as 'Use when provisioning or managing Azure Durable Task Scheduler resources in .NET.'

Clarify the management-plane scope in the description to reduce overlap with the data-plane SDK (e.g. mention 'management plane').

DimensionReasoningScore

Specificity

The description names the domain precisely ('Azure Resource Manager SDK for Durable Task Scheduler in .NET') but lists no concrete actions such as provision, create, or manage, matching anchor 2; it is not vague enough for 1 and lacks the 1-2 actions needed for 3.

2 / 5

Completeness

It gives a clear 'what' (an ARM SDK for Durable Task Scheduler) but no 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Azure Resource Manager', 'Durable Task Scheduler', and '.NET' are natural phrases a user would say, but no synonyms or variations are present, fitting anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

It names a specific Azure product niche with distinct triggers and minimal conflict risk, but the description does not distinguish the management plane from the related data-plane SDK, leaving minor overlap risk consistent with anchor 4.

4 / 5

Total

12

/

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.