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.

73

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is a well-structured, highly actionable guide with strong workflow sequencing and validation checkpoints, supported by real one-level-deep reference files. The main gaps are minor: a buggy inline code example, some checklist redundancy, and a long inline testing section that could be progressively disclosed.

Suggestions

Fix the error-propagation code example: use 'except Exception as e:' and add the missing colon after 'def foobar(self, *, organization_id: int) -> RpcTentativeResult' so the snippet is executable as written.

Deduplicate the Step 3 'Checklist for new services' and the Step 8 'Pre-flight Checklist' — the latter could reference the former rather than restating overlapping items (e.g. the 'no future annotations' and keyword-only checks).

Consider moving the detailed Step 7 testing subsections (7.1–7.6) into a references/testing.md file, keeping only a brief overview and the key decorator/import examples inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense, actionable, and assumes Claude's competence (it does not re-explain RPC or basic Python), but the Step 3 checklist and Step 8 pre-flight checklist overlap heavily, which could be trimmed. It is noticeably above the 'mostly efficient' anchor without being fully lean.

4 / 5

Actionability

Mostly copy-paste-ready code with concrete decorators, signatures, and test patterns, but the error-propagation example contains bugs ('except e:' instead of 'except Exception as e:' and a missing colon on the def line) that prevent it from being fully executable.

4 / 5

Workflow Clarity

A clearly sequenced 8-step workflow with a routing decision table in Step 1, explicit validation via Step 7 (six testing categories) and Step 8 (a 17-item pre-flight checklist), plus feedback loops for error recovery.

5 / 5

Progressive Disclosure

All four referenced files (rpc-models.md, resolvers.md, service-template.md, deprecation.md) exist, are one level deep, and are clearly signaled with 'Load references/X.md'. Structure is good, but the very long inline Step 7 testing section could itself be split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: third-person voice, concrete capability list, explicit 'Use when' trigger guidance with many natural synonyms, and a distinct niche that minimizes conflict risk. No improvements needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating, updating, and deprecating' plus 'service scaffolding, method signatures, RPC models, cell resolvers, testing, and safe deprecation workflows' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (creating/updating/deprecating hybrid cloud RPC services and what it covers) and 'when' (a clear 'Use when asked to...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Provides an extensive list of natural trigger phrases users would actually say ('add RPC method', 'create RPC service', 'cross-silo service', 'cell RPC', 'control silo service', etc.) including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Sentry hybrid cloud RPC services — with distinct, domain-specific triggers that make conflict with other skills unlikely.

5 / 5

Total

20

/

20

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.