Name: azure-mgmt-botservice-dotnet
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings.

Quality

61%

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

The canonical home for this skill is azure-mgmt-botservice-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

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 body is highly actionable with fully executable workflows and clean structure, but inline version/date info hurts conciseness and destructive operations lack validation checkpoints that cap workflow clarity. Inlining reference material rather than splitting it into bundle files limits progressive disclosure.

Suggestions

Add explicit validation/pre-confirmation checkpoints before destructive operations (e.g., verify the bot exists and confirm before deleting; check for 409 conflict before create) to lift workflow clarity above 3.

Move inline version numbers and the date into a dedicated 'Versions / lifecycle' or deprecated-patterns section so they do not penalize conciseness.

Extract the channel-type, key-type, and enum-value reference tables plus the reference-links table into a separate references file (e.g., references/types.md) linked one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient code and tables with no conceptual padding, but inline time-sensitive version info ('Stable v1.1.1, Preview v1.1.0-beta.1') and the date_added field penalize conciseness since they are not placed in a deprecated/old-patterns section.	3 / 5
Actionability	Eight complete, copy-paste-ready C# workflows (create, channel config for DirectLine/Teams/Web Chat, get/list, regenerate keys, update, delete) with full type names cover the common cases comprehensively.	5 / 5
Workflow Clarity	Workflows are clearly numbered and sequenced with an error-handling section, but the destructive Delete Bot workflow and CreateOrUpdate lack explicit validation/verification checkpoints, which caps workflow clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Sections are well-organized but no bundle files exist and all reference material (channel type table, key types, enum values, reference links) is inlined in a ~330-line file rather than split into separate one-level-deep reference files.	3 / 5
	Total	14 / 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 clearly states what the SDK does and names concrete capabilities with specific channels, but it lacks an explicit 'Use when...' trigger clause and has only moderate natural-term coverage. It is distinctive but capped by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when provisioning Azure Bot Service resources, configuring DirectLine/Teams channels, or managing bot connection settings').

Broaden trigger-term coverage with synonyms and file/SDK cues users naturally say, such as 'Azure bot channels', 'DirectLine configuration', and the NuGet package name.

Mention additional concrete actions surfaced in the body (list channels, regenerate DirectLine keys, update/delete bots) to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings') with specific channel names, though it omits actions like listing, key regeneration, and deletion present in the body.	4 / 5
Completeness	Has a clear 'what' (management plane operations for bot resources, channels, connection settings) but no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant technical terms ('Azure Resource Manager SDK', 'Bot Service', 'Teams, DirectLine, Slack') but misses natural variations users might say ('bot channels', 'DirectLine config', 'Azure bot setup').	3 / 5
Distinctiveness Conflict Risk	The 'Azure Resource Manager SDK for Bot Service in .NET' niche is distinct from general bot-building skills, with only minor overlap risk against Microsoft.Bot.Builder.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-mgmt-botservice-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 16 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.