CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coercing-authentication-with-coercer-petitpotam

Trigger machine account authentication with PetitPotam (MS-EFSR) and Coercer (MS-RPRN, MS-DFSNM, MS-FSRVP, MS-EVEN) via Coercer's scan/coerce/fuzz modes, feeding the coerced NTLM auth into a relay against AD CS Web Enrollment (ESC8), LDAP (RBCD), or SMB. Use in authorized engagements to complete a coercion-relay chain against a Domain Controller, or to validate coercion detections and signing/EPA mitigations.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The skill body is highly actionable, with copy-paste-ready commands and a coherent scan-relay-coerce workflow validated by a criteria checklist. Its main weaknesses are a lack of progressive disclosure — bundle reference files and the agent.py script are never referenced while their content is partially duplicated inline — and mild verbosity from concept re-explanation and redundant tables.

Suggestions

Add explicit one-level-deep pointers to the bundle files (e.g. 'Full flag reference: see references/api-reference.md; MITRE/NIST mapping: see references/standards.md; automation wrapper: scripts/agent.py') and remove the inlined 'Coercion Method Reference' and MITRE tables that duplicate them.

Embed inline validation checkpoints between steps — after Step 3 confirm the coerced authentication arrived at the relay listener, and after Step 5 verify dc.pfx authenticates before DCSync — instead of only a terminal checklist.

Trim the Overview's explanation of what forced authentication and NTLM relay are (Claude already knows these) down to the tool- and method-specific facts.

DimensionReasoningScore

Conciseness

The body is mostly command-dense and efficient, but includes unnecessary material: an Overview that re-explains forced-authentication/NTLM-relay concepts Claude already knows, and redundant tables ('Coercion Method Reference', 'Tools and Resources', MITRE table) whose content duplicates both the Overview text and references/api-reference.md and references/standards.md. Not score 2 because there is no fluffy library-comparison padding and the bulk is executable commands; not score 4 because the concept re-explanation and table duplication are trimmable overhead.

3 / 5

Actionability

Every workflow step provides copy-paste-ready commands with real flags and placeholders explained inline: 'coercer scan -u ... -t 10.0.0.10 -l 10.0.0.50', 'certipy relay -target http://CA.CORP.LOCAL -template DomainController', 'impacket-ntlmrelayx -t http://CA.CORP.LOCAL/certsrv/certfnsh.asp -smb2support --adcs', plus install commands in Prerequisites. Not score 4 because the examples cover the common cases (scan, coerce, filter, fuzz, ESC8 relay, RBCD relay) completely and would run as written.

5 / 5

Workflow Clarity

A clear 7-step sequence (scan → relay → coerce → use result → alternative chains) with a terminal 'Validation Criteria' checklist covering each objective. Not score 5 because validation lives only in an end-of-document checklist rather than inline checkpoints or feedback loops — e.g. no 'confirm the coerced auth hit the listener before running certipy auth' step and no recovery guidance when a coercion attempt fails. Not score 3 because the sequence is coherent, checkpoints are enumerated, and each step states its purpose and preconditions.

4 / 5

Progressive Disclosure

The bundle provides references/api-reference.md (full flag reference), references/standards.md (MITRE/NIST mapping), and scripts/agent.py, but the body never points to any of them — no 'See references/api-reference.md' navigation exists. Instead it inlines duplicate content (method tables, command examples also present in api-reference.md, MITRE mapping duplicated in standards.md), leaving the reference files orphaned and the reader without navigation. Not score 2 because the body itself is well-sectioned and the inlined material is compact, but signaling references and moving the duplicated detail would lift it to 4.

3 / 5

Total

15

/

20

Passed

Description

92%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 high-quality description: it states concrete capabilities (tools, protocols, modes, relay targets) and an explicit authorization-scoped 'use when' clause covering both offensive and defensive-validation use cases. The only weakness is a few missing synonyms ('forced authentication', 'PrinterBug', 'DFSCoerce', 'ntlmrelayx') that could broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names multiple concrete actions with comprehensive coverage: 'Trigger machine account authentication with PetitPotam (MS-EFSR) and Coercer (MS-RPRN, MS-DFSNM, MS-FSRVP, MS-EVEN) via Coercer's scan/coerce/fuzz modes, feeding the coerced NTLM auth into a relay against AD CS Web Enrollment (ESC8), LDAP (RBCD), or SMB.' Tools, protocols, modes, and relay targets are all explicit. Not score 4 because there are no meaningful coverage gaps; the action set is complete for this technique chain.

5 / 5

Completeness

Both 'what' and 'when' are explicitly answered: what — trigger machine-account authentication via named RPC methods and relay it to ESC8/LDAP/SMB; when — 'Use in authorized engagements to complete a coercion-relay chain against a Domain Controller, or to validate coercion detections and signing/EPA mitigations.' This is an explicit 'Use when...' equivalent with concrete trigger contexts. Not score 4 because the 'when' clause is already specific (engagement chain vs. detection/mitigation validation), not merely serviceable.

5 / 5

Trigger Term Quality

Strong natural keywords a user would actually say: 'PetitPotam', 'Coercer', 'ESC8', 'NTLM auth', 'relay', 'RBCD', 'Domain Controller', 'signing/EPA mitigations'. Not score 5 because common synonyms users may say are missing — e.g. 'forced authentication', 'PrinterBug'/'SpoolSample', 'DFSCoerce'/'ShadowCoerce', 'ntlmrelayx', 'Certipy' — leaving a few trigger variations uncovered. Not score 3 because coverage goes well beyond a bare domain mention, hitting both tool names and technique outcome terms.

4 / 5

Distinctiveness Conflict Risk

The named tools (PetitPotam, Coercer) and the coercion-to-relay-to-ESC8 chain define a clear niche with distinct triggers unlikely to collide with other skills. Not score 4 because the unique tool names and the specific chained outcome (ESC8/RBCD relay) leave minimal overlap risk with generic NTLM-relay or AD-CS skills.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/coercing-authentication-with-coercer-petitpotam/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.