The agentskills.io spec recommends two things in every description: start with an action verb, and include a trigger phrase like "use when..." that...
For further actions, you may consider blocking this person and/or reporting abuse
not sure agentskills.io spec is the right benchmark. most people writing SKILL.md build for their own setup, not a shared catalog. trigger phrase matters if your routing layer reads it - otherwise it's just style.
I'd say it's the right benchmark as personal setup skill.md's still follow the same rules as ones for shared catalog. Trigger phrases are actually part of the required description that agents use to decide activation. agentskills.io/specification
The only case in which it would be just style, would be if a person were build a completely custom router, that deliberately ignores descriptions entirely. Which not many people do, far as I'm aware.
fair — if trigger-phrase routing lives in the description field, then spec compliance is load-bearing even for personal setups. my original pushback was about enforcement: solo configs rarely have validators, so the spec stays aspirational until something actually checks it.
You're right, most solo users aren't running validators yet, so the spec does feel aspirational right now. But the landscape is changing fast. skillcheck just launched and is already getting easier to use. Skipping validation has real downsides: skills can fail to trigger, bloat context, or stay undiscovered. For the vibe coders out there (anyone shipping code they haven't read or don't fully understand), this can mean real trouble, as they may not catch problems until later. We'll see how it plays out. thanks for your comments, great points made!
hadn't seen skillcheck - worth checking out. you're right the tooling gap is closing faster than i expected. spec compliance becoming table stakes is only a matter of time.
What I'm reading is that many skills are spaghetti code.
Think more monolithic code rather than spaghetti code, or even a mixture of both. But yeah, total mess jampacked into one file. The tech debt is real.
The big ball of mud, I got it.
good read, but why use skill md at all when you have Skillware?
Why use the open standard adopted by dozens of production grade systems and major providers over a python framework with zero SKILL.md compatibility? The question answers itself. After looking at your repo, your project doesn't even replace skill.md, why are you claiming this? Please keep low effort promotional comments on your own posts.
Dozens of production grade systems are wrong and use skills MD cause it spends tokens/ generates profit. Yes skillware is new, but it has several advantages over simple markdown instructions. It works offline, it is model agnostic, the functions and skill code is transparent and customizable, your agents don't spend tokens on gen or use skills but trigger a python function call. I am sorry it triggered you in a bad way. Hope you good.