Agent skill

Build And Verify

Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures.

Apache-2.0Auto-check passedTesting & QA

Install Build And Verify

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a claude-code

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

GitHub CLI

$ gh skill install timeplus-io/proton build-and-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/timeplus-io/proton.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/build-and-verify .claude/skills/build-and-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/

Paste into Claude Code

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .claude/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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

$skill-installer install https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify

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

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton build-and-verify --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/build-and-verify .agents/skills/build-and-verify && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .agents/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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.

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton build-and-verify --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/build-and-verify .cursor/skills/build-and-verify && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .cursor/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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

$ gemini skills install https://github.com/timeplus-io/proton.git --path .claude/skills/build-and-verify

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton build-and-verify --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/build-and-verify .gemini/skills/build-and-verify && rm -rf skills-src

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

Paste into Gemini CLI

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .gemini/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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.

GitHub CLI

$ gh skill install timeplus-io/proton build-and-verify

Installs 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).

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/build-and-verify .github/skills/build-and-verify && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .github/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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.

skills CLI

$ npx skills add timeplus-io/proton --skill build-and-verify -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton build-and-verify --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/build-and-verify .opencode/skills/build-and-verify && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "build-and-verify" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/build-and-verify into .opencode/skills/build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-and-verify", 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: build-and-verify
GitHub stars: 2.3k
Token cost: ~1.3k tokens
SKILL.md length: 268 words
Files: 7 (incl. references)
Skills in repo: 7
Repo updated: Sep 20, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures.

The user mentions building
SKILL.md covers Binaries, Part 1 — Build, Part 2 — Test and Server (manual start/stop), plus 2 more sections
Calls cmake
Starting the server

What it does

Build And Verify is an agent skill from timeplus-io/proton. Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures. Make sure to use this skill whenever the user mentions building, compiling, ninja, cmake, running tests, test failures, starting the server, or pre-commit checks, even if they just say 'it doesn't build' or 'the test broke'.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/join-testing.md`, `references/mv-testing.md` and `references/smoke-testing.md`).

It sits in Testing & QA, covering SQL and Failing and flaky tests. It works with SQL and C++. The repository describes itself as: The Fastest Unified Streaming SQL Engine in a Single C++ Binary. ⚡ Millisecond latency. 100+ GB/s throughput. Continuously compute real-time context from streams, logs, metrics… The licence is Apache-2.0.

When your agent uses it

The user mentions building
Starting the server
Pre-commit checks
Even if they just say it doesnt build

Example prompts

“it doesn”
“the test broke”
“/build-and-verify”

What it can do on your machine

Read from SKILL.md and the folder at commit 1c47e60. 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:
- cmake
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

Build And Verify loads about 1.3k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 268 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.7k

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 timeplus-io/proton at commit 1c47e60, republished under its Apache-2.0 licence (© timeplus-io). 268 words, ~1,322 tokens.

Download SKILL.mdSave it as .claude/skills/build-and-verify/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: build-and-verify
description: Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures. Make sure to use this skill whenever the user mentions building, compiling, ninja, cmake, running tests, test failures, starting the server, or pre-commit checks, even if they just say 'it doesn't build' or 'the test broke'.

Build & Verify

Binaries

Binary	Path (stripped, preferred)	Fallback
Server / Client	`build/programs/stripped/bin/proton`	`build/programs/proton`
Unit tests	`build/src/stripped/bin/unit_tests_dbms`	`build/src/unit_tests_dbms`

Stripped = 90 % smaller, faster startup, matches CI. Always prefer stripped; fall back only if the file does not exist.

Source-root rule — all build* dirs embed absolute source paths. Use each worktree's own build*; never share across checkouts.

Part 1 — Build

Always configure from inside the chosen build* directory with the repo's build.sh. Do not substitute direct cmake -S/-B configure commands unless the user explicitly requests that workflow.

bash

