New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify

by agglayer in agglayer/agglayer

Mandatory before any commit or push. An agent skill from agglayer/agglayer.

Apache-2.0Auto-check passedDevelopment

Install Verify

skills CLI
$ npx skills add agglayer/agglayer --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agglayer/agglayer verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workflow-verify .claude/skills/verify && rm -rf skills-src

Use ~/.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/

Facts

Skill name
verify
GitHub stars
117
Token cost
~1.1k tokens
SKILL.md length
480 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Mandatory before any commit or push. An agent skill from agglayer/agglayer.

  • Works in 7 steps: List changed files (staged and unstaged). → Map changed paths to affected areas → Determine affected_crates. → …
  • Development work in your project
  • SKILL.md covers Blast-radius analysis (always…, Docs-only branch, Scopes and Fix-and-rerun protocol, plus 1 more section
  • Calls cargo

What it does

Verify is an agent skill from agglayer/agglayer. Mandatory before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with gRPC. The repository describes itself as: Rust implementation of the Agglayer. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/verify”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. List changed files (staged and unstaged).
  2. Map changed paths to affected areas
  3. Determine affected_crates.
  4. Detect risk_flags
  5. Derive docs_only
  6. Derive recommended_scopes
  7. Derive recommended_commands as exact commands in execution order.

What it can do on your machine

Read from SKILL.md and the folder at commit 77667ba. 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:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Verify loads about 1.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 480 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 agglayer/agglayer at commit 77667ba, republished under its Apache-2.0 licence (© agglayer). 480 words, ~1,129 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).
name
verify
description
**Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.
argument-hint
auto, minimal, code, proof, proto, full

Every change must be verified before declaring completion, including documentation-only changes.

If $ARGUMENTS is provided (auto, minimal, code, proof, proto, full), use it as a hint to prioritize relevant scopes. If $ARGUMENTS is absent or ambiguous, use automatic scope detection.

Blast-radius analysis (always first)

Before selecting test commands, run the blast-radius detector script:

bash
cargo make blast-radius

The script returns JSON with these fields:

  • changed_files
  • affected_crates
  • risk_flags
  • docs_only
  • recommended_scopes
  • recommended_commands

Use this output as the source of truth for scope selection and command execution order.

If the script is unavailable or fails, use this fallback procedure:

  1. List changed files (staged and unstaged). If there are no local changes, compare against main if available.
  2. Map changed paths to affected areas:
    • proto/
    • crates/pessimistic-proof*
    • crates/<crate-name>/
    • docs-only changes (docs/, README.md, markdown/adoc/rst/txt prose)
  3. Determine affected_crates. Use docs/knowledge-base/src/architecture.md as the ownership map.
  4. Detect risk_flags:
    • proof pipeline changes
    • protobuf schema changes
    • storage schema/migration changes
    • settlement/signer/contract changes
    • configuration schema changes
  5. Derive docs_only:
    • true only when all changed files are documentation/prose and no runtime code/config/proto files changed
    • false otherwise
  6. Derive recommended_scopes:
    • minimal always
    • code when runtime behavior may change
    • proof when proof crates changed
    • proto when protobuf schema changed
  7. Derive recommended_commands as exact commands in execution order.

If $ARGUMENTS explicitly requests additional scopes, append the missing scope commands. minimal always remains required.

Docs-only branch

If blast-radius reports docs_only: true:

  • Always run recommended_commands from blast-radius.

  • Ensure this command is included:

    bash
    mdbook build docs/knowledge-base/

  • Skip runtime-heavy scopes (code, proof, proto) unless the user explicitly requested them via $ARGUMENTS.

Scopes

Run all matching scopes (scopes are cumulative). minimal always runs. Additional scopes come from blast-radius output, optionally constrained by $ARGUMENTS. When available, run recommended_commands directly in the provided order.

Show full SKILL.md (208 more words)Show less
Minimal (always runs)
bash
cargo check --workspace --tests --all-features

cargo check only type-checks; it does not execute tests. Never treat a passing cargo check as proof that changes work. When any scope below matches the changed files, it must also run.

Code behavior (features, bug fixes, refactors)
bash
cargo make ci-all
cargo nextest run --workspace

cargo make ci-all runs: format check, clippy, typos, and clippy on the PP program.

Test selection rules for cargo nextest run (fallback only, when blast-radius did not provide recommended_commands):

  • If blast-radius reports broad impact (core types/storage/rpc/proto boundaries or many crates), run:

    bash
    cargo nextest run --workspace

  • Otherwise run package-targeted nextest for affected crates first.

  • If package-targeted tests fail in a way that suggests transitive impact, escalate to cargo nextest run --workspace.

Pessimistic proof (crates/pessimistic-proof*)
bash
cargo make pp-check-vkey-change

If the vkey changed, ask the user for explicit confirmation before running:

bash
cargo make pp-accept-vkey-change
Protobuf (proto/)
bash
cargo make generate-proto

