Jo skill kabhi chalti hi nahi, usme syntax ki gadbadi shayad hi hoti hai. Wo load hoti hai, list mein dikhti hai, aur kabhi chuni nahi jaati — kyunki description ye nahi kehta ki wo kab apply hoti hai, ya aise shabdon mein kehta hai jo koi nahi bolta. Ye failure banawat se hi chup hai: na error, na warning, na koi ishara ki kuchh gadbad hai. Ye linter file ko waise hi padhta hai jaise loader padhta hai, bigde hisson ki soochna deta hai, aur phir lagbhag saara dhyan description par lagata hai: trigger named hai ya nahi, lambai kaafi hai ya nahi, aur shuruaat ye dohrane se to nahi hoti ki ye ek skill hai. Jin fields ko loader padhta hi nahi, wo bhi bataye jaate hain, kyunki key mein hui galti theek waisi dikhti hai jaisi ek sahi file.
Features
Frontmatter asli YAML parser se padhta hai aur batata hai kahaan toota
Loader jin fields ko nahi padhta unhe dikhata hai — key ki galti aisi hi dikhti hai
Description mein trigger phrase aur lambai ki jaanch
Description ki lambai limit ke saamne rakhkar batata hai
Instructions us lambai se upar hain ya nahi jiske neeche wo kaam nahi aate
Aisa score jisme errors suggestions se bhaari hain
File drop kijiye, ya paste
Jaan-boojhkar bigada gaya example, ye dekhne ke liye ki kya pakad mein aata hai
Skill Linter kaise use karein
SKILL.md drop kijiye ya uska content paste kijiye
Sabse gambhir se shuru karke notes padhiye
Description uthe to pehle wahi theek kijiye — asli baat wahi hai
Score saaf hone tak dobara check karte rahiye
Example
Input
description: Helps with PDFs
Output
Warning: says what the skill is, but not when to use it
Kisi skill ke kabhi na chune jaane ki sabse aam wajah yahi hai.
Common errors aur troubleshooting
Kehta hai frontmatter nahi hai, jabki saaf dikh raha hai. — Teen hyphen sabse pehli line honi chahiye: upar na khaali line, na comment, kuchh bhi nahi.
Lambe description par YAML toot jaata hai. — Jis description mein colon ke baad space ho use quote mein rakhna padta hai, warna YAML use doosri key maan leta hai.
Jis field ko main jaan-boojhkar rakhta hoon, wahi dikhaya ja raha hai. — Anjaan fields note ke roop mein aate hain, error ke roop mein nahi. Loader unhe chhod deta hai; note isliye hai ki galat likhi key sahi key jaisi hi dikhti hai.
Description ko kaam se match kiya jaata hai, isliye agar wo sirf topic batata hai — "spreadsheets ke saath kaam karti hai" — to kisi request se match karne ko kuchh bachta hi nahi. Sthiti, file ke types ya logon ki bhasha named karne wala ek phrase jod dena aam taur par poora ilaaj hai.
Trigger phrase kise maanein?
Har wo baat jo apply hone ka kshan named kare: "Jab user … maange tab", "Jab bhi migration file badle", "… se jude kaamon ke liye". Linter yahi aakaar dhoondhta hai aur na mile to warning deta hai.
Kya lamba description bura hai?
Apne aap mein nahi — limit udaar hai aur ginti dikhti bhi hai. Nuksaan lambe us description se hai jo phir bhi kabhi nahi kehta ki skill kab use karni hai; ye jodi hairaan karne ki had tak aam hai.
Kya doosron ki likhi skill check kar sakte hain?
Ye achha upyog hai. Kahin aur se laayi skill drop karte hi dikh jaata hai ki uska description aapki skills se takrayega ya nahi aur wo koi anapekshit tool to declare nahi karti.
Saaf nateeje ka matlab hai skill kaam karegi?
Nahi. Matlab itna hai ki file load hogi aur description ka aakaar waisa hai jaisa match kiya jaata hai. Instructions achhe hain ya nahi, ye faisla koi linter nahi karta.