BC microsoft-docs
Запрашивайте официальную документацию Microsoft, чтобы находить концепции, учебники и примеры кода по Azure, .NET, Agent Framework, Aspire, VS Code, GitHub и другим. Используется Microsoft Learn MCP по умолчанию, а для контента, размещённого вне learn.microsoft.com, — Context7 и Aspire MCP.
The skill connects Microsoft's official documentation via MCP servers: Microsoft Learn, Context7, and Aspire. It promises access to concepts, tutorials, and code examples for Azure, .NET, Agent Framework, VS Code, and GitHub.
One file, no scripts, 1770 body tokens. No critical errors found, lint is clean. Content quality rated 74, process score 55. Security at maximum. Works across platforms from Claude to DeepSeek.
Worth installing. The skill does exactly what it says: plugs in the docs. Useful if you frequently need Microsoft examples and references pulled into your agent. Promises nothing fancier, requires nothing fancier either.
Запрашивайте официальную документацию Microsoft, чтобы находить концепции, учебники и примеры кода по Azure, .NET, Agent Framework, Aspire, VS Code, GitHub и…
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1770 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +3Description length 291: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (1 code blocks)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.