SKILLEMALL.ai
GitHub ↗ RU Sign in

BC microsoft-docs

Запитуйте офіційну документацію Microsoft, щоб знаходити концепції, навчальні посібники та приклади коду щодо Azure, .NET, Agent Framework, Aspire, VS Code, GitHub та іншого. Використовує Microsoft Learn MCP за замовчуванням, а для вмісту, що знаходиться поза learn.microsoft.com, — Context7 та Aspire MCP.

The skillemall take

This skill connects Microsoft's official documentation via MCP servers: Microsoft Learn for core content, Context7 and Aspire MCP for everything else. Promises access to materials on Azure, .NET, Agent Framework, VS Code, and GitHub.

Tests show grade B: content quality 74 points, process score 53 points. No critical errors, no broken links found. Single file, no scripts. Sandbox run didn't happen. Works across all major platforms from Claude to DeepSeek.

Useful if you need Microsoft ecosystem reference without browser search. Downside: relies on three data sources, and sync between them may lag. Worth installing if you frequently hit Microsoft docs.

microsoft/ai-agents-for-beginners Agent Skills author: microsoft MIT 1 file body ≈ 1 708 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Запитуйте офіційну документацію Microsoft, щоб знаходити концепції, навчальні посібники та приклади коду щодо Azure, .NET, Agent Framework, Aspire, VS Code…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubVS CodeAzureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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-when description 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 1708 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
  • +3Description length 306: 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.