regenerate-grpc-stubs

Regenerate Python + TypeScript gRPC stubs after editing proto files. Use when proto/*.proto changes, imports from bindu.grpc.generated fail, CI reports generated-code drift, or HandleMessages calls fail with proto mismatch.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The content is highly actionable and well-structured, with executable commands throughout and clear validation checkpoints. The main improvements are trimming the redundancy between the Safety/Execution Contract/Never-do sections and adding an explicit error-recovery loop.

Suggestions

Add an explicit feedback loop after the verification steps (e.g., 'If mypy, the build, or integration tests fail, fix the proto or regeneration and re-run from step 2').

Consolidate the overlapping guidance between 'Safety', 'Execution Contract', and 'Never do' to remove repeated statements about not editing generated dirs and not regenerating a single language.

Clarify what a 'version bump plan' for breaking changes should look like, or link to where that process is documented, since step 1 references it without detail.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanations of protobuf/gRPC basics), but the Execution Contract, Safety, and 'Never do' sections overlap somewhat and could be consolidated.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every step (git diff, generate_protos.sh, mypy, npm build, pytest) plus a concrete commit-message template covering the common case.	5 / 5
Workflow Clarity	Clear seven-step sequence with explicit validation checkpoints (mypy, build, integration tests) and an Execution Contract checklist, but it lacks an explicit fix-and-retry feedback loop if validation fails.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, self-contained at a single level, and the only references are one-level links to real repo files (proto, docs); no nested or buried references.	5 / 5
	Total	18 / 20 Passed

Description

87%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.

The description is strong: it states a concrete capability, gives an explicit 'Use when' clause with four specific trigger scenarios, and is tightly scoped to a distinct niche. Minor room to add a few natural synonyms, but it is already well above average.

Dimension	Reasoning	Score
Specificity	Names concrete actions (regenerate Python and TypeScript gRPC stubs) tied to a specific domain; it lists two distinct generation targets rather than one abstract action, with only minor coverage gaps.	4 / 5
Completeness	Explicitly states both what the skill does ('Regenerate Python + TypeScript gRPC stubs after editing proto files') and when to use it via a clear 'Use when' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides several concrete, codebase-anchored triggers ('proto/*.proto changes', 'bindu.grpc.generated fail', 'CI reports generated-code drift', 'HandleMessages calls fail with proto mismatch') that a developer would naturally say, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (cross-language gRPC stub regeneration for this specific codebase) with highly specific triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: GetBindu/Bindu
Path: .agents/skills/regenerate-grpc-stubs/SKILL.md
Commit: 7d5b6d2

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.