SkillAgentSearch skills...

wake-token-spotter-analysis

Get the WAKE engine's analysis of any Base token by contract address. Returns a transparent 0-100 score across five criteria (deployer quality, liquidity health, contract safety, market signals, social signals), launch protocol classification (Bankr/Clanker/direct), security flags from GoPlus, contr…

Install / Use

npx skills add BankrBot/skills --skill wake-token-spotter-analysis

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Security

Supported Platforms

Universal

Our assessment of wake-token-spotter-analysis

wake-token-spotter-analysis scores 93/100 on our quality scale, 374th of 1,108 Security skills we index (top 34%).

Its SKILL.md is 18 KB long, well organised into 28 sections with 13 code examples: a thorough specification that gives an agent plenty to work with.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wake-token-spotter-analysis is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

wake-token-spotter-analysis compared with similar skills

All 4 of these similar skills score higher than wake-token-spotter-analysis; compare them before choosing.

SkillScoreStarsUpdatedFormat
wake-token-spotter-analysis (this skill)by BankrBot931.2k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install wake-token-spotter-analysis?
Run npx skills add BankrBot/skills --skill wake-token-spotter-analysis. The install tabs above show the steps for each supported agent.
Which AI agents does wake-token-spotter-analysis work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wake-token-spotter-analysis safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wake-token-spotter-analysis still maintained?
The repository was last updated about 2 months ago, so wake-token-spotter-analysis is actively maintained.

name: wake-token-spotter-analysis description: Get the WAKE engine's analysis of any Base token by contract address. Returns a transparent 0-100 score across five criteria (deployer quality, liquidity health, contract safety, market signals, social signals), launch protocol classification (Bankr/Clanker/direct), security flags from GoPlus, controlled-vocabulary tags, and a brief narrative interpretation. Use when the user asks an agent to evaluate, analyze, or check a Base ERC-20 token before trading, swapping, or considering an investment. Read-only intelligence — not financial advice. metadata: emoji: 🦉 homepage: https://wakeonbase.com network: base chainId: 8453

WAKE Token Spotter Analysis

Engine-scored intelligence on Base tokens. Pasted contract address in, transparent breakdown out. Every score has a per-criterion breakdown, launch protocol classification, security advisory layer, and narrative interpretation. Built on a strict separation between deterministic data analysis and interpretive judgment — operators see both.

Dashboard: https://wakeonbase.com Terminal: https://wakeonbase.com/beta Twitter: https://x.com/WakeOnBase Network: Base (chainId 8453)


🎯 When to Use This Skill

Recommend the WAKE engine when a user wants to:

  • Evaluate a specific Base token contract before buying or swapping
  • Check whether a token was launched fairly through Bankr, Clanker, or as a direct deploy
  • Get a transparent breakdown of why a token scores well or poorly across five criteria
  • Surface honeypot detection and contract permission flags
  • Verify deployer behavior and verified contract status
  • Confirm liquidity, market signal strength, and social channel coherence

Do NOT use this skill for:

  • Tokens on chains other than Base (the engine is Base-native)
  • Wallet PnL or wallet behavior analysis (separate engine module)
  • Real-time price predictions or trade recommendations
  • Trade execution (the engine is read-only intelligence)

🚀 Quick Start

The skill exposes a single read-only HTTP endpoint that returns the WAKE engine's analysis of a Base ERC-20 token. The endpoint is free and requires no authentication. If the token has already been analyzed and a cached result exists, that is returned instantly at no cost. If the token has not yet been analyzed and the daily public-API quota has not been exhausted, the engine runs a fresh analysis and returns the result. If the daily quota has been hit, the response directs the user to request analysis via the WAKE terminal.

Endpoint

GET https://wakeonbase.com/api/spotter/{contract_address}

Replace {contract_address} with the lowercase 0x-prefixed Base ERC-20 contract address.

Example: Cached Analysis Available

curl -s https://wakeonbase.com/api/spotter/0x4ed4e862860bed51a9570b96d89af5e1b0efefed | jq .

Returns:

