Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Settle a claim about a change with evidence that can be recomputed.
Apache-2.0Auto-check passed
Install Verification
$ npx skills add s3s-project/s3s --skill verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install s3s-project/s3s verification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verification .claude/skills/verification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .claude/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/s3s-project/s3s/tree/main/.agents/skills/verificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add s3s-project/s3s --skill verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install s3s-project/s3s verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verification .agents/skills/verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .agents/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add s3s-project/s3s --skill verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install s3s-project/s3s verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verification .cursor/skills/verification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .cursor/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/s3s-project/s3s.git --path .agents/skills/verification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add s3s-project/s3s --skill verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install s3s-project/s3s verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verification .gemini/skills/verification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .gemini/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install s3s-project/s3s verificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add s3s-project/s3s --skill verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verification .github/skills/verification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .github/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add s3s-project/s3s --skill verification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install s3s-project/s3s verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verification .opencode/skills/verification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verification" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/verification into .opencode/skills/verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verification- GitHub stars
- 311
- Token cost
- ~977 tokens
- SKILL.md length
- 625 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Settle a claim about a change with evidence that can be recomputed.
- A change claims to fix
- SKILL.md covers Two controls, Keep a gate as a script, Local gates are not CI gates and Measure the same way twice, plus 4 more sections
- Calls just and git
- Improve something
What it does
Verification is an agent skill from s3s-project/s3s. Settle a claim about a change with evidence that can be recomputed. Use when a change claims to fix or improve something, when a gate result has to be trusted, when a test is meant to prove behaviour, or when a port or a rewrite must be shown equivalent.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Rust. The licence is Apache-2.0.
When your agent uses it
- A change claims to fix
- Improve something
- A gate result has to be trusted
- A test is meant to prove behaviour
Example prompts
- “/verification”
What it can do on your machine
Read from SKILL.md and the folder at commit 0fdcb86. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
justgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verification loads about 977 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 625 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from s3s-project/s3s at commit 0fdcb86, republished under its Apache-2.0 licence (© s3s-project). 625 words, ~977 tokens.
Download SKILL.mdSave it as
.claude/skills/verification/SKILL.md (or your agent's skills folder).- name
- verification
- description
- Settle a claim about a change with evidence that can be recomputed. Use when a change claims to fix or improve something, when a gate result has to be trusted, when a test is meant to prove behaviour, or when a port or a rewrite must be shown equivalent.
- license
- Apache-2.0
Verification
A claim about a change is settled by an artifact somebody else can recompute: a command and its exit code, a count, a tree, a diff, a file. Reading the diff again is not verification, and "should work" is not a result.
Two controls
Every check needs both directions.
- Red control — inject the failure the check claims to catch and watch it fail. Rename the field a test compares, break the branch a parser is supposed to reject, corrupt the input: if nothing goes red, the check proves nothing.
- Positive control — run the same check on the good input and watch it pass, so a check that always fails, or one that matches nothing at all, is not mistaken for agreement.
A new script that validates something deserves the same pair before it is trusted: feed it a sample that must fail and a sample that must pass.
Keep a gate as a script
Run a gate as one script that writes its output and its exit code to a log, so a failure can still be attributed afterwards. The gates here are just dev (fetch, format, codegen, lint, test), just ci-rust (format check, clippy with -D warnings, tests, codegen, assert_unchanged) and the nightly clippy line; just ci-rust fails when a codegen run leaves an uncommitted diff, because assert_unchanged compares the tree with git status.
Local gates are not CI gates
CI runs a matrix nobody runs locally: two toolchains, the MSRV, macOS and Windows, a wasm build, both feature sets, and jobs that are filtered by path. Two consequences:
- A green check does not prove your code ran.
Audit,Fuzzand thee2ejobs skip when the paths they watch are untouched, and a lane can be allowed to fail: therustjob marks its nightly lanecontinue-on-error, so a nightly-only lint does not block a merge. Reproduce the gate you care about locally. - A local pass does not prove CI passes. Run what the job runs, with the same flags, before saying a failure is fixed.
Measure the same way twice
An expectation only matches the measurement that produced it. Do not reuse a number that came from another tool: the coverage JSON, the LCOV file and the text report of one profile count lines differently. Recompute with the command the check uses, and name the source of every number.
Show full SKILL.md (232 more words)Show less
Flakes
A test that failed once is not understood until two cases are separated: run it alone N times, and run the whole suite N times. If only the parallel run fails, look for shared state — ports, timers, files, a global; if the single run fails as well, it is a bug. Record the first failure with its environment instead of retrying until green.
Mutation as a last resort
When the question is "could this test ever fail", mutate one production line, run the test, then restore the file byte for byte. Point the build at a separate target directory: a mutated artifact left in a shared cache poisons later runs. Keep the mutation to the lines the test claims to cover.
Ports and rewrites
A rewrite is verified against the thing it replaces, not against its own output: build a table of inputs, run both implementations on every row, and compare stdout, stderr, exit code and bytes where the bytes are the contract. The xtask report subcommands were accepted that way, by feeding the retired scripts and the new ones the same mint log and the same JUnit report.
What to write down
State the claim, the command, the exit code and the artifact. When a claim cannot be settled with what is at hand, name the artifact that would settle it and leave the question open rather than softening it.
© s3s-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/verification of s3s-project/s3s.
Open the folder on GitHubat commit 0fdcb86
Compare with similar skills
Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verification this skills3s-project/s3s | 311 | — | ~977 | Automated safety check: Pass | Apache-2.0 | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 | |
| Firecrawl Page Scrape Integrationfirecrawl/firecrawl | 190k | 1 repos | ~944 | Automated safety check: Pass | ISC | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Firecrawl Page Scrape Integration
firecrawl/firecrawl
Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Rust TDD Workflow
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
More from s3s-project/s3s
All 10 skills in this repoCode Coverage
s3s-project/s3s
Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.
Gh Stack
s3s-project/s3s
Work with stacked pull requests in this repository using gh stack.
Code Review
s3s-project/s3s
Review a pull request or a proposed change to this repository.
Codegen
s3s-project/s3s
Change generated code in this repository. An agent skill from s3s-project/s3s.
Fuzz Testing
s3s-project/s3s
Add, run or schedule a fuzz target in this repository. An agent skill from s3s-project/s3s.
Mutation Testing
s3s-project/s3s
Run or triage the mutation sweep in this repository. An agent skill from s3s-project/s3s.
Related
Works with
Questions about Verification
What does Verification do?
Settle a claim about a change with evidence that can be recomputed. Verification is an agent skill from s3s-project/s3s. Settle a claim about a change with evidence that can be recomputed.
When should I use Verification?
Verification fits situations like: A change claims to fix; improve something; A gate result has to be trusted; A test is meant to prove behaviour.
How do I install Verification in Claude Code?
Run `npx skills add s3s-project/s3s --skill verification -a claude-code`. Or copy the skill folder (.agents/skills/verification in s3s-project/s3s) into .claude/skills/verification in your project. Claude Code loads it when a task matches its description.
How do I install Verification in Codex?
Run `npx skills add s3s-project/s3s --skill verification -a codex`. Or copy the skill folder (.agents/skills/verification in s3s-project/s3s) into .agents/skills/verification in your project. Codex loads it when a task matches its description.
Can I use Verification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add s3s-project/s3s --skill verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification, .gemini/skills/verification, .github/skills/verification and .opencode/skills/verification in your project.
What does Verification need to run?
Going by SKILL.md and its folder, Verification needs the command-line tools its instructions call (just and git).
Does Verification access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verification use?
Verification is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verification use?
About 977 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verification?
Skills that share tags, products or a category with Verification: Update V8 Version (openinterpreter/openinterpreter, 69k stars), Firecrawl Page Scrape Integration (firecrawl/firecrawl, 190k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and Rust TDD Workflow (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification?
s3s-project (a GitHub organization) maintains it in s3s-project/s3s, which has 311 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.
Source: s3s-project/s3s on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.