CtrlK
BlogDocsLog inGet started
Tessl Logo

m365-entra-attack

Microsoft 365 / Entra ID red-team attack chain — current 2026 reality. AADSTS code reference, user enumeration vectors (with hardening status), Smart Lockout math, Conditional Access bypass options, ROPC + SAML SSO browser flow, Burp/Playwright templates. Built from authorized red-team work where ROPC spray surfaced pre-existing lockouts and CA-blocked credentials, plus real-time external attacker activity correlation. Use for any M365/Entra credential attack, password spray, user enumeration, CA-bypass exploration, or active-attacker-detection scenario.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with strong workflow checkpoints and specialized, non-obvious detail that earns its place, but it is over-long for a SKILL.md and keeps all code/reference material inline with no bundle-file offloading. Conciseness and progressive disclosure are the weak dimensions.

Suggestions

Move the full ROPC validator and SAML Playwright scripts plus the AADSTS code-reference table into reference files (e.g. references/aadsts-codes.md, references/ropc-validator.py, references/saml-flow.py) and keep SKILL.md as an overview with one-level-deep links, raising progressive_disclosure.

Trim engagement storytelling (the live '183 false AADSTS50053 in 15s' anecdote, the '2026-05-17 re-verification' narratives, 'Killer use case' / 'Red flag' dramatic callouts) down to the actionable rule each illustrates, raising conciseness without losing guidance.

DimensionReasoningScore

Conciseness

Much of the body is genuinely specialized knowledge Claude lacks (AADSTS semantics, Smart Lockout thresholds, the access_token substring trap), but it is padded with engagement anecdotes, dramatic callouts, and repeated '2026-05-17 re-verification' narratives that could be tightened — matching the 'mostly efficient but includes some unnecessary explanation' anchor.

2 / 3

Actionability

Provides fully executable Python (ROPC validator, SAML Playwright flow), concrete HTTP requests, specific client_ids, an AADSTS reference table, and exact commands — copy-paste ready, matching the top anchor.

3 / 3

Workflow Clarity

Sequenced discovery→spray→validation→report pipeline with explicit checkpoints for the risky batch operation (hard cap, atomic state writes, kill-switch on >~5 AADSTS50053, 'NEVER use concurrency' hard rule, diagnose-before-continue feedback loop), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Sections are well-organized with clear headers and a cross-skill 'Related Skills & Chains' map, but no bundle files exist and ~380 lines of full scripts, code tables, and reference material sit inline in a single monolith — matching the 'content that should be separate is inline' anchor rather than the top level.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and clearly niched, naming concrete actions and explicit use-scenarios in third-person voice. It is slightly verbose with engagement backstory, but no description rubric dimension penalizes that and all four anchors land at the top level.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'AADSTS code reference, user enumeration vectors (with hardening status), Smart Lockout math, Conditional Access bypass options, ROPC + SAML SSO browser flow, Burp/Playwright templates' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (the capability inventory) and when (an explicit 'Use for...' clause with named scenarios), satisfying the top anchor.

3 / 3

Trigger Term Quality

The 'Use for any M365/Entra credential attack, password spray, user enumeration, CA-bypass exploration, or active-attacker-detection scenario' clause covers natural terms a red-team operator would actually say.

3 / 3

Distinctiveness Conflict Risk

A clearly defined M365/Entra red-team niche with distinct triggers ('password spray', 'CA-bypass', 'active-attacker-detection') unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
elementalsouls/Claude-BugHunter
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.