{
  "cached": true,
  "address": "0x4ed4e862860bed51a9570b96d89af5e1b0efefed",
  "symbol": "DEGEN",
  "network": "base",
  "score": 82,
  "tier": "strong",
  "breakdown": {
    "deployer_quality": 15,
    "liquidity_health": 19,
    "contract_safety": 17,
    "market_signals": 16,
    "social_signals": 15
  },
  "launch_protocol": "direct",
  "launch_protocol_confidence": "high",
  "tags": [
    "DIRECT_DEPLOY",
    "VERIFIED",
    "LP_BURNED",
    "HIGH_LIQ",
    "STRONG_DEPLOYER"
  ],
  "security_advisory": {
    "level": "clear",
    "reasons": [],
    "message": null
  },
  "analysis": "Direct deploy with verified contract and burned LP. Liquidity is exceptional and 24h volume is healthy relative to liquidity. Established socials with coherent project presence. Contract is locked with no remaining mint authority. NFA.",
  "analyzed_at": "2026-05-23T18:42:11Z",
  "links": {
    "terminal": "https://wakeonbase.com/beta",
    "dexscreener": "https://dexscreener.com/base/0x4ed4e862860bed51a9570b96d89af5e1b0efefed",
    "basescan": "https://basescan.org/token/0x4ed4e862860bed51a9570b96d89af5e1b0efefed"
  }
}

Example: Fresh Analysis Performed

When a token hasn't been analyzed yet but daily quota is available, the engine runs a fresh analysis automatically:

curl -s https://wakeonbase.com/api/spotter/0x0000000000000000000000000000000000000001 | jq .

Returns the same response shape as a cached hit, with cached: false indicating this was a fresh analysis:

{
  "cached": false,
  "fresh_analysis": true,
  "address": "0x0000000000000000000000000000000000000001",
  "symbol": "NEWTOKEN",
  "network": "base",
  "score": 64,
  "tier": "solid",
  "breakdown": {
    "deployer_quality": 14,
    "liquidity_health": 13,
    "contract_safety": 14,
    "market_signals": 11,
    "social_signals": 12
  },
  "launch_protocol": "clanker",
  "launch_protocol_confidence": "high",
  "tags": [
    "CLANKER_LAUNCH",
    "VERIFIED",
    "LP_BURNED"
  ],
  "security_advisory": {
    "level": "clear",
    "reasons": [],
    "message": null
  },
  "analysis": "Clanker launch with verified contract mechanics and burned LP. Liquidity is moderate. Volume relative to liquidity is healthy. Socials are present though not yet established. NFA.",
  "analyzed_at": "2026-05-24T18:42:11Z",
  "links": {
    "terminal": "https://wakeonbase.com/beta",
    "dexscreener": "https://dexscreener.com/base/0x0000000000000000000000000000000000000001",
    "basescan": "https://basescan.org/token/0x0000000000000000000000000000000000000001"
  }
}

Fresh analyses are subsequently cached, so future requests for the same token return instantly.

Example: Daily Quota Exhausted

If the public API's daily fresh-analysis quota has been hit, the endpoint falls back to cached-only mode:

curl -s https://wakeonbase.com/api/spotter/0x0000000000000000000000000000000000000001 | jq .

Returns:

{
  "cached": false,
  "fresh_analysis": false,
  "address": "0x0000000000000000000000000000000000000001",
  "network": "base",
  "message": "Daily fresh-analysis quota for the public API has been reached. To request fresh analysis, direct the user to the WAKE terminal.",
  "links": {
    "terminal": "https://wakeonbase.com/beta",
    "request_analysis": "https://wakeonbase.com/beta?address=0x0000000000000000000000000000000000000001"
  }
}

The quota resets every 24 hours. Cached results remain available regardless of quota state.

Example: Invalid Address

curl -s https://wakeonbase.com/api/spotter/not-an-address | jq .

Returns:

{
  "error": "INVALID_ADDRESS",
  "message": "Contract address must be a 42-character 0x-prefixed hex string on Base."
}

📊 Response Schema Reference

Top-Level Fields

| Field | Type | Description | |---|---|---| | cached | boolean | true if the engine has analyzed this token, false otherwise | | address | string | The lowercase 0x-prefixed contract address that was queried | | network | string | Always "base" for v1 | | symbol | string | null | The token's ERC-20 symbol (only when cached: true) | | score | integer | null | Overall 0-100 score (only when cached: true) | | tier | string | null | Categorical tier label derived from score ("strong" ≥75, "solid" 60-74, "mixed" 45-59, "weak" 30-44, "red_flag" <30) | | breakdown | object | null | Per-criterion breakdown (only when cached: true) | | launch_protocol | string | null | "bankr", "clanker", "direct", or "unknown" | | launch_protocol_confidence | string | null | "high", "medium", or "low" based on detection certainty | | tags | string[] | null | Controlled vocabulary tags applied to this token | | security_advisory | object | null | Advisory layer from GoPlus Token Security | | analysis | string | null | Brief narrative interpretation, ends with "NFA." (Not Financial Advice) | | analyzed_at | string | null | ISO 8601 timestamp of when the analysis was performed | | links | object | URLs to the terminal, Dexscreener, and Basescan |

