I never use skills, I think they're kinda overrated, it's just text files? I just tell my clanker what to do and how which is similar I think
Replying to @levelsio @TermiusHQ
Curious how you use skills to get new chats up to speed on repos? Or do you use huge compacted threads? I keep all the details in a Markdown file I reference (deploy details, product intent, etc), but feel like there’s a missing opportunity to use a skill to train agents about repos (esp when I have to work with multiple repos for a feature)

May 23, 2026 · 9:22 AM UTC

102
17
1,132
225,778
Sort replies: Relevant Recent Liked
Replying to @levelsio
The only skill I find invaluable is taste-skill I describe my product idea and have it by generate 3 sample renders using $imagegen-frontend-web Then have it use my favorite render of the options to build with $image-to-code
3
723
Replying to @levelsio
I didn’t either until I decided to abstract all my business metrics as an api and told a skill how to do it Now I say “use Chrome to audit my Google Ads account, then figure out based on my company metrics using $companyskill if I’m optimized or if any changes need to be made, compare it to seasonality data” Allows it to find recent COGS data, performance, etc and revise ads/road targets etc Also do this by having it browse my Google Analytics accounts and find emerging keywords to implement in my website copy and/or launch SEO pages based on the intelligence it finds, but that’s not a skill Anyway like you I don’t really use skills until I built this one
463
Replying to @levelsio
Is that very repeatable? Do you not find yourself typing the same thing over and over?
1
13
3,396
No not rly, or I just copy paste
2
10
2,994
Replying to @levelsio
I did like the three.js skills for vibejam tho. They have so much knowledge i don't have!
1
10
7,064
Ah yes that makes sense, sometimes I just copy paste documentation or a URL to docs
2
19
6,733
Replying to @levelsio
Skills are just for when you want to bottle/save some way of doing something
32
2,419
Replying to @levelsio
Same, but these are useful. RTK -> appends to each command and get rid of the unnecessary things from it automatically -> less token usage Caveman -> removes unnecessary blablabla from to output -> straight to the point Superpowers -> for complex features it is sometimes better in the planning phase
2
31
4,097
Replying to @levelsio
Skills are for people who are too inexperienced / stupid to tell their AI what to do. They revel in being able to “install a skill” to use a well-documented API / SDK that they wouldn’t even know exists. If you need to use a skill, that’s a skill issue (99% of the time).
1
12
1,087
Replying to @levelsio
I use skills for repeatable tasks, once an agent does something well i distill it into a skill and I have several per project for repetitive tasks, most of them aren't about coding or code review, but about agents using an API in a specific way or for browser / computer use
10
596
Replying to @levelsio
skills are useful for workflows and progressive disclosure of knowledge model wasn't trained on, e.g. "make-hyperframes-video-in-my-brand-style". but most skills like "marketer" or "growth-hacker" are beyound useless, they're harmful.
1
1
6
2,269
Replying to @levelsio
I love skills! Most skills are just elaborate system prompts and a way to make & share custom LLm memory Also way better than 99% of MCPs, just point it at an api and tell it to make a skill and now you have your own custom MCP Helpful because I don’t want to type the same long commands over and over Also nice because you can make it automatic, kinda like training your ai to do something again later Becoming popular in big companies since you can have many people making skills and sharing them, now your agent can do things you didn’t even know existed
8
665
Replying to @levelsio
Try create a few for things you notice yourself repeatedly doing They are like prompts Claude will automatically invoke when contextually relevant Them being “just text files” is what makes it such an elegant system
1
7
1,157
Replying to @levelsio
I'd been feeling imposter syndrome about this for a while. Hearing all of these people go on and on about their crazy ass skill setups with no apparent improvement in productivity
1
4
473
Replying to @levelsio
You will get better result with a well written skill and don’t have to repeat all the time. At least if it’s up to date.
3
1,140
Replying to @levelsio
Skill issue :)
2
194
Replying to @levelsio
They’re ways of packaging instructions so you don’t need to go into detail every time We eval our skills and get genuinely better results with them, but most skills out there are just vibe coded slop without data backing it
2
294
Replying to @levelsio
I have like a stash of prompts that I use repeatedly I guess people refer to those as skills
1
164
Replying to @levelsio
they're excellent and very useful
1
82
Replying to @levelsio
skills are only useful for teamwork to streamline everyone's output
1
230
Replying to @levelsio
No different than using packages, which you probably do If someone else has already written something, no need to rewrite it yourself
1
186
Replying to @levelsio
Thought the same, but some are good.
1
565
Replying to @levelsio
Skills aren't only text, the can include scripts that can be run, too
1
267
Replying to @levelsio
ive been analysing what they do a lot, often it looks up skills automatically and yea i should turn it off because its a verbose waste of tokens eg in this example when it looks up how to use git when it knows already how to use git its in the weights....
the problem with skills right now often is just that they are too verbose prompts written by people :( like this one for github. like the model can already use github and this entire thing was wasted tokens by codex, like skills are great just dont make a skill for something the model can already do... ..(the yeet skill here in codex cli is used instead of just asking the model to use git which would have worked instead of reading this huge document about git)
1
674
Replying to @levelsio
Think it is like a script. Use it for repeated tasks
122
Replying to @levelsio
I’ve found it to be helpful when getting the agent to help with a tool (clerk cli). But it’s really just a substitute for looking up docs. Skills are very useful for agents completing business tasks though cause those processes change for every company
220
Replying to @levelsio
Skills sit higher in the prompt stack. That’s the only reason to use them vs playbook / SOP workspace files
248
Replying to @levelsio
Never download a skill, but when you find yourself doing something over and over with an agent, in different projects, the agent sometimes skips memory or fixed instructions, so a skill ensures it gors through the right process I have one for insrance to search for info, it goes through the exact process i want to search X, the web, etc
187
Replying to @levelsio
Write specs > Let AI create build-plan.md > One step in the plan is one prompt > Follow steps > When done, tweak, refactor, and redesign.
46
Replying to @levelsio
Skills are documentation, indeed. They are also a prepackaged prompt to refresh your context on demand with specific instructions and knowledge around processes. The only thing I want around d skills is the ability to eject them from the context once they are used.
105
Replying to @levelsio
They are useful in brownfield apps with a bunch of ppl working on things I think
152