SkillAgentSearch skills...

cattown

Interact with Cat Town — a Farcaster-native game world on Base. Covers KIBBLE staking (stake, claim, unlock, unstake, leaderboard, deposit history); live world state (season, weather, time of day, weekend flag); fishing drops filtered by world state; Isabella's weekend fishing competition with live…

Install / Use

npx skills add BankrBot/skills --skill cattown

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Other

Supported Platforms

Universal

Tags

Our assessment of cattown

cattown scores 84/100 on our quality scale, 228th of 329 Other skills we index.

Its SKILL.md is 49 KB long, well organised into 65 sections with 23 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

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

Substance
21/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 cattown is actively maintained.
  • Our last check on 2026-11-06 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-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

cattown compared with similar skills

All 4 of these similar skills score higher than cattown; compare them before choosing.

SkillScoreStarsUpdatedFormat
cattown (this skill)by BankrBot841.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 cattown?
Run npx skills add BankrBot/skills --skill cattown. The install tabs above show the steps for each supported agent.
Which AI agents does cattown 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 cattown 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 cattown still maintained?
The repository was last updated about 2 months ago, so cattown is actively maintained.

name: cattown description: Interact with Cat Town — a Farcaster-native game world on Base. Covers KIBBLE staking (stake, claim, unlock, unstake, leaderboard, deposit history); live world state (season, weather, time of day, weekend flag); fishing drops filtered by world state; Isabella's weekend fishing competition with live prize-pool math; Paulie's weekly fish raffle (free-ticket claim, tier-based prize pool, odds, last winners); the daily 3-item boutique with KIBBLE→USD conversion; gacha spins (async VRF pay-then-receive, 100/day cap, seasonal pools); item valuation plus batch selling via the V2 vendor (5% tax); and KIBBLE tokenomics (% burned, % staked, live APY). Use when the user mentions Cat Town, KIBBLE, Wealth & Whiskers, Jasper, Isabella, Paulie, Skipper, Theodore, Cassie, RevenueShare, fishing, gacha, raffle, boutique, vendor, prize pools, drop tables, or any read/write on the Cat Town contracts.

Cat Town — Agent Overview

Cat Town is a Farcaster-native game world on Base. Players fish, collect, and earn KIBBLE; a share of town revenue is streamed weekly to KIBBLE stakers. This skill lets agents read Cat Town state and submit the transactions needed to participate.

The town's NPCs run each activity and are worth naming when talking to players:

  • Wealth & Whiskers Bank — where KIBBLE staking happens. Theodore works the day shift, Cassie takes over in the evening.
  • Paulie — runs the weekly fish raffle.
  • Skipper — the weekday fishing NPC.
  • Isabella — hosts the weekend fishing competition.

Current coverage:

  • KIBBLE staking (RevenueShare) — stake, claim, claim-and-restake, unlock, relock, unstake, plus staking leaderboard and deposit history.
  • World state (GameData) — live season, time of day, weather, weekend flag.
  • Fishing drops — the public item-truth catalog filtered by world state (weather/season/time).
  • Fishing competition (Isabella, Sat–Mon) — live prize-pool math, top-10 leaderboard, active/inactive response patterns.
  • Fish raffle (Paulie, Fri 20:00 UTC draw) — free-ticket claim flow, tier-based prize pool, chance-to-win, leaderboard + last winners.
  • Boutique — daily 3-item onchain rotation with KIBBLE→USD conversion via the Kibble Price Oracle.
  • KIBBLE tokenomics — Jasper's math for % burned, % staked, and live staking APY.

Each surface has its own subdirectory under references/ for the deep reference. The weekly calendar below is the shared timing reference — many sections link back to it.

Links:

  • Game: https://cat.town
  • Bank (staking UI): https://cat.town/bank
  • Docs: https://docs.cat.town

Weekly Calendar (all times UTC)

Cat Town runs on a fixed weekly cadence. Use these timings when setting user expectations ("your next fishing drop is Monday") or scheduling follow-ups.

