CC microsoft-docs
Poizvedujte v uradni Microsoftovi dokumentaciji, da poiščete koncepte, vodiče in primere kode za Azure, .NET, Agent Framework, Aspire, VS Code, GitHub in še več. Privzeto uporablja Microsoft Learn MCP, za vsebino, ki se nahaja zunaj learn.microsoft.com, pa Context7 in Aspire MCP.
Skill offers search across Microsoft's official docs: Azure, .NET, Agent Framework, Aspire, VS Code, GitHub. Uses Microsoft Learn MCP by default, Context7 and Aspire MCP for content outside learn.microsoft.com.
Quality score of 72 against process score of 53 hints at reproducibility issues. No critical findings, but sandbox testing didn't run. One file, no scripts. Safety checks pass. Works across all major platforms including Claude, Cursor, and local variants.
Install if you need quick Microsoft documentation access from your agent. Without sandbox verification, though, it's unclear how well MCP integration handles real-world queries.
Poizvedujte v uradni Microsoftovi dokumentaciji, da poiščete koncepte, vodiče in primere kode za Azure, .NET, Agent Framework, Aspire, VS Code, GitHub in še…
As a process C 53/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 53/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
- 0Progress reporting. Says nothing while it works
- 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 1367 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +3Description length 280: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.