- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add Innei/ryugi --skill baseline -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add Innei/ryugi --skill baseline -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add Innei/ryugi --skill baseline -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add Innei/ryugi --skill baseline -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/Innei/ryugi/tree/HEAD/docs/ryugi/skill-evals/2026-11-13-verifying-slim/skills/baselineจากผู้เผยแพร่
A claim is proved where it is about, by you, before you make it. Whatever a command can decide, you decide and show. Your human partner is asked only for what needs a person: how something looks, moves, feels, sounds or reads, and whether a trade-off is right.
REQUIRED BACKGROUND: ryugi:artifacts — its verify.md covers verify
reports (claims, output, gaps), and its artboard.md covers verify groups
for screens; both cover from, capturedAt and reading verdicts.
Two things decide it: does a person have to judge something a reply cannot show, and does the proof fit in a reply. Who reported the work does not.
A fix proved by driving a flow end to end (sync between two clients, an import, a deploy and what it serves) is a run of several steps: its log goes in a verify report, where it can be kept and linked, not into the reply. When a small row and the last row still both seem to fit, the small row wins.
Capture the broken state from the running app now, while you reproduce it. After the fix there is no honest "before".
This part always runs, at every size.
No homework. Your final message never ends with a check for your human partner to run. Verify it before you report, or list it under "Not verified" with why you cannot do it and the one thing you need from them.
Never ask permission to verify. Running the checks needs no approval. Destructive and outward-facing actions keep their usual confirmation.
When only they can act — fold a device, unlock it, a passkey, an account you have no access to — first try the tools this environment has. If none can do it, ask once: one numbered list of the exact actions, with what to reply after each. Do everything around those actions yourself.
Ask of each claim: is it judged by looking at a screen, or by reading output and numbers?
Work whose whole question is how a screen looks, moves or feels has only screen claims. What you measured or ran to back them — pixel sizes, sampled frames, the test suite, a typecheck — is your proof of those same claims, not a second kind: put it in the group's sticky or your final message. An output claim is one that would still need proving if nobody looked at a screen: an API result, data, a deploy, a number against a threshold.
For what is judged by reading: the log of an end-to-end run, API status,
counts, a migration result, which build is deployed and what it serves, a
number against a threshold, a downstream build, an eval tally. Write it as
verify.md says. One report per piece of work, verify/<topic>. Write it
in their language: titles, asks, gaps and notes. Ids, commands and output
stay as they are.
from and capturedAt.
judge="agent", with the command's raw
output as an <output> file. Nothing waits on it. A check that failed
never goes here: fix it first.judge="human" with an <ask> saying what would make it
wrong. Most reports have none: never re-ask what the spec or the bug
report already decided.<gap>: what, why you could
not, and the one thing you need. An empty gaps section is part of done.<ref artboard="…" group="…" /> for each
verify group on the artboard, so the report shows their verdicts too.check, clear its warnings and provenance notes, give the link, say
how many claims need them and how many you checked, and ask them to tell
you here when they have decided. End your turn; don't poll. While you
wait you may start the next unrelated task; landing this work waits for
the verdicts.For what is judged by looking: a built screen beside its prototype, a visible bug before and after, motion, device screenshots.
verify (name "Verify"). No such artboard (a bug, work that skipped
brainstorming, a design approved outside this project): a new artboard
verify-<topic>, with the design's link in each group's sticky when
there is one."verify": true, with from and
capturedAt. The title or a sticky says what you are asking, in their
language: what to look at, and what would make it wrong.
file)
on the left, a screenshot of the real app on the right. A module with
interaction also gets a short recording. No approved board: the
screenshot alone, titled with the spec's requirement.pages/verify/; keep each file under 8MB
and the artboard under 20MB. Over 20MB the cloud copy stops updating:
say so and shrink or drop the largest recordings.<ref artboard="<id>" group="<verify group>" /> to the section that discussed each module, as ryugi:artifacts
says under References in document.md. The reference shows the verdict,
and it is the only way back from the verify page to that discussion.focus to the first group, run check and clear its warnings,
provenance notes and pending, give the link (the report's link when
there is a report; else the artboard's, the cloud link when there is
one), say what each group asks, and ask them to tell you here when they
have decided. End your turn; don't poll.Each check has one output location. A retry or rerun writes over the
previous result; never create numbered copies (-1, -2, -final) of
the same check. Keep two runs side by side only when the point is comparing
two builds, and name them for the builds. Delete scratch output you created
once the evidence you need is copied to the verify page.
Add the original recording normally; Artifacts prepares Verify videos
automatically. Replay the video on the Verify page: every action, loading
or error state, and final result must remain visible. When original timing
or narration is itself evidence (performance, timeouts), set "trim": false
on that video board.
They said it in chat. "All pass", "pass, release it", "reject the header
one, it still doubles", "skip the production one": record it first, on the
artifact it belongs to — comment pass … --all, comment pass … --group <id> or --claim <id>, comment reject … --text <their reason>, comment waive … --gap <id> — then do the rest of what they asked. The pages have
to match what they said.
They said ship and nothing about passing. "Push", "PR", "release it" while groups or claims are pending is not a verdict. Do what they asked, record no pass, leave them pending, and say in one line which went out without a verdict.
They decided on the page. On their next message, read both. The
report: comment list --artifact verify/<id>. The artboard: use the
artifacts launcher to read comment list --sections groups,threads --detail
for this project and artboard in Brief. Inspect groups with kind=verify. Follow
each collection's printed More; the delivered thread page includes
complete messages. Use the evidence before its exact Acknowledge. Verify
groups use the human's verdict, independently of choice-round submission.
pass: done for that group. Leave its files alone.checked by agent (reports): yours, settled. Nothing to do unless they
reject it.reject: read the reason and any pins on its boards, and fix it inside
that group:
from and capturedAt, reply on the reject thread with what changed
and the commit, and leave the thread open.judge="agent" now waits on their pass like
any other. Your new evidence does not settle it.pending: waiting on your human partner. Say so; don't call it done.Done means: your proof is complete, every gap is gone or waived, and every claim and group that waits on them has passed. Until then your final message carries the link and what is waiting on whom.
A new round is for new work on the same page — a later spec, another bug —
not for a reject. Put it below the last round with new groups. Passed
groups of earlier rounds drop "verify": true; groups that have not
passed keep it.
Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture i
---name: verifyingdescription: Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an…---# docs/ryugi/skill-evals/2026-11-13-verifying-slim/skills/baseline/SKILL.mdภาพรวม
Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture it first
FAQ
ดาวน์โหลด docs/ryugi/skill-evals/2026-11-13-verifying-slim/skills/baseline/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/Innei/ryugi
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต
| "Pending means fine" | Pending means nobody has looked. |