SKILLEMALL.ai
GitHub ↗ RU Sign in

CC microsoft-docs

ಅಧಿಕೃತ Microsoft ಡಾಕ್ಯುಮೆಂಟೇಶನ್ ಅನ್ನು ಪ್ರಶ್ನೆ ಮಾಡಿ Azure, .NET, Agent Framework, Aspire, VS Code, GitHub ಮತ್ತು ಇತರೆ ಸಂಬಂಧಿತ ವಿಷಯಗಳ ಮೇಲೆ ತತ್ವಗಳು, ಟ್ಯುಟೋರಿಯಲ್ಗಳು ಮತ್ತು ಕೋಡ್ ಉದಾಹರಣೆಗಳನ್ನು ಕಂಡುಹಿಡಿಯಿರಿ. ಡೀಫಾಲ್ಟ್‌ವಾಗಿ Microsoft Learn MCP ಅನ್ನು ಬಳಸುತ್ತದೆ; learn.microsoft.com ಹೊರಗಿನ ವಿಷಯಗಳಿಗೆ Context7 ಮತ್ತು Aspire MCP ಅನ್ನು ಬಳಸಲಾಗುತ್ತದೆ.

Not recommendedcritical or high security findings
microsoft/ai-agents-for-beginners Agent Skills author: microsoft MIT 1 file body ≈ 1 350 tokens Open the sourcegithub.com↗ analyzed 6 d ago

ಅಧಿಕೃತ 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

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
C
78/100
safety, quality, tests
Safety 60%
82
Quality 40%
72
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

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Obfuscation
If you install

The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.

For the author

Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 1

  • high Obfuscation uni-zero-width SKILL.md:5
    Zero-width / invisible characters (possible hidden text) (16 occurrences)
    ಮತ್ತು ಕೋಡ್ ಉದಾಹರಣೆಗಳನ್ನು ಕಂಡುಹಿಡಿಯಿರಿ. ಡೀಫಾಲ್ಟ್␀ವಾಗಿ Microsoft Learn MCP ಅನ್ನು ಬಳಸುತ್ತದೆ;

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 1350 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 332: 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.