SKILLEMALL.ai

BC auditing-entra-id-with-aadinternals

Drive the AADInternals PowerShell toolkit to perform Microsoft Entra ID tenant reconnaissance, access-token acquisition across Microsoft APIs, and federation/AD FS backdoor testing (Golden SAML, T1606.002) for defensive validation. Use during an authorized Entra ID/Microsoft 365 red-team assessment to map external attack surface or verify AD FS signing certs resist Golden SAML.

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

Drive the AADInternals PowerShell toolkit to perform Microsoft Entra ID tenant reconnaissance, access-token acquisition across Microsoft APIs, and…

As a process C 60/100 · Has gaps — weak spots: result and completion, failures and branches

AnalyzerAzureGitHubInfrastructureMarketingSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
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: 5. 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 81): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 23 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2510 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    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
    • -42 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
    • +3Description length 380: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 23 items
    • +4Has examples (7 code blocks)
    • +1License stated

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