CtrlK
BlogDocsLog inGet started
Tessl Logo

oracle-manipulation

Hunt single-block oracle manipulation — spot-price AMM oracles, manipulable TWAP, dependent calculations, missing staleness checks.

59

Quality

70%

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/contracts/oracle-manipulation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

A concise, well-structured playbook with concrete commands and executable remediation code, fitting its single-file scope. It loses points for a pseudocode flash-loan PoC and for lacking explicit validation checkpoints/assertions in its workflow steps.

Suggestions

Replace the 'Pseudo' flash-loan PoC with runnable Foundry code (actual flash-loan + swap + revert-and-reverse calls) so the primary exploit example is copy-paste ready.

Add explicit validation checkpoints to the audit workflow — e.g., a `forge test` step with assertions that gate progression and a clear 'verify PoC profits / reverts as expected' checkpoint after each test.

DimensionReasoningScore

Conciseness

Lean and dense with actionable specifics; it assumes competence and avoids explaining what an oracle or a flash loan is, so every token earns its place.

3 / 3

Actionability

Provides concrete, copy-paste grep commands and mostly executable Solidity, but the primary flash-loan PoC is explicitly labeled 'Pseudo' with commented-out steps rather than runnable code, leaving one key example incomplete.

2 / 3

Workflow Clarity

The audit steps are clearly sequenced (locate → trace → validate staleness → trace use), but there are no explicit validation checkpoints or pass/fail assertions for the PoC runs — the stale-price test comments 'If we reach here w/o revert → bug' but performs no assert that gates continuation.

2 / 3

Progressive Disclosure

No bundle files exist, so this is a single self-contained SKILL.md; it is well-organized into clearly headed sections (vectors, audit steps, PoC, severity, remediation) appropriate for a skill under the reference threshold.

3 / 3

Total

10

/

12

Passed

Description

67%Weight 40%Scale 1-3

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-targeted description that names concrete oracle-manipulation vectors and a distinct niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use' half only implied.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when auditing DeFi protocols that read on-chain prices, or when the user mentions oracle manipulation, TWAP, spot-price, or stale feeds').

Broaden trigger terms to include natural user phrasings like 'price oracle', 'flash loan manipulation', and 'stale price' to improve trigger matching.

DimensionReasoningScore

Specificity

Lists multiple concrete vectors — 'spot-price AMM oracles, manipulable TWAP, dependent calculations, missing staleness checks' — naming specific attack surfaces rather than vague capabilities.

3 / 3

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause; the 'when' is only implied, so completeness caps at 2 per the missing-trigger-clause guideline.

2 / 3

Trigger Term Quality

Includes natural terms a user would say ('oracle manipulation', 'TWAP', 'price') but lacks common phrasings like 'price oracle', 'flash loan manipulation', or 'stale price'; the metadata when_to_use 'oracle manipulation twap price bypass' partially compensates but is not in the description itself.

2 / 3

Distinctiveness Conflict Risk

Single-block oracle manipulation is a sharply defined niche with distinct triggers unlikely to collide with unrelated skills.

3 / 3

Total

10

/

12

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.

Validation14 / 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
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.