cd build && ../build.sh Debug   # configure (once)
cd build && ninja                # incremental rebuild

Part 2 — Test

Full run (pre-commit)

bash

./run-all-tests.sh                # unit → SQL → smoke (all three)
./run-all-tests.sh --skip-smoke   # faster pass: unit + SQL only
./run-all-tests.sh --only unit    # single suite: unit | sql | smoke
./run-all-tests.sh --port <tcp>   # reuse running server for SQL + smoke

Targeted run (during issue work)

What changed	Run this
C++ data structures / algorithms	`./run-unit-tests.sh <SuiteName>`
SQL parsing / planner / execution	`./run-sql-tests.sh <test_id>`
Streaming end-to-end behaviour	`./run-smoke-tests.sh -s <suite>`
Unsure	`./run-all-tests.sh --skip-smoke` then add smoke if behaviour changed

Individual scripts

All scripts auto-manage server lifecycle and accept --help.

bash

# Unit (no server needed)
./run-unit-tests.sh                          # all
./run-unit-tests.sh StorageStream            # prefix filter → StorageStream*
./run-unit-tests.sh "ParserStream.ParseDDL"  # exact case
./run-unit-tests.sh -l StorageStream         # list, don't run

# Stateless SQL
./run-sql-tests.sh                           # all
./run-sql-tests.sh 00001_select_1            # single test
./run-sql-tests.sh '0003_*'                  # wildcard prefix
./run-sql-tests.sh --port <tcp> 0003_*       # reuse running server

# Smoke
./run-smoke-tests.sh                         # all suites
./run-smoke-tests.sh -s tumble_window        # single suite
./run-smoke-tests.sh -s tumble_window -k 00_tumble_window_max
./run-smoke-tests.sh --collect-only          # list, don't run
./run-smoke-tests.sh --port <tcp>            # reuse running server

Writing tests

Change type	Add this test	Guide
C++ logic / data structures	gtest case in `src/`	references/unit-testing.md
SQL behavior / streaming semantics	stateless `.sql` + `.reference`	references/sql-testing.md
End-to-end streaming scenario	smoke YAML case	references/smoke-testing.md

Server (manual start/stop)

Only needed when running SQL or smoke tests with --port / --reuse-server.

bash

./start-local-proton.sh             # prints tcp: and table_http: ports
build/programs/stripped/bin/proton client --port <tcp>
kill $(cat tmp_data_<tcp>/proton.pid)      # stop by port

Runtime data and logs: ./tmp_data_<tcp>/ — removed automatically on exit when the test script started the server. When using --port/--reuse-server, the directory is left untouched. Test reports: tmp_data_<tcp>/logs/sql/ and tmp_data_<tcp>/logs/smoke/ (server-owned mode); ./tmp/sql_reports/ and ./tmp/smoke_logs/ (reuse mode).

Parallel-safe — each start-local-proton.sh picks a free port automatically; multiple instances (or concurrent agents) coexist without conflicts.

Debugging

bash

# Running queries / stream state
build/programs/stripped/bin/proton client --port <tcp> \
  --query "SELECT * FROM system.processes"
build/programs/stripped/bin/proton client --port <tcp> --query "SHOW STREAMS"
build/programs/stripped/bin/proton client --port <tcp> --query "SHOW VIEWS"

# Server logs
tail -f ./tmp_data_<tcp>/data/var/log/proton-server/proton-server.log
tail -f ./tmp_data_<tcp>/data/var/log/proton-server/proton-server.err.log

References

Topic	File
Unit tests: options, writing gtest cases	references/unit-testing.md
SQL tests: run, write, streaming patterns	references/sql-testing.md
Smoke tests: probe setup, options, writing YAML cases	references/smoke-testing.md
Materialized view testing	references/mv-testing.md
JOIN testing patterns	references/join-testing.md

Files

SKILL.md and 6 other files (references) in .claude/skills/build-and-verify of timeplus-io/proton.

