ClawHub

Skylens Transaction Analysis

v1.0.0

Inspects one EVM transaction with Skylens APIs and returns human-readable trace, balance, storage, and nonce changes. Use when the user asks for tx-level inv...

⭐ 0· 147·0 current·0 all-time
byCertiK@certik-ai

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for certik-ai/skylens-transaction-analysis.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Skylens Transaction Analysis" (certik-ai/skylens-transaction-analysis) from ClawHub.
Skill page: https://clawhub.ai/certik-ai/skylens-transaction-analysis
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install skylens-transaction-analysis

ClawHub CLI

Package manager switcher

npx clawhub@latest install skylens-transaction-analysis
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description, SKILL.md, README, and the bundled scripts/skylens.py all consistently implement transaction-level inspection via Skylens APIs (trace, balance, state, nonce, source files). The only network host used is skylens.certik.com, which aligns with the stated purpose.
ℹ
Instruction Scope
Runtime instructions instruct the agent to exec the included Python script and call Skylens endpoints. This stays within the stated purpose. Note: the get-source-file command can save downloaded source to an arbitrary path when --OUTPUT is provided, so the agent (or user) could write files to disk — expected for this tool but something to be conscious of.
ℹ
Install Mechanism
There is no install spec (instruction-only with a bundled script). The script requires a zstd backend (Python 3.14's compression.zstd or the pip package zstandard) but the skill does not provide an automated installer; that may cause runtime failures if the environment lacks the dependency. No arbitrary downloads or external install URLs are used by the skill itself.
✓
Credentials
The skill declares no required environment variables or credentials. The script performs only outbound HTTPS calls to skylens.certik.com and does not read declared secrets or unrelated config paths in the provided code. No excessive or unrelated environment access is requested.
✓
Persistence & Privilege
always:false (default) and the skill does not attempt to persist configuration or modify other skills. It only includes an executable script within its own directory; no elevated or permanent privileges are requested.
Assessment
This skill appears to do what it claims: it runs a bundled Python CLI that queries Skylens (skylens.certik.com) and prints or optionally writes results. Before installing, confirm you trust skylens.certik.com and are comfortable granting outbound HTTPS access. Ensure the runtime has a zstd backend (Python 3.14+ or the zstandard package) or the script may fail. Be aware that get-source-file --OUTPUT can write files to arbitrary paths if chosen — avoid running it with sensitive system paths. No credentials are requested by the skill itself; if you see prompts for API keys or tokens later, treat them as unexpected and investigate.

Like a lobster shell, security has layers — review code before you run it.

latestvk971syy0gn01rvcya3m9kmxcs9832hh8
147downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0
CertiK@certik-ai
latest
Download

Skylens Transaction Analysis

Use {skillDir}/scripts/skylens.py to inspect one transaction with Skylens APIs.

When To Use This Skill

Use this skill when the user wants transaction-level investigation for a single EVM transaction on a supported chain. Typical triggers:

  • The user provides a transaction hash and asks what happened.
  • The user wants an execution trace or call flow for one transaction.
  • The user asks which balances changed for a specific address in one transaction.
  • The user asks which storage slots changed for a contract in one transaction.
  • The user asks whether an address nonce changed in one transaction.
  • The user wants contract source files tied to addresses touched by one transaction.

Quick Triage Workflow

  1. Run get-trace to identify key calls/contracts.
  2. Run list-source-files for suspicious contract addresses to enumerate available files.
  3. Run get-source-file with selected --FILE_INDEX (and optional --OUTPUT) to fetch source code.
  4. Run state-change for suspicious contract addresses (storage deltas).
  5. Run nonce-change for addresses that sent/triggered actions.
  6. Run balance-change for holder asset impact.

Commands

  • get-trace: readable execution trace (paged)
  • balance-change: balance deltas for one holder
  • state-change: storage slot changes for one address
  • nonce-change: nonce before/after for one address
  • list-source-files: list contract source files (or AST-only files) by tx
  • get-source-file: get one contract file by index from list-source-files

Supported Chains

eth, bsc, polygon, optimism, arb, base, blast, avalanche, scroll, linea, sonic, kaia, world, unichain, hyperliquid, plasma

Shared Parameter Rules

  • tx_hash: full hash with 0x
  • chain: must be one of supported chains above
  • address / holder: case-insensitive, accepts with or without 0x

get-trace

CLI:

{skillDir}/scripts/skylens.py get-trace --TX <tx_hash> --CHAIN <chain> --OFFSET 0 --SIZE 100

Output:

  • Prints one readable trace line per event.
  • Prints only [offset, offset+size).

Output format:

{index}({depth}) {op} {description} [source: ...]

Source suffix (optional):

source: [c: {contractAddress}, f:{fileIdx}, s:{start}, o:{length}]

Current event variants:

  • callEvent
  • createEvent
  • storageAccessEvent
  • logEvent
  • keccak256Event

balance-change

CLI:

{skillDir}/scripts/skylens.py balance-change --TX <tx_hash> --CHAIN <chain> --HOLDER <address>

Output:

  • Prints balance deltas for the target holder.
  • May include native/token/NFT sections when available.

Printed shapes:

  • BalanceOf Native ETH: holder=... before=... after=... delta=...
  • BalanceOf Token: token=... holder=... before=... after=... delta=...
  • BalanceOf NFT: collection=... holder=... before=... after=... delta=...

state-change

CLI:

{skillDir}/scripts/skylens.py state-change --TX <tx_hash> --CHAIN <chain> --ADDRESS <address>

Output:

  • Prints storage changes for the target address only.

Printed shape:

Storage: address=... slot=0x... before=... after=...

nonce-change

CLI:

{skillDir}/scripts/skylens.py nonce-change --TX <tx_hash> --CHAIN <chain> --ADDRESS <address>

Output:

  • Prints nonce before/after for the target address.

Printed shape:

Nonce: address=... before=... after=...

list-source-files

CLI:

{skillDir}/scripts/skylens.py list-source-files --TX <tx_hash> --CHAIN <chain> --ADDRESS <contract_address>

Output:

  • Lists source files for the target contract.
  • Includes file indexes used by get-source-file.

Printed shape:

  • Contract: ...
  • Files: ...
  • [index] fileName (artifact=..., available=source|none)

get-source-file

CLI:

{skillDir}/scripts/skylens.py get-source-file --TX <tx_hash> --CHAIN <chain> --ADDRESS <contract_address> --FILE_INDEX <index> [--OUTPUT <file_path>]

Output:

  • Returns source content for one selected file index.
  • If --OUTPUT is provided, saves source content to that path.

Comments

Loading comments...