Build the solution and run unit tests to verify changes are correct.

Apache-2.0Auto-check passedTesting & QA

Install Verify

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

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

GitHub CLI
$ gh skill install valdisiljuconoks/LocalizationProvider 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/valdisiljuconoks/LocalizationProvider.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/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
180
Token cost
~159 tokens
SKILL.md length
56 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build the solution and run unit tests to verify changes are correct.

  • Works in 2 steps: Build: dotnet build → Test: dotnet test --filter…
  • Tasks that involve Internationalization
  • Calls dotnet
  • Tasks that involve Unit testing

What it does

Verify is an agent skill from valdisiljuconoks/LocalizationProvider. Build the solution and run unit tests to verify changes are correct. Use after implementing features or fixes.

Its SKILL.md is about 160 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 Testing & QA, covering Internationalization and Unit testing. It works with .NET and C#. The repository describes itself as: Database driven localization provider for .NET applications. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Internationalization
  • Tasks that involve Unit testing

Example prompts

  • “/verify”

Requirements

  • Docker

Workflow steps

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

  1. Build: dotnet build
  2. Test: dotnet test --filter Category!=Integration

What it can do on your machine

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

    • dotnet

    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 159 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 56 words of instructions outside code blocks.

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

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 valdisiljuconoks/LocalizationProvider at commit 45ae787, republished under its Apache-2.0 licence (© valdisiljuconoks). 56 words, ~159 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).
name
verify
description
Build the solution and run unit tests to verify changes are correct. Use after implementing features or fixes.

Run the following commands in sequence to verify the codebase compiles and tests pass:

  1. Build: dotnet build
  2. Test: dotnet test --filter Category!=Integration

Report results clearly. If there are failures, analyze them and suggest fixes.

If the user asks for a full verification including integration tests, run:

dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=opencover /p:CoverletOutput=coverage

Note: Integration tests require Docker to be running.

© valdisiljuconoks, 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 .claude/skills/verify of valdisiljuconoks/LocalizationProvider.

Open the folder on GitHubat commit 45ae787

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 skillvaldisiljuconoks/LocalizationProvider180—~159Automated safety check: PassApache-2.0
ScottPlot Test RunnerScottPlot/ScottPlot6.8k—~308Automated safety check: PassMIT
Csharp Testingaffaan-m/ECC276k1 repos~2.2kAutomated safety check: PassMIT
Csharp Testingaffaan-m/ECC276k—~2kAutomated safety check: PassMIT
Csharp Testingaffaan-m/ECC276k—~2kAutomated safety check: PassMIT
Csharp Tunitgithub/awesome-copilot40k1 repos~1.3kAutomated safety check: PassMIT

Similar skills

  • ScottPlot Test Runner

    ScottPlot/ScottPlot

    Run or add ScottPlot 5 tests. Use for unit-test and cookbook-test work; unless explicitly asked otherwise, restrict manual test execution to the Unit Tests…

    6.8k GitHub stars~308 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Csharp Testing

    affaan-m/ECC

    C and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

    276k GitHub starsUsed in 1 repo~2.2k tokens
    Testing & QAAuto-check passed
  • Csharp Testing

    affaan-m/ECC

    xUnit、FluentAssertions、モッキング、統合テスト、テスト組織のベストプラクティスを使用したCと.NETのテストパターン。

    276k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • Csharp Testing

    affaan-m/ECC

    使用 xUnit、FluentAssertions、模拟、集成测试和测试组织最佳实践的 C 和 .NET 测试模式. An agent skill from affaan-m/ECC.

    276k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • Csharp Tunit

    github/awesome-copilot

    Official

    Get best practices for TUnit unit testing, including data-driven tests

    40k GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed
  • Csharp Conventions

    Goldziher/ai-rulez

    C code conventions covering .NET 8+/C 12, nullable reference types, Roslyn analyzers, xUnit, record types, async/await discipline, and dependency security.

    159 GitHub stars~363 tokensUpdated today
    Testing & QAAuto-check passed

Works with

Categories

Questions about Verify

What does Verify do?

Build the solution and run unit tests to verify changes are correct. Verify is an agent skill from valdisiljuconoks/LocalizationProvider. Build the solution and run unit tests to verify changes are correct.

When should I use Verify?

Verify fits situations like: tasks that involve Internationalization; tasks that involve Unit testing.

How do I install Verify in Claude Code?

Run `npx skills add valdisiljuconoks/LocalizationProvider --skill verify -a claude-code`. Or copy the skill folder (.claude/skills/verify in valdisiljuconoks/LocalizationProvider) 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 valdisiljuconoks/LocalizationProvider --skill verify -a codex`. Or copy the skill folder (.claude/skills/verify in valdisiljuconoks/LocalizationProvider) 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 valdisiljuconoks/LocalizationProvider --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 (dotnet). Our summary lists: Docker.

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 159 tokens (SKILL.md is roughly 636 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: ScottPlot Test Runner (ScottPlot/ScottPlot, 6.8k stars), Csharp Testing (affaan-m/ECC, 276k stars), Csharp Testing (affaan-m/ECC, 276k stars) and Csharp Testing (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

valdisiljuconoks (a GitHub user) maintains it in valdisiljuconoks/LocalizationProvider, which has 180 GitHub stars. The repository was last updated on June 13, 2026.

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