SKILL.md
references/join-testing.md
references/mv-testing.md
references/smoke-testing.md
references/sql-testing.md
references/streaming-verify.md
references/unit-testing.md

Open the folder on GitHubat commit 1c47e60

Compare with similar skills

Build And 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.

Build And Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Build And Verify this skilltimeplus-io/proton	2.3k	—	~1.3k	Automated safety check: Pass	Apache-2.0	19 days ago
Turning Engineering Analytics Into InsightsPostHog/posthog	40k	—	~2.9k	Automated safety check: Pass	Custom licence	today
Forge Project Inityaomindong1996/forge-admin	125	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Close Flaky IssuesClickHouse/ClickHouse	50k	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Pure Lsp SQL E2Efinos/legend-engine	113	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
512 Frameworks Micronaut Datajabrena/plinth	447	—	~879	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Turning Engineering Analytics Into Insights
PostHog/posthog
Official
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL.
40k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check passed
Forge Project Init
yaomindong1996/forge-admin
Bootstrap a new project from this Forge template end to end, or reset a Forge database into a clean template system.
125 GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check: notes
Close Flaky Issues
ClickHouse/ClickHouse
Audit open "flaky test" GitHub issues and close those whose tests are no longer failing on master.
50k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check: notes
Pure Lsp SQL E2E
finos/legend-engine
Runs cases from the legend-engine SQL e2e parity corpus (TestPostgresParity, ~2300 SQL cases compared against a real Postgres) through the warm interpreted Pure LSP with pure-sql-e2e, so edits to…
113 GitHub stars~1.8k tokensUpdated today
Testing & QAAuto-check passed
512 Frameworks Micronaut Data
jabrena/plinth
A skill your agent uses when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and…
447 GitHub stars~879 tokensUpdated yesterday
Testing & QAAuto-check passed
Static Vulnerability Detector
ArabelaTso/Skills-4-SE
Statically analyze code to detect security vulnerabilities including buffer overflows, injection risks (SQL, command, XSS), insecure deserialization, improper authentication, hard-coded credentials…
253 GitHub stars~2k tokensUpdated 1 mo ago
SecurityAuto-check passed

Questions about Build And Verify

What does Build And Verify do?

Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures. Build And Verify is an agent skill from timeplus-io/proton. Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures.

When should I use Build And Verify?

Build And Verify fits situations like: the user mentions building; starting the server; pre-commit checks; even if they just say it doesnt build.

How do I install Build And Verify in Claude Code?

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

How do I install Build And Verify in Codex?

Run `npx skills add timeplus-io/proton --skill build-and-verify -a codex`. Or copy the skill folder (.claude/skills/build-and-verify in timeplus-io/proton) into .agents/skills/build-and-verify in your project. Codex loads it when a task matches its description.

Can I use Build And 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 timeplus-io/proton --skill build-and-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/build-and-verify, .gemini/skills/build-and-verify, .github/skills/build-and-verify and .opencode/skills/build-and-verify in your project.

What does Build And Verify need to run?

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

Does Build And 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 Build And 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 Build And Verify use?

Build And 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 Build And Verify use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.

What are the alternatives to Build And Verify?

Skills that share tags, products or a category with Build And Verify: Turning Engineering Analytics Into Insights (PostHog/posthog, 40k stars), Forge Project Init (yaomindong1996/forge-admin, 125 stars), Close Flaky Issues (ClickHouse/ClickHouse, 50k stars) and Pure Lsp SQL E2E (finos/legend-engine, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build And Verify?

timeplus-io (a GitHub organization) maintains it in timeplus-io/proton, which has 2,265 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 20, 2026.

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

Install Build And Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Build & Verify

Binaries

Part 1 — Build

Part 2 — Test

Full run (pre-commit)

Targeted run (during issue work)

Individual scripts

Writing tests

Server (manual start/stop)

Debugging

References

Files

Compare with similar skills

Similar skills

More from timeplus-io/proton

Related

Questions about Build And Verify