CtrlK
BlogDocsLog inGet started
Tessl Logo

hybrid-cloud-rpc

Guide for creating, updating, and deprecating hybrid cloud RPC services in Sentry. Use when asked to "add RPC method", "create RPC service", "hybrid cloud service", "new RPC model", "deprecate RPC method", "remove RPC endpoint", "cross-silo service", "cell RPC", or "control silo service". Covers service scaffolding, method signatures, RPC models, cell resolvers, testing, and safe deprecation workflows.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-3

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

A well-structured, actionable skill with a clear sequenced workflow, strong validation checklist, and effective progressive disclosure to real reference files. Its weaknesses are minor: some redundancy in the lengthy testing section and a few non-executable code snippets.

Suggestions

Fix the non-executable code in Step 4's error-propagation example: add the missing colon after 'def foobar(...) -> RpcTentativeResult' and change 'except e:' to 'except Exception as e:'.

Consolidate redundant testing examples in Step 7 — the three RPC-model accuracy snippets (single, flags, list) share the same pattern and could be compressed into one parameterized example.

Move the per-test-category boilerplate in Step 7 into a reference file (e.g. references/testing.md) and keep only the key rules and one canonical example in SKILL.md to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no concept explanations), but the ~200-line Step 7 testing section duplicates many near-identical code patterns and could be tightened by consolidating redundant test examples, so it is not fully lean.

2 / 3

Actionability

Most guidance is concrete and copy-paste ready, but a couple of code examples are not directly executable — 'def foobar(self, ...) -> RpcTentativeResult' is missing a trailing colon and uses 'except e:' instead of 'except Exception as e:', placing it at the level-2 anchor of incomplete concrete guidance.

2 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced with an operation-routing table (Step 1), decision rules (Step 2), two-phase breaking-change coordination (Step 5), and an explicit pre-flight validation checklist (Step 8) acting as a feedback checkpoint, matching the level-3 anchor.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that clearly signals four real one-level-deep references (references/rpc-models.md, resolvers.md, service-template.md, deprecation.md, all verified present) with 'Load ... for' phrasing, and content is appropriately split, matching the level-3 anchor.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 excellent: third-person voice, concrete actions, an explicit 'Use when' clause with many natural trigger phrases, and a distinct Sentry-specific niche. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating, updating, and deprecating hybrid cloud RPC services' and enumerates coverage areas ('service scaffolding, method signatures, RPC models, cell resolvers, testing, and safe deprecation workflows'), matching the level-3 anchor of several specific concrete actions.

3 / 3

Completeness

Clearly answers both what it does ('Guide for creating, updating, and deprecating...') and when to use it with an explicit 'Use when asked to...' clause and enumerated triggers, matching the level-3 anchor that requires explicit triggers.

3 / 3

Trigger Term Quality

Provides extensive natural quoted trigger phrases users would say ('add RPC method', 'create RPC service', 'new RPC model', 'deprecate RPC method', 'cross-silo service', 'cell RPC'), giving good coverage of common variations, matching the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Sentry hybrid cloud RPC services) with highly domain-specific triggers unlikely to overlap with other skills, matching the level-3 anchor of a clear niche with distinct triggers.

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.

Repository
getsentry/sentry
Reviewed

Table of Contents

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.