CtrlK
BlogDocsLog inGet started
Tessl Logo

business-logic

Business logic / authentication bypass / privilege escalation — POST body field tampering (role/is_admin/user_type), 2FA bypass via response manipulation, predictable TOTP seeds, hidden authorization headers, multi-step workflow tampering. For challenges tagged business_logic, privilege_escalation, 2fa_bypass, or auth_bypass that aren't pure IDOR/JWT.

75

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A tightly written, highly actionable catalog of business-logic attack primitives with a useful decision tree for ordering them. Its only gap is the absence of explicit validation/stop gates on the batch probe loops, which caps workflow clarity.

Suggestions

Add an explicit success check to the probe loops (e.g., stop and report when a response contains a flag/admin indicator) so each technique has a clear validation gate rather than relying on implicit grep inspection.

Convert the trailing 'Anti-pattern (real-world evidence)' anecdote into a one-line directive; the specific elapsed-time figures are motivational padding that does not change what Claude should do.

In the Decision Tree, note what to do when a probe returns an unexpected status code (e.g., 500 or redirect) so error recovery is explicit rather than implied.

DimensionReasoningScore

Conciseness

The body is overwhelmingly executable commands with only brief, purposeful tactical context per section; it assumes Claude's competence and avoids explaining what 2FA or curl is, with every section earning its tokens.

3 / 3

Actionability

Provides copy-paste-ready bash with real wordlist paths (/usr/share/wordlists/rockyou.txt, seclists), concrete curl loops, and specific flags — fully executable guidance rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

A Decision Tree sequences the six approaches, but the batch curl loops and hydra brute-force lack explicit validate/stop checkpoints (e.g., 'halt when a flag appears'), so per the batch-operations guideline workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is cleanly organized into six numbered sections plus a decision tree, giving easy navigation without a monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

100%

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 precise, third-person description that pairs concrete capability enumeration with an explicit, tag-based trigger clause and an explicit disambiguator against IDOR/JWT skills. It hits the top anchor on all four dimensions without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete attack techniques — 'POST body field tampering', '2FA bypass via response manipulation', 'predictable TOTP seeds', 'hidden authorization headers', 'multi-step workflow tampering' — matching the anchor for several specific concrete actions rather than vague domain naming.

3 / 3

Completeness

Explicitly answers both what (the enumerated tampering/bypass techniques) and when ('For challenges tagged business_logic, privilege_escalation, 2fa_bypass, or auth_bypass that aren't pure IDOR/JWT'), an explicit trigger clause that clears the completeness cap.

3 / 3

Trigger Term Quality

Covers the natural trigger vocabulary for this domain — 'business_logic, privilege_escalation, 2fa_bypass, or auth_bypass' tags plus technique terms (2FA, TOTP, role/is_admin) — giving good coverage of terms a user/Claude would actually invoke the skill on.

3 / 3

Distinctiveness Conflict Risk

The 'that aren't pure IDOR/JWT' qualifier carves out a clear niche from sibling auth skills, and the tagged triggers are specific enough to avoid firing for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.