The skills aren’t all finished.Talk them into shape.
Some of the 31 skills are rough around the edges. That is deliberate: you fix and extend them by describing what you want. You never write code. You say what is broken or what to add, and your agent does it, tests it, and shows you the result.
01What vibe coding actually means
Normally, making software better means a developer reads code and edits it. Here you skip that. You describe the problem in normal words, and the agent does the reading and the editing.
A skill is just a written-down set of instructions your agent follows. So improving one is not a coding job, it is a conversation. You say “this keeps failing when someone gives it a Robinhood link”, and it goes and fixes that.
02The four step loop
Say what you want
In plain English, in Discord. If you can describe it to a person, you can describe it here.
Let it work
It reads the skill, works out what to change, and makes the change. Ask it to explain in one line what it did.
Make it prove it
Say “test it and show me the output”. This is the step people skip, and it is the one that matters.
Repeat until right
If it is not right, say what is still wrong. Two or three rounds is normal.
03Prompts to start with
Do these in order the first time. They take about ten minutes and set you up.
Find out what needs work
@yourbot read through all the skills I installed and tell me which ones look unfinished, unclear or missing steps
@yourbot pick the weakest one and tell me exactly what is missing from it
@yourbot which skill would you improve first to make my life easier, and why?Fix one
@yourbot the rarity skill doesn't handle collections that are still hidden. add that and show me it working
@yourbot make the mint checker output easier to read, I don't understand the current format
@yourbot this skill assumes I know what a contract address is. rewrite it for someone who doesn't
@yourbot improve this skill using what we learned in this conversationTest it
@yourbot test that properly and paste the actual output
@yourbot give me a real example I can try myself to check it works
@yourbot what could still go wrong with what you just built?Keep it
@yourbot save what you just worked out as a skill so you can do it again without me explaining
@yourbot write down the steps you just took so this works the same next time04When one of them breaks
This is the most common thing you will do, and it is completely normal. Something errors, you paste the error back, it fixes it.
@yourbot that didn't work. here's what it said: <paste the whole error>
@yourbot same as last time but with this wallet address instead: <address>
@yourbot find out why that keeps failing instead of just trying again
@yourbot go back to how it was before, that change made it worse
@yourbot you said it works but it didn't. show me the proof it works before you say that again05Teach it something new
The 31 skills are a starting point. The real value is adding your own, for things you do over and over.
@yourbot watch how I check a mint before buying, then write a skill so you can do it for me next time
@yourbot make a skill for finding collections where the floor just dropped
@yourbot every time I paste a tweet you should check if it's a mint, what it costs, and if it's real. turn that into a skill
@yourbot make a skill that checks all my wallets and tells me anything I should look at
@yourbot build something that compares two collections side by side and tells me which has better odds06Build a whole small thing
Same idea, bigger. You can have it build a working page and put it online, which is what the Vercel part of the setup guide is for.
@yourbot build me a page showing every collection I hold, with images and rarity rank
@yourbot build a simple dashboard of the collections I'm watching and put it on Vercel
@yourbot make a page where I can paste a collection link and it ranks everything and shows pictures
@yourbot put this on Vercel and give me the link when it's actually live07Phrases that work
| Say this | And you get |
|---|---|
| “show me your plan before you start” | You see what it intends before it does anything, and can redirect it |
| “test it and show me the output” | The difference between a real fix and a confident sentence |
| “explain what you changed, in one line” | You stay in control without reading any code |
| “don’t spend anything / don’t change anything yet” | It does the thinking without touching your money or your files |
| “make it simpler” | It strips the clever stuff and leaves something you can follow |
| “I don’t understand this, explain it like I’m new” | A straight answer instead of jargon |
| “go back to how it was” | An undo, when a change made things worse |
| “save that as a skill” | It becomes permanent, and you never explain it again |
08Staying out of trouble
- Never paste a private key into a chat with an agent, or anywhere else. If you ever have, consider that wallet burnt and move anything in it.
- Ask for the plan before big changes. “Show me the plan first” costs you ten seconds and saves you a mess.
- One change at a time. Three improvements at once means you cannot tell which one broke it.
- Keep your money behind a “no”. Say “don’t spend anything without asking me” and it will not.
- Back up before you go deep. Ask it to save a copy of your skills first: “copy my skills folder somewhere safe”.
- If it claims success and you cannot see it, it is not real. Ask again for the proof.
All of this needs one thing
The subscription, about $10 a month, running deepseek v4.1 flash. It gives a genuinely generous amount of usage, which is what makes this kind of back-and-forth something you can do all day without watching a meter.