Where does my SKILL.md go?
Nowhere. The check is a script that runs in this page, and pasted text is never sent to us or stored. If you give a GitHub link, your browser fetches the public file directly from GitHub, or from jsDelivr's public mirror of GitHub when GitHub's lookup limit is used up. You can read the script at /check/check-core.js.
Does a clean result mean my skill will trigger?
No. It means nothing in the file's shape is stopping it. Whether an agent picks your skill for the right request depends on what the description says and on the other skills installed beside it, and no script can judge that. Test it on real requests.
I got warnings. Do I have to fix them all?
No. Fix every FAIL. A WARN is a question to answer: a skill with no neighbours does not need a "Not for" line, and a heading that differs from the name on purpose is fine.
What exactly do I get for $19?
One email with three things: your SKILL.md as a replacement file, a list of findings that each quote the line and give the smallest fix, and a short set of test requests that should and should not trigger the skill. We tell you which checks we ran and which we could not.
What is the refund policy?
If the audit finds nothing worth changing, we refund the full amount without being asked. If you are unhappy with what you get back, reply within 14 days and we refund you. Refunds go back to the original payment method.
Can you tune a private skill?
Yes. Paste the file into your order email with anything sensitive removed. We read it to do the work and do not publish or reuse it. We never need access to your repo, your systems or your API keys.
What about GitHub's rate limit?
GitHub allows 60 anonymous lookups an hour from one network address, which a shared office or mobile network can use up. When that happens the page finds the skill through jsDelivr's public mirror instead and the check carries on. One check is skipped on that route, whether the files the body points to exist, and the result says so.