CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/buf-cli-lint-breaking-build

Wraps the buf CLI for protobuf PR gating: `buf build` (compile .proto), `buf lint` (STANDARD rules: snake_case fields, Service suffix), `buf breaking --against {ref}` (detect wire/codegen breakage vs a git/BSR baseline), and `buf format`. Use as the CI proto-lint + breaking-change gate, or to debug a breaking failure by rule ID (e.g. FIELD_NO_DELETE_UNLESS_NUMBER_RESERVED) and pick the FILE/PACKAGE/WIRE_JSON/WIRE ruleset per consumer. This is the detection TOOL that enforces the rules and carries the catalog of what is breaking and why (field-number reservation, wire-safe vs wire-incompatible changes, oneof/map constraints, the four buf categories) in references/versioning-strategy.md; for cross-service schema contract testing use protobuf-compat-checking - not this.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body that splits detail into real reference files and sequences the three gates clearly. Minor conciseness trims and an explicit validation checkpoint would push it to the top band.

Suggestions

Add an explicit 'if any gate emits output, stop and fix before continuing' checkpoint between build/lint/breaking to make the validation loop literal rather than implied by `&&`.

Trim explanatory asides like 'Equivalent to protoc compilation but reads buf.yaml for paths' that restate what Claude can infer from the command.

Move the '1.32.0 or higher' version pin into a short prerequisites note so the main flow stays free of time-sensitive detail.

DimensionReasoningScore

Conciseness

Mostly lean and operational with dense tables and copy-paste commands, but includes a few trimmable asides (e.g. 'Equivalent to protoc compilation but reads buf.yaml for paths') and a version pin that could live in a dedicated note.

4 / 5

Actionability

Fully executable throughout: chained pipeline command, complete `buf.yaml`/`buf.gen.yaml` configs, JSON output flags, and failure→rule→fix tables covering the common cases.

5 / 5

Workflow Clarity

The build→lint→breaking sequence is explicit with `&&` chaining and silent/output validation, plus an anti-patterns table for error recovery, but lacks an explicit validate-then-proceed checkpoint loop.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled one-level-deep references to real bundle files (versioning-strategy.md, buf-breaking-rules.md, ci-integration.md); the breaking-rule catalog is correctly split out rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, specific description that states concrete actions, explicit trigger guidance, and a clear boundary against a sibling skill. It is slightly jargon-heavy and light on file-extension/synonym triggers, but otherwise strong.

DimensionReasoningScore

Specificity

Names four concrete commands (`buf build`, `buf lint`, `buf breaking --against {ref}`, `buf format`) with per-command behavior and a sample rule ID, giving comprehensive coverage of the tool's actions.

5 / 5

Completeness

Explicitly answers 'what' (wraps the buf CLI for build/lint/breaking/format) and 'when' ('Use as the CI proto-lint + breaking-change gate, or to debug a breaking failure by rule ID') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong domain keywords (`protobuf`, `buf`, `proto-lint`, `breaking-change gate`, `FILE/PACKAGE/WIRE_JSON/WIRE`) but only one file extension (`.proto`) and few synonyms, so a couple of natural user phrases are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (single-service proto-PR gating) and explicitly disambiguates the adjacent skill ('for cross-service schema contract testing use protobuf-compat-checking - not this').

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents