SKILLEMALL.ai
GitHub ↗ RU Sign in

CF azure-files

Expert knowledge for Azure Files development including best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when planning Azure File shares, File Sync tiering, NFS/SMB migrations, DR topologies, or RAG integrations, and other Azure Files related development tasks. Not for Azure Blob Storage (use azure-blob-storage), Azure NetApp Files (use azure-netapp-files), Azure Managed Lustre (use azure-managed-lustre), Azure Virtual Machines (use azure-virtual-machines).

MicrosoftDocs/Agent-Skills Agent Skills author: MicrosoftDocs CC-BY-4.0 1 file body ≈ 4 890 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Expert knowledge for Azure Files development including best practices, decision making, limits & quotas, security, configuration, integrations & coding…

As a process F 32/100 · No process to follow — References files that are not bundled: security.md

GeneratorAzureInfrastructuretype 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
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
75
Run on models
none yet
Process rating
F
32/100
No process to follow
References files that are not bundled: security.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Concealment medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. The text references files that are not there: add them or drop the references.
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

✓ No critical or high findings

Medium and low: 1
  • medium Concealment en-hide-from-user SKILL.md:115
    Instruction to hide actions from the user (documentation of a security skill)
    | Silently install the Azure File Sync agent | https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-agent-silent-installation |
    security skill

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: security.md

Process rating: all ten parameters 32/100

Will not run. References files that are not bundled: security.md
  • 0Tools and files. 1 referenced file(s) missing: security.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 14 mutating operations with no state check
  • 50Steps. 2 steps
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Execution cost. Instruction body is 4890 tokens
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 538: enough signal without eating the budget
  • +4Structure: 10 headings

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.