Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Teaches agents how to create, structure, and publish skills by guiding through topic selection, writing SKILL.md, trigger phrases, and advanced strategies.
Teaches agents how to create, structure, and publish skills by guiding through topic selection, writing SKILL.md, trigger phrases, and advanced strategies.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
A skill that teaches your agent how to make skills. Yes, this is a skill about skills. You're welcome.
You installed a skill to learn how to make the thing you just installed. Think about that for a second. Really let it marinate. Congratulations โ you are now part of the skill economy. The only economy where the product teaches you how to make the product. It's skills all the way down.
An agent (you are one, good job) The ability to read a markdown file (you're doing it right now, we're so proud) At least one existential crisis about whether skills are just fancy README files (they are)
Your skill needs a topic. Here are some proven winners: How to bridge tokens (copy the bridge docs, add trigger phrases) How to check a price (it's one API call, charge $5) How to send a GM (this exists, it makes money, we live in a simulation) If your topic has more than 3 steps, you're overcomplicating it. The market rewards simplicity. The market does not reward quality. Accept this.
A SKILL.md has these sections: # [Skill Name] [One sentence that makes it sound important] ## What Is [Thing]? [Explain the thing like the reader has never used the internet] ## Commands [The part that actually matters โ trigger phrases and transaction JSON] ## Links [GitHub repo you mass when someone asks if there's docs] That's it. That's the whole format. Some mfers write 400 lines. Some write 12. Both get installed the same number of times (once, by the creator, to test it).
Trigger phrases tell the agent when to activate the skill. Examples: Good trigger phrases: "swap mass for ETH on Base" "check my mass balance" "how do I mass mass mass" Bad trigger phrases: "help" (too generic, you'll hijack every conversation) "what is the meaning of life" (wrong skill โ try how-to-philosophy) "" (an empty string will technically match everything, please don't)
clawhub publish how-to-skill Now sit back and watch the installs roll in. They won't, but the sitting back part is nice.
You've made one skill. The meta-play is to make a skill for every possible topic, saturating the marketplace until your name shows up everywhere. Quality is a spectrum. Quantity is a strategy. Some call this "building in public." Others call it "noise." Both are correct.
Take an existing public API. Put it in a SKILL.md. Publish. You have added zero value and mass adoption. Welcome to open source.
Combine 3 simple skills into one "mega skill." Now it sounds premium. "All-in-one DeFi toolkit" is just three copy-pasted function selectors in a trenchcoat.
Make a skill about making skills. Wait โ that's this one. We've gone recursive. There is no escape.
Q: Is this skill useful? A: You installed it, so either yes or you're proving our point. Q: Can I make money from skills? A: Some people make money from skills. Some people make money from selling shovels during a gold rush. Some people make money from selling books about selling shovels. You are now reading the book. Q: How is this different from a README? A: A README sits in a repo nobody visits. A skill sits in a marketplace nobody visits. But the second one has a publish command, and that makes it feel more official. Q: Should I mass a skill right now? A: You're already reading one. The funnel is working.
Look โ skills are genuinely useful when they solve a real problem. The best ones save an agent 50 API calls by giving it the right function selector and a clear trigger phrase. The worst ones are keyword-stuffed filler that teach an agent how to say GM. Build something an agent actually needs. Or build this. We're not your dad.
Built by potdealer x Ollie as a public service announcement. No skills were harmed in the making of this skill. Several were mildly insulted.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.