CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/grpc-status-code-mapping-reference

Pure-reference catalog of gRPC standard status codes - the 17 canonical codes (OK..UNAUTHENTICATED), their numeric values, semantics, retry behaviour per AIP-194 (only UNAVAILABLE is auto-retry-safe), and the gRPC-to-HTTP status mapping used by grpc-gateway (NOT_FOUND→404, INVALID_ARGUMENT→400, PERMISSION_DENIED→403, UNAUTHENTICATED→401, RESOURCE_EXHAUSTED→429, FAILED_PRECONDITION→400 not 412, ABORTED→409, UNAVAILABLE→503, DEADLINE_EXCEEDED→504, etc.). Use when designing a gRPC service's error vocabulary, writing assertions in gRPC client tests, configuring retry policies, or mapping gRPC errors to HTTP via a gateway. Consumed by buf-cli-lint-breaking-build, ghz-load, grpcurl-cli, grpc-mock, grpc-streaming-test-author.

75

Quality

94%

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

85%

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

A dense, well-organized reference catalog with concrete executable examples and clear decision tables; the main weakness is verbatim restating of standard gRPC code definitions Claude largely already knows, which adds tokens without proportional value.

Suggestions

Trim the verbatim 'Definition (gRPC docs)' column or collapse it to a one-word gloss, since gRPC status-code semantics are largely known — keep only the numeric values, retry verdicts, and HTTP mappings that constitute the novel payload.

Consider splitting the large HTTP-mapping and retry tables into a separate reference file (e.g. references/mappings.md) and summarizing the key mappings inline, so SKILL.md reads as a tighter overview pointing to detail.

Tighten the 'Overview' framing ('Three things to get right') to a single line; the disambiguator tables already convey these points more concretely.

DimensionReasoningScore

Conciseness

Mostly efficient tables and code, but the body restates the gRPC docs' definitions verbatim for all 17 codes (e.g. 'Not an error; returned on success', 'The operation was cancelled, typically by the caller') — concepts Claude largely already knows — and the 'Overview' adds framing prose that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready executable artifacts: a retry policy JSON block, concrete pytest assertions on `grpc.StatusCode.*`, and a working error-details unpacking snippet, plus exact code↔HTTP mappings in tables.

3 / 3

Workflow Clarity

A single-purpose reference skill with an unambiguous action (look up the code/retry/HTTP mapping) and explicit disambiguator decision tables; per the simple-skills scoring note this scores 3 without needing multi-step validation loops.

3 / 3

Progressive Disclosure

A self-contained catalog with a clear overview, well-signaled single-level sections, and no nested multi-level references; the judging guideline allows a well-organized single-file skill with no external references to score 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, specific description that concisely states both what the skill catalogs and when to use it, with natural trigger phrasing and a clearly distinct niche. Third-person voice is maintained throughout, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'catalog of gRPC standard status codes', 'their numeric values, semantics, retry behaviour', and 'the gRPC-to-HTTP status mapping used by grpc-gateway' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('catalog of gRPC standard status codes... retry behaviour... HTTP mapping') and when ('Use when designing... writing assertions... configuring retry policies'), with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Natural phrasing users would say is present: 'Use when designing a gRPC service's error vocabulary, writing assertions in gRPC client tests, configuring retry policies, or mapping gRPC errors to HTTP via a gateway', covering common variations.

3 / 3

Distinctiveness Conflict Risk

A clear narrow niche (gRPC status code mapping) with distinct triggers and a named set of consumer skills, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents