CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-managed-identity

Azure Managed Identity abuse — IMDS at 169.254.169.254 from compromised VM / App Service / Function, token exchange for Graph/ARM/KeyVault, federated workload identity abuse, hybrid AAD Connect MSOL credential extraction.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/cloud/azure-managed-identity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

A dense, command-first reference that is largely copy-paste actionable and free of padding. Its weaknesses are the absence of validation checkpoints in the token-theft-to-pivot flow, a few undefined variables and one half-finished code block (AAD Connect), and no progressive-disclosure split as subtopics accumulate.

Suggestions

Add a lightweight verification step after token theft, e.g. check `jq -r .access_token` is non-empty and probe `az rest`/ARM with a harmless GET before pivoting, plus guidance to enumerate assigned MI roles before requesting each audience.

Define or annotate the placeholder variables ($SUB, $VAULT_NAME, $TENANT, $CLIENT_ID) inline so every snippet is fully copy-paste ready, and either complete or remove the orphaned AesManaged line in the AAD Connect block.

Consider moving the pivot-pattern table, workload identity, and AAD Connect sections into one-level-deep reference files to keep SKILL.md a lean overview as the skill grows.

DimensionReasoningScore

Conciseness

The body is lean: executable commands, two compact tables, and one-line setup prose with no explanation of concepts Claude already knows. It falls short of the level-5 "every token earns its place" anchor due to the dead `$key = (New-Object System.Security.Cryptography.AesManaged).Key` line that serves no purpose and the redundant double attribution "MicroBurst (NetSPI), MicroBurst-Cloud (Karl Fosaaen)", which is trimmable noise rather than the padded explanation of the level-3 anchor.

4 / 5

Actionability

Concrete copy-paste-ready curl/PowerShell covers Linux VM, Windows VM, App Service, ARM enumeration, Key Vault secret access, and the federated STS token exchange. Minor gaps keep it below level 5: `$SUB`, `$VAULT_NAME`, `$TENANT`, and `$CLIENT_ID` are used but never defined, and the AAD Connect block replaces real steps with a bare `Get-AADIntSyncCredentials` call assuming an unexplained module.

4 / 5

Workflow Clarity

A logical sequence is implied by section order (steal token → pick audience → use token → pivot), matching the level-3 anchor of "steps listed but validation gaps". There are no checkpoints at all — no step to verify the token before use, no check of which MI assignments exist before requesting audiences, no error handling for failed token requests — so the level-4 anchor (most checkpoints present) does not fit.

3 / 5

Progressive Disclosure

A single-file skill with clear section headers, well-organized tables, and no nested or dangling references; the ~95 lines of commands are appropriately kept inline. It sits at level 4 rather than 5 because distinct subtopics (pivot patterns, workload identity, AAD Connect, OPSEC) are moderately sized and could be split into one-level-deep reference files, and no reference structure is offered despite the content having grown past a simple single-purpose skill.

4 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

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

A dense, highly specific description that accurately enumerates the skill's capabilities with strong niche distinctiveness. Its main weakness is the missing "Use when..." trigger clause, which caps completeness, and slightly incomplete synonym coverage for trigger terms.

Suggestions

Append an explicit trigger clause, e.g. "Use when enumerating or abusing Azure managed identities, IMDS endpoints, or hybrid AAD Connect credentials after initial access."

Add common synonyms such as "MSI", "instance metadata service", and "managed identity token" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions spanning the skill's full scope: "IMDS at 169.254.169.254 from compromised VM / App Service / Function", "token exchange for Graph/ARM/KeyVault", "federated workload identity abuse", and "hybrid AAD Connect MSOL credential extraction". This matches the comprehensive-coverage anchor; each phrase maps to a concrete capability also present in the body, so the level-4 anchor (several actions with coverage gaps) is a worse fit.

5 / 5

Completeness

The "what" is clear and concrete (IMDS token theft, token exchange, workload identity abuse, MSOL extraction), but the description contains no "Use when..." clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. It is not a 4 because the "when" is entirely absent rather than merely implicit or under-specified.

3 / 5

Trigger Term Quality

Natural terms a practitioner would say are present ("Azure Managed Identity", "IMDS", "workload identity", "AAD Connect", "MSOL"), giving good keyword coverage. It falls short of the level-5 anchor because common synonyms such as "MSI", "instance metadata", or "managed identity token theft" are absent, but it clearly exceeds level 3 (relevant keywords with missing variations).

4 / 5

Distinctiveness Conflict Risk

"Azure Managed Identity abuse — IMDS ... Graph/ARM/KeyVault ... AAD Connect MSOL" carves out a clear niche with distinct triggers, explicitly Azure-branded and distinguishable from AWS/GCP IMDS or generic credential skills. Minimal conflict risk, matching the level-5 anchor.

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/cloud/azure-managed-identity/SKILL.md

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.