CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

business-logic-testing

Test an authorized web application for business-logic flaws and race conditions — the classes scanners cannot find. Model invariants (conservation of value, uniqueness, monotonicity, exclusivity), build an Actor x Action x Resource matrix, abuse state machines (skip/reorder/replay steps, limit-slicing), find numeric bugs (float-vs-decimal rounding, cross-currency refund arbitrage, negative amounts), stale feature gates, and saga gaps; prove concurrency bugs (double-spend, lost update, idempotency-key reuse) with controlled parallel requests. Use when the user mentions 'business logic testing,' 'race condition,' 'double spend,' 'TOCTOU,' 'concurrency bug,' 'idempotency,' 'coupon reuse,' 'workflow bypass,' 'limit bypass,' 'negative amount,' 'refund arbitrage,' 'parallel request attack,' or 'logic flaw.'

Quality

94%

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

92%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 well-engineered instruction-only skill body: sequenced methodology, concrete attack recipes, an exceptional per-class validation and false-positive framework, and clean one-level-deep disclosure into a verified reference bundle. The only improvement space is trimming a handful of sentences that re-explain fundamentals Claude already knows.

DimensionReasoningScore

Conciseness

The body is dense and technique-first with no padding, but a few sentences explain concepts Claude already knows — "the default isolation level permits non-repeatable reads and write skew", "prices or balances stored or computed as floats accumulate rounding error", and the Redis NX/EX mechanics. These are minor instances that could be trimmed, matching the efficient-but-slightly-trimmable anchor rather than the every-token-earns-its-place of a 5.

4 / 5

Actionability

Concrete, executable guidance throughout: exact probes (quantity `-1`, `1e3`, `0.1 + 0.2`, discount after total lock, shipping address change between authorization and capture), specific fields to tamper (`approver_id`/`reviewer_id`), and code-level control identifiers (`(principal, endpoint, key)` scoping, `INSERT ... ON CONFLICT`, `WHERE balance >= amount`). The executable tooling is one level deep in references/concurrency.md with copy-paste-ready Turbo Intruder, curl --parallel, and httpx code that was verified to exist.

5 / 5

Workflow Clarity

A clearly sequenced Steps 1–6 methodology with a hard pre-flight Authorization Check ("If any of these is missing, stop and ask") and an unusually thorough validation gate: a per-class confirmed/false-positive table, a durable-state proof standard, two enumerated false-positive traps, and an explicit recovery path (a candidate not landed under the cap becomes needs_validation with a validation_plan). The destructive/batch-operation cap does not apply because validation is emphatically present.

5 / 5

Progressive Disclosure

The body is the methodology overview and correctly pushes depth to the bundle: tooling to references/concurrency.md, verification methodology to verification.md, severity calibration to severity-calibration.md, and the findings record/export to findings-format.md — all four referenced paths verified to exist in the bundle, each clearly signaled with a descriptive link. References are one level deep, and concurrency.md demonstrably delivers the worked Turbo Intruder config and httpx/curl runners the body promises.

5 / 5

Total

19

/

20

Passed

Description

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

An excellent description: concrete, comprehensive capability statements paired with an explicit and extensive trigger list. The only weakness is that a few trigger terms (TOCTOU, idempotency) are shared with adjacent source-audit/API-audit skills, creating minor routing ambiguity between closely related skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with sub-illustrations — "build an Actor x Action x Resource matrix", "abuse state machines (skip/reorder/replay steps, limit-slicing)", "prove concurrency bugs (double-spend, lost update, idempotency-key reuse) with controlled parallel requests" — giving comprehensive coverage. It exceeds the score-4 anchor because the actions are numerous and each is instantiated with concrete examples rather than left generic.

5 / 5

Completeness

Both questions are answered explicitly: the "what" is a full capability list (model invariants, matrix, state-machine abuse, numeric bugs, stale gates, saga gaps, concurrency proofs) and the "when" is a concrete "Use when the user mentions..." clause enumerating trigger phrases. It matches the anchor requiring concrete trigger phrases, not the score-4 case where the "when" could be more specific.

5 / 5

Trigger Term Quality

Thirteen explicit trigger phrases span natural user vocabulary with synonyms and variations: "race condition", "concurrency bug", "parallel request attack", "double spend", "coupon reuse", "refund arbitrage", "limit bypass", "logic flaw". This is comprehensive natural-term coverage including synonyms, matching the top anchor rather than the "a few natural terms missing" of score 4.

5 / 5

Distinctiveness Conflict Risk

The dynamic-testing niche is clearly framed ("the classes scanners cannot find", testing an authorized running application), but triggers such as "TOCTOU" and "idempotency" overlap with closely related source-side audit and API audit skills that the body itself cross-references as covering the same concepts. That is minor overlap risk with sibling skills — above anchor 3's "could still overlap with similar skills" but below the "minimal conflict risk" required for a 5.

4 / 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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/business-logic-testing/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.