validate
100 / 100 · Low risk
Fine to try.
Verify a change is ready to ship by checking it against its acceptance criteria and running the repo's own quality gates in order, then report a pass/fail verdict with the exact failures. Use to decide go/no-go right before shipping — when you want a pass/fail verdict against acceptance criteria and the repo's quality gates (lint/build/test), not a code critique (use `review` for that). It reports — it does not fix (route failures to `pr-fix`/`implement`) and does not ship.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'validate' ] || [ -L ~/.agents/skills/'validate' ]; then echo 'A skill folder named validate already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/ronaknnathani/relay' "$d" && git -C "$d" checkout --quiet '5ab51c2d8af79f04294f91621a5b65e21f39dd53' -- 'skills/validate' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/validate' ~/.agents/skills/'validate' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'validate' ~/.claude/skills/'validate' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/ronaknnathani/relay/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-10 | 5ab51c2 | 100 |