CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

signature-replay

Signature replay attacks — missing nonces, missing chain ID, ecrecover zero address, signature malleability, cross-chain replay.

Quality

75%

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 ./packages/decepticon/decepticon/skills/standard/contracts/signature-replay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 strong, dense audit playbook: seven bug classes with concrete vulnerable/fix pairs, a greppable audit sequence with checklists, and near-executable Foundry PoCs plus a remediation reference contract. The main gaps are the fully monolithic single-file structure with no progressive disclosure, placeholder ellipses in several code snippets, and no explicit PoC-confirmation step linking findings to the templates.

Suggestions

Move the Foundry PoC templates, the known-exemplars list, and the full remediation contract into references/ files (e.g., references/poc-templates.md, references/exemplars.md, references/remediation.md), leaving SKILL.md as the bug-class overview plus the audit sequence with one-level-deep pointers.

Replace ellipsis placeholders in the bug-class snippets (ecrecover(h, ...), new Target(...)) with complete minimal snippets, or define the sign()/vm helpers once so the PoC templates are copy-paste runnable.

Add an explicit step 5 to the audit sequence: 'For each suspected finding, write a PoC from the templates below and only report the bug if the replay/malleable transaction succeeds' — turning the templates into a validation checkpoint rather than an appendix.

DimensionReasoningScore

Conciseness

The body is dense and efficient: each bug class is a compact vulnerable/safe Solidity pair, and it never explains background concepts Claude already knows (what EIP-712 is, how ecrecover works at length). It is not a 5 because of minor trimmable prose (e.g., 'This is mostly resolved by OZ ERC20Permit, but custom permit impls are often wrong', 'Each has well-known bugs') and the somewhat listy exemplar section, matching anchor 4's 'minor instances of over-explanation'.

4 / 5

Actionability

Concrete grep commands, per-call-site checklists, three Foundry PoC templates, and a full executable OZ remediation contract — mostly executable guidance. It stops short of anchor 5's copy-paste-ready bar because several snippets contain ellipses and undefined helpers (ecrecover(h, ...), new Target(...), sign(privKey, hash), Target targetB) that the reader must fill in, matching anchor 4's 'concrete code with minor gaps'.

4 / 5

Workflow Clarity

The Audit steps section gives a clear 1→4 sequence (find ecrecover call sites → verify payload contents → verify signature validation → grep for dangerous patterns) with verification checklists at each step. It is not a 5 because there is no explicit checkpoint that ties suspected findings to the PoC templates (no 'confirm with a PoC, and only report when it reverts/fails' step), and no feedback loop for the destructive implication of a confirmed finding — anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The skill is a single ~256-line file with no references/, scripts/, or assets/ bundle at all; everything — PoC templates, exemplar incident list, full remediation contract — is inlined. Headers are clear (better than anchor 2's structure-less wall), but content that clearly belongs in separate reference files is inlined with no external navigation, which is exactly anchor 3's 'some structure... content that should be separate is inline' — and it cannot be a 4-5 since there are no well-signaled one-level-deep references at all.

3 / 5

Total

15

/

20

Passed

Description

70%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, well-scoped description that clearly names the bug taxonomy of the signature-replay domain with strong natural trigger terms. Its main weakness is the missing "Use when..." trigger clause and the absence of key synonyms (EIP-712, permit, meta-transactions, bridges) in the description field itself.

Suggestions

Append an explicit trigger clause, e.g., "Use when auditing smart contracts that verify signatures: EIP-712, ERC-2612 permit, meta-transactions, or cross-chain bridges."

Shift from a pure topic list to naming what the skill does — e.g., "Find and exploit signature replay bugs..." — so the description conveys capabilities, not just subject matter.

Include the high-value synonyms (EIP-712, permit, meta-transaction, bridge) in the description text, since they currently exist only in metadata.when_to_use.

DimensionReasoningScore

Specificity

The description enumerates five concrete bug classes ("missing nonces, missing chain ID, ecrecover zero address, signature malleability, cross-chain replay") giving comprehensive coverage of the niche. It falls short of anchor 5 because it enumerates topics covered rather than the actions the skill performs (e.g., detect, audit, write PoCs), matching anchor 4's 'several specific items; minor gaps' rather than an action-verb list.

4 / 5

Completeness

The "what" is clear and specific (the five replay bug classes), but the description field contains no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3. It is not a 4 because the "when" is entirely absent from the field rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

Natural audit-domain terms users would actually say are present: "signature replay", "nonce", "chain ID", "ecrecover", "cross-chain". It sits at anchor 4 rather than 5 because common synonyms users might invoke are absent from the description field itself — "EIP-712", "permit", "meta-transaction", "bridge" (some appear only in metadata.when_to_use, which is not the description field under evaluation).

4 / 5

Distinctiveness Conflict Risk

A clear niche — signature replay attacks in smart contracts — with distinct technical triggers (ecrecover, nonce, chain ID, cross-chain) that adjacent skills (reentrancy, oracle manipulation, access control) would not claim. Matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'; it does not exhibit the overlap risk described at anchor 4.

5 / 5

Total

16

/

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/contracts/signature-replay/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.