agentleFS
ianallowayianalloway/openclaw-skills/nft-tracker/SKILL.md

nft-tracker

Skill4 starsChanged 5 months agoMITView on GitHub

Track NFT collection prices, floor prices, and sales data. Supports Ethereum collections including BAYC, MAYC, CryptoPunks, and more.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use collection slugs for stats.

    line 135

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NFT Price Tracker

Track NFT collection stats, floor prices, and recent sales using the OpenSea API.

Setup

Export your OpenSea API key (free tier available):

export OPENSEA_API_KEY="your-key"

Popular Collection Slugs

  • boredapeyachtclub - Bored Ape Yacht Club (BAYC)
  • mutant-ape-yacht-club - Mutant Ape Yacht Club (MAYC)
  • cryptopunks - CryptoPunks
  • azuki - Azuki
  • pudgypenguins - Pudgy Penguins
  • doodles-official - Doodles
  • clonex - CloneX

Collection Stats

Get collection floor and volume stats:

curl -s "https://api.opensea.io/api/v2/collections/mutant-ape-yacht-club/stats" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq '{
  floor: .total.floor_price,
  volume: .total.volume,
  sales: .total.sales,
  num_owners: .total.num_owners,
  average_price: .total.average_price
}'

BAYC example:

curl -s "https://api.opensea.io/api/v2/collections/boredapeyachtclub/stats" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq '.'

Collection Metadata

curl -s "https://api.opensea.io/api/v2/collections/mutant-ape-yacht-club" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq '{
  name: .name,
  description: .description,
  image_url: .image_url,
  contracts: .contracts
}'

Recent Events / Sales

curl -s "https://api.opensea.io/api/v2/events/collection/boredapeyachtclub?event_type=sale&limit=10" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq '.asset_events[] | {
  event_type: .event_type,
  order_hash: .order_hash,
  chain: .chain
}'

Contract addresses:

  • BAYC: 0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d
  • MAYC: 0x60e4d786628fea6478f785a6d7e704777c86a7c6
  • CryptoPunks: 0xb47e3cd837ddf8e4c57f05d70ab865de6e193bbb

NFT Lookup

Get details for a specific token (MAYC #1234):

curl -s "https://api.opensea.io/api/v2/chain/ethereum/contract/0x60e4d786628fea6478f785a6d7e704777c86a7c6/nfts/1234" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq '.nft | {name, image_url, owners, traits}'

Price Alerts (Script Example)

Monitor floor price and alert when below threshold:

#!/bin/bash
COLLECTION="mutant-ape-yacht-club"
THRESHOLD=5  # ETH (or collection floor units)

FLOOR=$(curl -s "https://api.opensea.io/api/v2/collections/$COLLECTION/stats" \
  -H "X-API-KEY: $OPENSEA_API_KEY" | jq -r '.total.floor_price // empty')

if [ -n "$FLOOR" ] && (( $(echo "$FLOOR < $THRESHOLD" | bc -l) )); then
  echo "ALERT: $COLLECTION floor is $FLOOR (below $THRESHOLD)"
fi

Tips

  • OpenSea requires an API key for most endpoints — get one at https://docs.opensea.io/reference/api-keys
  • Rate limits apply — cache responses when possible
  • Use collection slugs for stats; use chain + contract + token id for precise NFT lookups
  • The old Reservoir api.reservoir.tools host no longer resolves; prefer OpenSea

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.