Read every candidate
18 skills, 269 operations, no cross references. Each SKILL.md describes when to trigger and what comes back, and says nothing about the skill you are going to call next.
Binance Skills Hub publishes 18 skills across two namespaces. A real job needs two or three of them, in a fixed order, with a condition between each step. Skillsmith writes that file.
Every skill in Binance Skills Hub is written to stand alone. Trigger text, inputs, outputs, done. The moment your job needs two of them in a row, the wiring is yours.
18 skills, 269 operations, no cross references. Each SKILL.md describes when to trigger and what comes back, and says nothing about the skill you are going to call next.
The format has no dependency field. Order is not declared anywhere, so it lives in your head until you write it into a system prompt and hope it survives the next session.
The condition between two calls is prose. It has to be tight enough that an agent reading it literally stops when the audit fails instead of continuing to the swap.
> Skillsmith does all three and hands back the file.
Nothing is generated behind your back. You see which skills matched and how strongly, where each gate stops the run, and what the file says, before it is written.
watch smart money on BSC, audit the token before anything else, and only swap if the audit is clean and the pool is deep
The index mirrors Binance Skills Hub. 18 skills, two namespaces, every one of them security reviewed before listing. Skillsmith never invents a skill and never edits one.
Open the hubSpot, USD-S futures and Convert through binance-cli. The exchange surface an agent trades on.
Connect, sign, swap, transfer, approve, stake, bridge. Every on-chain wallet operation an agent can run, inside the limits you set.
Top trader rankings by PnL, win rate, volume. Scores a single address on six dimensions and finds wallets holding a given token.
World Cup match probabilities and news insight, with correction signals you supply, ahead of a prediction market trade.
Ondo tokenized US equities: trading status, corporate actions, on-chain supply, fundamentals, candles.
Smart money events, platform strategies and your own meme or fomo strategies, plus backtests and credit management.
Watch groups of wallets. Consensus, accumulation and distribution, sector rotation, anomaly orders, live WebSocket push.
Ranked feeds across the whole market: hype, trending, Alpha, smart money net inflow, Pulse breakout score, trader PnL.
Fiat rails by country: payment methods, limits, rates, plus the caller's own order history.
Launchpad lifecycle feed for Pump.fun and Four.meme, filtered by dev behaviour, age and cap, with AI detected narratives.
Buy crypto with fiat or push from a Binance account straight to an external address, no manual withdrawal step.
P2P ads, order history, appeals and merchant profiles, plus publishing and managing your own advertisements.
Binance Pay send and receive. QR payment from the funding wallet, PIX auto detection, receive links.
One address, one chain, every token held right now with price, 24h change and quantity.
Contract and trading risk on a token before you touch it. Honeypots, scams, malicious code.
Search, metadata, live market data and OHLCV for one token by keyword, symbol or contract address.
Publish to Binance Square: short text, up to four images, long form with a cover, or video.
Discrete smart money buy and sell events with trigger price, current price, max gain and exit rate.
A published build shows its full sequence before you take it. Install it unchanged, or open it in the composer and move a gate.
All 8 builds? marks a gate between two calls, > marks a hand off with no condition
100,000,000 SKLSM, fixed, no mint function. The token enters through the market and leaves through payment. 30% of every stablecoin payment buys it back, weekly, on chain.
Read the economicsUnlimited builds and rebuilds
Check the thresholdFour things are out of scope on purpose. They are written here rather than discovered later.
Skillsmith returns a file. Installing it, committing it, or submitting it anywhere is your call. Nothing is pushed to a registry on your behalf.
A source skill can change after your build is generated, and your file will keep calling it by name. Change tracking is the first post launch update, not part of this release.
Matching reads the published SKILL.md text as written. When a source skill describes itself loosely, the match is loose, and the review screen is where you catch it.
Binance Skills Hub only. Other catalogues on the agentskills.io format come after the first release, once cross hub sequencing is worth the added surface.
No. It reads what Binance Skills Hub publishes and writes an instruction on top of it. The skills stay where they are, owned by their authors and reviewed by Binance. Skillsmith adds a layer, it does not fork anything.
As text the agent reads at run time. The SKILL.md format has no formal branching field, and it does not need one: the hub's own skills already use PREREQUISITE lines and references to other skills the same way. Skillsmith writes that pattern precisely instead of loosely.
Your file keeps calling it by name, so behaviour can drift from what the build assumed. This release does not watch for that. Rebuild when a skill you depend on changes, and version tracking arrives in the first update after launch.
It is plain markdown. Change a gate, drop a step, rename it, commit it next to your agent config. Skillsmith has no runtime and never calls back to check on the file.
Anything that reads the agentskills.io format. The file installs with npx skills add, the same command you use for a single skill from the hub.
No. The first build is free and needs no wallet at all. A wallet matters only when you want the SKLSM discount or the hold based subscription.
No. Skillsmith reads a public catalogue and writes files against a public format. It has no affiliation with Binance and no special access to anything.
No wallet, no key, no signup wall. Describe the job and read the plan before anything is written.