Skip to content
TrustedSkillsbeta
Back to all skills

Get Block Number

Checked
tradingstrategy-ai·vlatest·other·MIT

Retrieves the block height at a specific timestamp, crucial for accurate order book analysis and strategy execution.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tradingstrategy-ai/web3-ethereum-defi --skill get-block-number -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tradingstrategy-ai

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tradingstrategy-ai/web3-ethereum-defi at 8316aa7d9b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8316aa7d9b
Manifest
.claude/skills/get-block-number/SKILL.md
Scanned
1 file, 47 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill retrieves the current block number from an Ethereum node, providing a precise timestamp for on-chain events. It serves as a foundational query for synchronizing AI agent actions with the latest state of the blockchain.

When to use it

  • Timestamping Transactions: Verify exactly when a smart contract interaction occurred relative to network consensus.
  • Synchronization Checks: Ensure your agent's local data matches the live chain before executing trades or strategies.
  • Event Filtering: Determine the starting block for scanning historical logs or filtering specific transaction ranges.
  • Gas Optimization: Assess current network congestion levels by correlating block height with gas prices over time.

Key capabilities

  • Queries Ethereum nodes directly for the latest finalized block height.
  • Returns a raw integer representing the current chain state.
  • Integrates seamlessly with other web3-ethereum-defi skills to build complex DeFi workflows.

Example prompts

  • "What is the current Ethereum block number?"
  • "Get the latest block height from the mainnet and compare it to my last trade."
  • "Retrieve the block number so I can filter logs starting from this point."

Tips & gotchas

  • Latency Awareness: Block numbers update every ~12 seconds; do not use this for millisecond-precision timing.
  • Finality vs. Head: This typically returns the head of the chain; ensure your logic accounts for potential reorgs if relying on absolute finality.