CC microsoft-docs
سرکاری Microsoft دستاویزات میں استفسار کریں تاکہ Azure، .NET، Agent Framework، Aspire، VS Code، GitHub، اور دیگر میں موجود تصورات، ٹیوٹوریلز، اور کوڈ کی مثالیں تلاش کی جا سکیں۔ ڈیفالٹ کے طور پر Microsoft Learn MCP استعمال کیا جاتا ہے، جبکہ learn.microsoft.com کے باہر موجود مواد کے لیے Context7 اور Aspire MCP استعمال ہوتے ہیں۔
The skill promises search through official Microsoft documentation — Azure, .NET, Agent Framework, Aspire, VS Code, and GitHub. It claims to use Microsoft Learn MCP by default, with Context7 and Aspire MCP for content outside learn.microsoft.com.
Tests show a C grade with quality_score 72. No critical errors, but process_score sits at 53 — routing logic between MCP sources needs work. Single file, no scripts. The skill runs across wide platform support: Claude, Cursor, Copilot, DeepSeek, and seven others.
For documentation lookup this works, but answer quality depends on how well the skill switches between sources. Install if you need quick access to Microsoft examples without extra steps.
سرکاری Microsoft دستاویزات میں استفسار کریں تاکہ Azure، .NET، Agent Framework، Aspire، VS Code، GitHub، اور دیگر میں موجود تصورات، ٹیوٹوریلز، اور کوڈ کی…
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 1287 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 327: 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.