SKILLEMALL.ai

BB auditing-azure-active-directory-configuration

Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 4 files · 1 script body ≈ 2 816 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale…

As a process B 66/100 · Nearly there — weak spots: failures and branches, progress reporting

AnalyzerAzureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
B
66/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"
    • note edit-residue the text marks something as outdated (lines 26, 41, 148, 175, 177, 199): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 66/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 22 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2816 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
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 270: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 22 items
    • +3Output format is stated explicitly
    • +4Has examples (7 code blocks)
    • +1License stated

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