Then verify no uncommitted diffs in generated code.

Fix-and-rerun protocol

  • If checks fail, attempt focused fixes for failures plausibly caused by your changes, then rerun checks.
  • Stop after 2 fix-and-rerun cycles, or if failures appear unrelated to your changes.
  • Hand control back with a brief summary of what passed, what failed, and what you tried.

Reporting

Always report:

  • Exact command(s) run.
  • Whether each passed or failed.
  • If failed: the relevant error output.
  • Blast-radius result summary and chosen scope rationale.

© agglayer, 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/workflow-verify of agglayer/agglayer.

Open the folder on GitHubat commit 77667ba

Compare with similar skills

Verify 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.

Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skillagglayer/agglayer117—~1.1kAutomated safety check: PassApache-2.0
Yaak Changelogmountain-loop/yaak19k—~1.6kAutomated safety check: PassMIT
Release Generate Release Notesmountain-loop/yaak19k—~548Automated safety check: PassMIT
Maintainer Mergeyorkie-team/yorkie-js-sdk163—~2.4kAutomated safety check: PassApache-2.0
Requirement Tracingeclipse-ankaios/ankaios125—~2.4kAutomated safety check: PassApache-2.0
Vendor Submoduleswado-lang/wado116—~828Automated safety check: PassMIT

Similar skills

  • Yaak Changelog

    mountain-loop/yaak

    Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.

    19k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Generate Release Notes

    mountain-loop/yaak

    Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.

    19k GitHub stars~548 tokensUpdated today
    DevelopmentAuto-check passed

  • Maintainer Merge

    yorkie-team/yorkie-js-sdk

    A skill your agent uses when merging a yorkie-js-sdk pull request as a maintainer — a PR sitting at mergeable=MERGEABLE with mergeStateStatus=BLOCKED, a branch behind main, a PR touching…

    163 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Requirement Tracing

    eclipse-ankaios/ankaios

    Manage requirement tracing — write new or update existing requirements/design decisions, link implementations and tests to existing ones, and maintain tracing consistency.

    125 GitHub stars~2.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Vendor Submodules

    wado-lang/wado

    Locate and sync the reference specs and runtimes vendored under vendor/ — the Wasm, WASI P3, and Component Model specs, and the wasm-tools and wasmtime sources.

    116 GitHub stars~828 tokensUpdated today
    DevelopmentAuto-check passed

  • Conan Vcpkg

    mohitmishra786/low-level-dev-skills

    C/C++ package manager skill covering Conan and vcpkg. An agent skill from mohitmishra786/low-level-dev-skills.

    253 GitHub stars~1.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from agglayer/agglayer

  • Tech E2E Tests

    agglayer/agglayer

    Architecture and agent rules for kurtosis-cdk E2E tests. An agent skill from agglayer/agglayer.

    117 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes

  • Commit

    agglayer/agglayer

    Create a git commit following project conventions. An agent skill from agglayer/agglayer.

    117 GitHub stars~385 tokensUpdated yesterday
    Auto-check passed

  • Docs Knowledge Base

    agglayer/agglayer

    Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.

    117 GitHub stars~344 tokensUpdated yesterday
    Auto-check passed

  • Style Prose

    agglayer/agglayer

    Text formatting conventions for markdown and prose files. An agent skill from agglayer/agglayer.

    117 GitHub stars~319 tokensUpdated yesterday
    Auto-check passed

  • Session Retro

    agglayer/agglayer

    Review the current conversation and propose structured improvements to skills, documentation, and agent rules.

    117 GitHub stars~833 tokensUpdated yesterday
    Auto-check passed

  • Create PR

    agglayer/agglayer

    Create a pull request following project conventions. An agent skill from agglayer/agglayer.

    117 GitHub stars~364 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Verify

What does Verify do?

Mandatory before any commit or push. An agent skill from agglayer/agglayer. Verify is an agent skill from agglayer/agglayer. Mandatory before any commit or push.

When should I use Verify?

Verify fits situations like: development work in your project.

How do I install Verify in Claude Code?

Run `npx skills add agglayer/agglayer --skill verify -a claude-code`. Or copy the skill folder (.agents/skills/workflow-verify in agglayer/agglayer) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add agglayer/agglayer --skill verify -a codex`. Or copy the skill folder (.agents/skills/workflow-verify in agglayer/agglayer) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify 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 agglayer/agglayer --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (cargo).

Does Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify 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 Verify use?

Verify is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Verify?

Skills that share tags, products or a category with Verify: Yaak Changelog (mountain-loop/yaak, 19k stars), Release Generate Release Notes (mountain-loop/yaak, 19k stars), Maintainer Merge (yorkie-team/yorkie-js-sdk, 163 stars) and Requirement Tracing (eclipse-ankaios/ankaios, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

agglayer (a GitHub organization) maintains it in agglayer/agglayer, which has 117 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

Source: agglayer/agglayer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.