CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

evilginx2-proxy

Author and deploy an evilginx2 phishlet to reverse-proxy a real login and capture the post-authentication session cookie, defeating MFA via session-token theft.

Quality

77%

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/phisher/evilginx2-proxy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 lean, well-structured skill with concrete console commands for deployment and capture. Its weaknesses are the absence of validation checkpoints in the workflow and the lack of a worked example for the phishlet-authoring path.

Suggestions

Add an explicit validation step between lure creation and use — e.g., 'load `lures get-url 0` output in a test browser and confirm the real login renders through the proxy before proceeding'.

Include a minimal skeleton phishlet YAML (auth_hosts, sub_filters, auth_tokens keys) in the authoring section so the custom-target path is as actionable as the deploy path.

Trim the introductory paragraph's explanation of why session cookies matter and how the proxy works; keep only the one-line framing.

DimensionReasoningScore

Conciseness

The body is efficient with command blocks and terse sections, but the intro paragraph re-explains the adversary-in-the-middle concept ('the victim authenticates against the *real* site through your proxy, MFA included') and the 'A phishlet is a YAML map of...' sentence could be tightened.

4 / 5

Actionability

The Deploy and Capture sections provide copy-paste console commands ('config domain login.acme-portal.example', 'phishlets enable o365', 'lures get-url 0', 'sessions <id>'), but the phishlet authoring section is prose-only with no concrete YAML example, leaving a gap.

4 / 5

Workflow Clarity

A coherent sequence exists (prerequisites, deploy, author, capture, replay, evidence, OPSEC), but there are no validation or verification checkpoints — no step to test the generated lure URL or confirm DNS/cert issuance before live use — which caps workflow clarity at 3 for this risky operation type.

3 / 5

Progressive Disclosure

The body is short with well-organized section headers and no bundle files; per the rubric's simple-skill note, a short skill with no need for external references scores 5 on well-organized sections alone.

5 / 5

Total

16

/

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 specific, distinctive description that clearly states what the skill does. Its main weakness is the absence of an explicit 'when to use' trigger clause in the description field itself, and natural trigger synonyms are relegated to metadata.

Suggestions

Add an explicit 'Use when...' sentence to the description (e.g., 'Use when the target enforces MFA and session-token capture is required'), mirroring the when_to_use terms already in metadata.

Fold one or two natural synonyms such as 'adversary in the middle' or 'AiTM' into the description text itself rather than keeping them only in metadata.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'author and deploy an evilginx2 phishlet', 'reverse-proxy a real login', 'capture the post-authentication session cookie', 'defeating MFA via session-token theft' — comprehensively covering what the skill does.

5 / 5

Completeness

The 'what' is explicit and concrete, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural domain keywords are present ('evilginx2', 'phishlet', 'reverse-proxy', 'session cookie', 'MFA'), but common variations such as 'phishing', 'AiTM', or 'adversary in the middle' appear only in metadata and not in the description itself.

4 / 5

Distinctiveness Conflict Risk

'evilginx2 phishlet' names a clear niche with distinct, unambiguous triggers; risk of firing for the wrong skill is minimal.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/phisher/evilginx2-proxy/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.