SkillWatch · open questions
three things we want to know before we build them · nothing here charges you anything
You install third-party skills and MCP servers into an agent’s context. What they change upstream, nobody watches. We already watch a public slice of that problem: 100 verified top skill/MCP repos, live risk scan reports, and verification badges. The three questions below are about what to watch for you — answer yes or no, by one click, no account, no payment.
1 · Upstream-change email alertshypothetical — $3/mo for 5 repos
If SkillWatch emailed you within 24h whenever a skill repo you installed pushed a new version (with a diff summary), would $3/month for watching 5 repos feel like fair value?
Yes, I would pay that | No, too expensive
2 · Custom-named verification badgehypothetical — $9 one-time
Projects already embed a plain "verified by SkillWatch" badge pointing at the public scan report. Would you pay $9 once for a badge that carries your project’s name and a report page you can point reviewers at?
Yes, badge + named report is worth $9 | No, the free badge is enough
3 · Batch prescan for a private registryhypothetical — waitlist vs $19/mo
The public prescan covers 100 most-starred repos. If you keep an internal skill list (company registry, curated team bundle), would you first reserve a batch scan by leaving your GitHub organisation name, or pay $19/month to scan the whole list on an ongoing basis?
Reserve a free batch scan (org name) | Pay $19/mo for ongoing registry scans
Why these are mail links
Honesty by construction: no form, no stored email, no paywall behind any button — a reply is the signal, and zero replies is equally a signal. We read every reply tagged skillwatch-q1…q3 and publish what we learn (aggregate only). Current shipped capability stays the read-only monitor + digest + badges described on pricing; none of the three questions above is billable today.
