third-party-integrations — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited third-party-integrations (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
When a val uses any external service, follow this order — do not skip steps and do not write integration code from training-data memory alone. Val Town's guides have platform-specific patterns and required workarounds that won't be in your training data.
https://docs.val.town/guides/, but the slug isn't always just the service name — some are grouped under a category (e.g. databases/neon-postgres/, browser-automation/kernel/) or live on a sub-page (slack/agent/). Don't guess the URL: fetch the docs sitemap at https://docs.val.town/sitemap-0.xml (it lists every docs URL), find the guides/… entry that matches the service, and fetch that page before writing any integration code.Deno.env.get("KEY_NAME") to read them, and document the required env vars in the README so the user (or anyone remixing the val) knows what to set. Whenever you reference an env var the user needs to set, show the raw, full URL to the prefilled Val Town env var editor on its own line, in this exact format: 👉 Add KEY_NAME here: https://www.val.town/x/HANDLE/VAL_NAME/environment-variables?key=KEY_NAME. Keep the URL visible (not hidden behind link text) — it's the call-to-action.Services with dedicated guides today — not exhaustive, so use the sitemap from step 1 as the current source of truth:
std/email instead — see the email skill)std/sqlite instead — see the sqlite-storage skill)std/oauth instead)Integration code is the most common place models hallucinate. APIs change, auth flows get reworked, and platform constraints (no filesystem, no subprocess) break naive approaches. The Val Town guide is the source of truth for what currently works on the platform.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.