CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-pass-the-ticket-attack

Perform Pass-the-Ticket (PtT) lateral movement by extracting Kerberos TGT/TGS tickets from LSASS memory on a compromised host and injecting them into another session to impersonate the ticket owner without knowing their password. Use during authorized post-exploitation to move laterally or escalate access via stolen Kerberos tickets, or to validate detections for Kerberos ticket theft and reuse.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-pass-the-ticket-attack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 body reads as a decent high-level runbook with a clear phase structure, but it stays at summary-level abstraction: steps lack executable commands, validation is a checkbox list without verification methods, and the high-value bundle files (especially the fully executable workflows in references/workflows.md) are never referenced. Duplicated MITRE and detection content inflates tokens without adding guidance.

Suggestions

Link the bundle files from their natural homes — replace the inline MITRE ATT&CK Mapping and Detection Indicators sections with pointers to references/standards.md and references/api-reference.md, and add 'See references/workflows.md for full command workflows' under the Workflow section.

Pull the executable commands from references/workflows.md into the Workflow phases (e.g., the full mimikatz.exe invocations for export/purge/ptt and Rubeus dump/ptt with /ticket:base64) so each step is copy-paste ready instead of a directive.

Make validation concrete: specify `klist` to verify the injected ticket is loaded in Phase 2, and add error-recovery guidance (e.g., what to check if injection fails or the stolen ticket is expired).

DimensionReasoningScore

Conciseness

The Overview ('Pass-the-Ticket (PtT) is a lateral movement technique that uses stolen Kerberos tickets...') re-explains a well-known technique Claude already knows, and the 'When to Use' bullets are circular ('When conducting security assessments that involve conducting pass the ticket attack'). Mostly efficient otherwise, matching anchor 3; not 2 because the padding is confined to these two sections.

3 / 5

Actionability

Workflow steps are directives without commands ('Dump Kerberos tickets from LSASS memory using Mimikatz or Rubeus'), and the tools table gives fragments ('sekurlsa::tickets /export, kerberos::ptt', 'dump, ptt, tgtdeleg') rather than full executable command lines. Some concrete guidance exists (e.g., 'ticketConverter.py ticket.kirbi ticket.ccache'), so it sits above anchor 2, but the fully executable commands in references/workflows.md are never surfaced.

3 / 5

Workflow Clarity

The three phases are clearly sequenced and validation items exist ('Verify ticket is loaded and valid', the final checklist), but checkpoints are implicit — no verification command (e.g., klist) and no error-recovery guidance. Matches anchor 3; not 4 because the checkpoints lack any concrete mechanism or feedback loop.

3 / 5

Progressive Disclosure

The bundle contains references/workflows.md, references/api-reference.md, and references/standards.md, but the body links to none of them, while inlining duplicated content (the MITRE ATT&CK Mapping and Detection Indicators sections mirror standards.md). Anchor 2 fits: content that belongs in separate files is inlined and the bundle references are effectively buried; not 3 because the body contains no references at all.

2 / 5

Total

11

/

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 strong description: it states concrete capabilities in third person and includes an explicit, multi-scenario 'Use when' clause with natural trigger terms. Its only weakness is slightly incomplete keyword coverage — no tool names like Mimikatz or file extensions like .kirbi that a user might naturally mention.

DimensionReasoningScore

Specificity

Quotes: 'extracting Kerberos TGT/TGS tickets from LSASS memory', 'injecting them into another session', 'impersonate the ticket owner without knowing their password' — multiple concrete actions covering extraction, injection, impersonation, lateral movement, and detection validation. Anchor 5 fits; anchor 4 ('minor gaps in coverage') understates it since every phase of a PtT operation is named.

5 / 5

Completeness

'Perform Pass-the-Ticket (PtT) lateral movement by extracting... and injecting...' answers what, and 'Use during authorized post-exploitation to move laterally or escalate access via stolen Kerberos tickets, or to validate detections for Kerberos ticket theft and reuse' is an explicit when-clause with concrete trigger scenarios. Both are explicit; not 4 because the when-clause is specific and multi-scenario rather than generic.

5 / 5

Trigger Term Quality

Natural terms like 'Pass-the-Ticket (PtT)', 'stolen Kerberos tickets', 'move laterally', and 'ticket theft and reuse' are present with synonyms, but a few natural phrases users might say are missing (e.g., 'Mimikatz', 'golden/silver ticket', '.kirbi'). Anchor 4 ('good keyword coverage; a few natural terms missing') is the best fit; anchor 5 requires comprehensive synonym and file-extension coverage this does not reach.

4 / 5

Distinctiveness Conflict Risk

Pass-the-Ticket is a narrowly named MITRE sub-technique with distinct triggers ('Kerberos TGT/TGS tickets', 'LSASS memory', 'pass-the-ticket'), making it unlikely to fire for unrelated skills. Not 4: it names its niche explicitly rather than merely overlapping with adjacent Kerberos attack 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/conducting-pass-the-ticket-attack/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.