mcpbeat

Verification Protocols

google/verification-protocols

> Standard verification pipeline to execute after modifying C++ source or header files. Use this skill to format includes, build the engine, and run core tests.

254 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
20318
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google/filament --skill verification-protocols

The instruction itself

1 sections, as written by the author

Verification Protocols

Before completing any task that modifies C++ source or header files, AI agents must execute the following verification pipeline:

  • Format Includes: Run ./tools/reorganize_headers/run.py <target>.
  • Compile Core Engine: Run ./build.sh -ip desktop debug to ensure the entire desktop target compiles cleanly with no warnings or errors.
  • Run Tests: Run the test suite binary located in the build output directory:
    ./out/cmake-debug/libs/utils/test_utils
  • Language Bindings Check: If any public APIs under filament/include/filament/ were modified, verify that matching Java and JavaScript/TypeScript bindings are implemented and up-to-date according to bindings-synchronization.

How to use it

Copy the folder

Take google/verification-protocols from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.