| Day | Event | Time | Host | Affects staking rewards? | |-----------|-----------------------------------|----------------------------|-------------------|--------------------------| | Monday | Fishing revenue deposit | by 12:00 (often earlier) | Theodore / Cassie | Yes | | Mon–Fri | Fish raffle ticket sales open | — | Paulie | No | | Mon–Fri | Weekday fishing | — | Skipper | No | | Wednesday | Gacha revenue deposit | by 12:00 (often earlier) | Theodore / Cassie | Yes | | Friday | Fish raffle draw | 20:00 | Paulie | No | | Sat–Sun | Weekly fishing competition | Sat morning → Sun night | Isabella | Indirect* |

*During the weekend fishing competition (Sat–Sun), 10% of every fish identification feeds the KIBBLE stakers pool. Weekday fishing (Skipper) does not feed stakers. This is why weekend activity sizes the following Monday's fishing-revenue deposit. See references/world/calendar.md for the full revenue split.

Deposits are triggered by the Cat Town backend calling depositRevenue(amount, source) on RevenueShare, with source in "fishing" or "gacha". Watch the RevenueDeposited(string source, uint256 depositTimestamp, uint256 depositAmount, uint256 newAccRewardPerShare) event to know the exact moment a drop lands.


⚠️ CRITICAL: stake/unstake take INTEGER KIBBLE, not wei — read this first

This contract breaks the 99%-of-ERC-20 default. If you reflexively wei-encode the stake/unstake amount because "that's how tokens work," the tx reverts. This is the single failure mode you will hit on this contract. Stop here and internalize the table before touching any write path.

| Call | Amount unit | Example for 1 KIBBLE | |-------------------------------------------|---------------------------|-----------------------------------| | kibble.approve(revenueShare, …) | wei (standard ERC-20) | 1000000000000000000 (= 1 × 10¹⁸) | | revenueShare.stake(uint256 amount) | integer KIBBLE | 1 | | revenueShare.unstake(uint256 amount) | integer KIBBLE | 1 |

Reads are also integer KIBBLE: getUserStaked, pendingRewards, getTotalStaked, getTotalActiveStaked.

Raw calldata — right vs. wrong

✅ stake(1)     → 0xa694fc3a0000000000000000000000000000000000000000000000000000000000000001
❌ stake(1e18)  → 0xa694fc3a0000000000000000000000000000000000000000000000000de0b6b3a7640000

The second form reverts with ERC20: transfer amount exceeds balance because the contract multiplies your argument by 10^18 internally, turning 1e18 into 1e36 wei. Verified via simulation against the deployed contract on Base.

Pre-submit validation (run this before every stake/unstake)

  • Is the amount < 1,000,000? → probably correct (integer KIBBLE).
  • Is the amount ≥ 10^15? → almost certainly wrong — you wei-encoded by reflex.
  • Sanity check: stake(1) = 1 KIBBLE. stake(100) = 100 KIBBLE. stake(10000) = 10,000 KIBBLE.
  • approve is the OPPOSITE — it is wei. Staking N KIBBLE requires approve(revenueShare, N * 10^18).

Signer = holder. The address that signs stake must be the same address that holds the KIBBLE and signed the approve.


KIBBLE Staking

Addresses (Base, chain id 8453)

  • RevenueShare: 0x9e1Ced3b5130EBfff428eE0Ff471e4Df5383C0a1
  • KIBBLE token (ERC-20, 18 decimals): 0x64cc19A52f4D631eF5BE07947CABA14aE00c52Eb

Base Sepolia addresses and the full ABI surface are in references/staking/contract.md. User-facing overview: https://docs.cat.town/economy/staking.

Core flows

Single pool, single reward token — KIBBLE in, KIBBLE out. No reward-token selection, no per-user lock duration, no multipliers. One global accRewardPerShare accumulator updated on each depositRevenue.

