CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ato-methodology

Account Takeover decision tree — 9 canonical ATO paths, chaining patterns (IDOR→ATO, XSS→ATO, OAuth→ATO), MFA bypass entry points.

Quality

78%

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/exploit/web/ato-methodology/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, expert-level methodology document: concrete endpoints and flaw conditions, a genuinely useful chain table and decision tree, and disciplined non-destructive PoC framing with no wasted tokens. The main gaps are a handful of unexplained how-to-test bullets and no error-recovery guidance for paths that fail.

DimensionReasoningScore

Conciseness

The body is lean throughout: compact bullet lists, concrete endpoints ('POST /api/users/me/email', 'PATCH /api/users/<id>'), and no padding or explanation of concepts Claude already knows. The one framing line ('ATO is an outcome, not a vuln class') is a genuinely useful heuristic, not filler — every token earns its place.

5 / 5

Actionability

For an instruction-only methodology skill, the guidance is highly concrete: specific endpoints and parameters, specific flaw conditions ('TOTP code accepted from past N-step (clock skew abuse)', 'Token guessable (timestamp + user_id...)'), a concrete chain table, and an operational decision tree. It falls short of 5 because a few bullets state findings ('verification token leaks', 'Account recovery bypasses MFA entirely') without any indication of how to test or confirm them.

4 / 5

Workflow Clarity

The decision tree gives an explicit sequenced workflow (MFA state → branch to specific numbered paths), and the PoC framing section acts as a validation checkpoint including the non-destructive proof requirement ('Show no destructive action taken on victim's actual data'). It is not a 5 because there are no feedback/recovery loops (e.g., what to re-examine when a path fails) and the path sections themselves are a catalog rather than an ordered procedure.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~95-line body is well-sectioned with numbered paths, a chain table, and clearly labeled cross-references to sibling skills that are one level deep and well signaled. It is not a 5 because the full methodology is inlined in SKILL.md — the per-path details and chain table could arguably live in reference files — and the body exceeds the under-50-lines simple-skill case.

4 / 5

Total

17

/

20

Passed

Description

66%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, domain-fluent description that clearly names what the skill contains, held back mainly by the complete absence of a 'when to use' trigger clause. Adding a 'Use when testing for account takeover / session hijacking / MFA bypass...' sentence would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g., 'Use when testing authentication flows, assessing account takeover risk, or when the user mentions ATO, account hijacking, or MFA bypass.'

Include a few more natural synonyms users say — 'account hijacking', 'session takeover', 'password reset flaws' — to broaden trigger coverage.

State the skill's action in third-person verb form (e.g., 'Maps ATO attack paths and chaining patterns...') rather than only naming the artifact.

DimensionReasoningScore

Specificity

The description lists several concrete, named specifics — '9 canonical ATO paths', 'chaining patterns (IDOR→ATO, XSS→ATO, OAuth→ATO)', 'MFA bypass entry points' — rather than vague domain language. It falls short of a 5 because these are content topics stated as a noun-phrase fragment rather than a comprehensive set of actions the skill performs.

4 / 5

Completeness

The 'what' is reasonably clear (an ATO decision tree covering 9 paths, chaining patterns, and MFA bypass entry points), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

It includes natural terms a user would say in this domain — 'Account Takeover', 'ATO', 'MFA bypass', plus named chain partners (IDOR, XSS, OAuth). A few natural variations are missing from the description itself (e.g., 'hijack', 'session takeover', 'password reset'), which keeps it below the comprehensive-synonym level of a 5.

4 / 5

Distinctiveness Conflict Risk

'Account Takeover decision tree' and 'ATO' establish a clear niche trigger with minimal conflict risk. The named technologies (OAuth, XSS, IDOR, JWT-adjacent terms) create minor overlap with dedicated per-vuln skills this body itself cross-references, but the ATO-outcome framing keeps the triggers mostly distinct.

4 / 5

Total

15

/

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/exploit/web/ato-methodology/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.