SKILLEMALL.ai

AC azure-mgmt-weightsandbiases-dotnet

Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 645 tokens Open the sourcegithub.com analyzed 26 h ago

Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO…

As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

IntegrationAzureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
98
Quality 40%
81
Run on models
none yet
Process rating
C
62/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-high-entropy-token SKILL.md:163
      High-entropy token-like string (may be an id, hash or a credential)
      upda…sV2 = new Weig…sV2
    • low Secrets in code secret-high-entropy-token SKILL.md:235
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | `Weig…sV2` | SSO configuration |
      table

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 62/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 10 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2645 tokens
    • low 15 top-level sections: this looks like several domains in one skill

    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 196: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 10 items
    • +4Has examples (13 code blocks)

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