1. Stake (mixed units — re-read the CRITICAL section above if uncertain)

  1. kibble.approve(revenueShare, amount_wei) — amount_wei = N * 10^18 where N is the KIBBLE count. Required once if allowance(user, revenueShare) < amount_wei.
  2. revenueShare.stake(uint256 N) — N is the integer KIBBLE count, NOT wei. If this reverts with ERC20: transfer amount exceeds balance, you wei-encoded — pass the plain integer instead. Emits Staked(user, amount).

2. Claim (after each fishing/gacha deposit)

  • revenueShare.claim() — transfers pendingRewards(user) to the user. Emits Claimed(user, amount).
  • revenueShare.claimAndRestake() — claims and auto-adds to the user's stake in one tx. Emits ClaimedAndRestaked(user, restakedAmount, totalStakedNow).

3. Exit (unlock → wait → unstake)

  1. revenueShare.unlock() — emits UnlockInitiated(user, unlockEndTime). Sets isUnlocking[user] = true. Always tell the user two things when they unlock: (a) the wait is 14 days (LOCK_PERIOD = 1,209,600 seconds, snapshotted so later changes don't affect them), and (b) their pool share just dropped from whatever-it-was to 0% — they won't earn fishing or gacha deposits during the wait. Read the pre-unlock share first via getPoolShareFraction(user) / 1e18 * 100.
  2. Wait until block.timestamp >= unlockEndTime(user). The 14-day value is safe to quote at the point of unlock. Read LOCK_PERIOD() live only if you want defensive protection against future upgrades (the contract is UUPS-upgradeable).
  3. revenueShare.unstake(uint256 N) — N is the integer KIBBLE count, same convention as stake. Reverts before the wait ends. Emits Unstaked(user, amount).
  • revenueShare.relock() — at any time during the wait, cancels the unlock and puts the user back into the earning pool. Emits Relocked(user, amount).

Checking remaining unlock time

When a user asks "how long until I can withdraw?", compute from unlockEndTime(user):

remaining_seconds = max(0, unlockEndTime(user) - current_unix_time)
  • isUnlocking(user) == false → not unlocking, nothing to wait on.
  • remaining_seconds > 0 → still waiting. Convert to days/hours for the reply.
  • remaining_seconds == 0 → unstake(N) is callable now.

No dedicated contract method for "time left" — just subtract. Use the latest block's timestamp if you want to avoid clock-skew with the user's device.

Mapping "unstake" / "withdraw" / "exit" to the right call

Users say "unstake" colloquially to mean the whole exit, not literally the onchain unstake() function. Before acting, read three values: isUnlocking(user), unlockEndTime(user), and the user's current pool share (getPoolShareFraction(user) / 1e18 * 100 as a percentage). Then route:

| State | What to call | What to tell the user | |----------------------------------------------------------|--------------|---------------------------------------------------------------------------------------| | isUnlocking(user) == false | unlock() | "Started your unlock. Wait is 14 days — ready at <unlockEndTime>. Your pool share just dropped from Y% to 0%; you won't earn revenue deposits during the wait. Call relock() any time to cancel and restore your share." | | isUnlocking == true and now < unlockEndTime | (no tx) | "Already unlocking. ~X days Y hours left until you can withdraw. Your pool share is 0% until you either unstake() after the wait or relock() now." | | isUnlocking == true and now >= unlockEndTime | unstake(N) | "Withdrew N KIBBLE." (Or remaining balance if partial.) |

Same routing for "withdraw," "exit," "pull my KIBBLE out," "get my stake back." Never call the onchain unstake() as the first step — it reverts unless the user has already completed an unlock wait.

Why the share drop matters: while isUnlocking == true, the user's stake is removed from totalActiveStaked, so they do not earn any fishing or gacha revenue deposits that land during the 14-day wait. Surfacing the pre-unlock share (Y%) makes the opportunity cost explicit.

Unlock state machine — the gotcha to warn users about

 [staking, earning] ──unlock()──▶ [unlocking, NOT earning] ──wait LOCK_PERIOD──▶ [unstake available]
         ▲                               │                                              │
         └────────── relock() ───────────┘                                              │
         │                                                                              │
         └────────────────────── unstake(amount) ◀──────────

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryOther
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