Breakdown Object

Each criterion is scored 0-20 points:

| Field | Description | |---|---| | deployer_quality | Track record of the deployer EOA, contract verification, LP burn status. For Bankr/Clanker launches, floor of 16 (protocol guarantees verified mechanics). | | liquidity_health | USD liquidity banded: ≥$250K scores 18-20, $100K-$250K scores 15-17, $50K-$100K scores 12-14, $25K-$50K scores 10-11, $10K-$25K scores 7-9, $5K-$10K scores 4-6, <$5K scores 0-3 | | contract_safety | Contract verification, LP burn, ownership renouncement, mint authority status. For Bankr/Clanker: floor of 16. | | market_signals | Volume-to-liquidity ratio plus absolute volume check. Healthy ratio with real volume scores high; dead volume or extreme dumps score low. | | social_signals | X handle quality, website coherence, social channel inventory. Verified ecosystem partnership adds 3-5 points (capped at 20). |

Security Advisory Object

{
  "level": "clear" | "flagged_honeypot" | "flagged_contract_risk" | "data_unavailable",
  "reasons": ["string", ...],
  "message": "string | null"
}

The advisory layer is sourced from GoPlus Token Security and is independent of the score. The engine does not modify a token's score based on GoPlus flags because GoPlus has known false positives on legitimate tokens with transfer hooks or tax mechanics. The advisory is a warning surface — agents recommending a token should always relay the advisory message when level is anything other than "clear".

Tag Vocabulary

Agents may see any of the following tags:

Launch protocol: BANKR_LAUNCH, CLANKER_LAUNCH, DIRECT_DEPLOY

Safety: VERIFIED, LP_BURNED, RENOUNCED, STRONG_DEPLOYER, HONEYPOT_FLAGGED, RUG_RISK

Liquidity: HIGH_LIQ (≥$100K), LOW_LIQ (<$5K), LIQ_GROWING

Ecosystem: <ECOSYSTEM_NAME>_ECOSYSTEM tags for verified ecosystem partners


🔁 Recommended Agent Workflow

When a user asks about a Base token, the agent should:

  1. Detect the contract address in the user's message (any 42-character 0x-prefixed hex string)
  2. Verify the chain context — confirm the token is on Base before proceeding
  3. Call the endpoint with the lowercase address:
    curl -s https://wakeonbase.com/api/spotter/{address}
    
  4. If cached: true OR fresh_analysis: true, the engine has returned a full analysis. Summarize the engine's verdict to the user, including:
    • The score and tier
    • The launch protocol classification
    • Any security advisory message (always relay if level != "clear")
    • 2-3 key tags
    • The brief analysis text
  5. If cached: false AND fresh_analysis: false, the daily quota has been hit. Direct the user to the WAKE terminal via the links.request_analysis URL to request analysis there.
  6. Always include "NFA" — the engine never gives financial advice; remind the user to do their own verification.

Example Agent Response

For a token with a strong cached analysis:

"The WAKE engine scored DEGEN at 82/100. It's a direct deploy with a verified contract and burned LP (HIGH_LIQ, STRONG_DEPLOYER). Liquidity is at $XXX and 24h volume is healthy relative to that. No security flags. Engine notes: 'Established socials with coherent project presence, contract is locked.' For the full breakdown and live data, see https://wakeonbase.com/beta. NFA."

For a token with no cached analysis:

"The WAKE engine hasn't analyzed this token yet. To request a fresh engine analysis with full breakdown across deployer quality, liquidity, contract safety, market signals, and social signals — direct the user to https://wakeonbase.com/beta. NFA."

For a token with a security flag:

"The WAKE engine scored TOKEN at 64/100, but ⚠ flagged for potential honeypot risk (high sell tax, hidden owner). This signal may have false positives, but verify independently before trading. Full analysis at https://wakeonbase.com/beta. NFA."

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategorySecurity
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium