CtrlK
BlogDocsLog inGet started
Tessl Logo

adding-personhog-rpc

Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC endpoint to personhog, migrating a Django ORM query to personhog, or extending the personhog service API.

80

Quality

100%

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

100%

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 tight, actionable end-to-end workflow with concrete file paths and commands, an eligibility gate, and a verification step plus checklist. Detail is appropriately offloaded to two real, clearly linked reference files one level deep.

DimensionReasoningScore

Conciseness

Lean and efficient — exact file paths and commands with no explaining of concepts Claude already knows; even the note that 'the compiler guides you' is actionable rather than filler.

3 / 3

Actionability

Copy-paste-ready commands (bin/generate_personhog_proto.sh, pnpm run generate:personhog-proto, cargo build -p personhog-replica) and exact file paths to edit at every layer.

3 / 3

Workflow Clarity

Clearly sequenced Step 0 through Step 4 with an upfront eligibility gate ('If the table is not listed above, stop'), an explicit verify step (cargo build/test), and a final checklist covering batch/database operations.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references to real files (database-indexes.md, proto-conventions.md), each linked inline where relevant.

3 / 3

Total

12

/

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.

The description is concise, specific, and uses third-person voice. It clearly states capabilities and provides explicit 'Use when...' triggers tied to natural user phrasing. It is distinctive within its domain with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does (full enumerated scope) and when to use it via a 'Use when...' clause with three concrete triggers.

3 / 3

Trigger Term Quality

Natural trigger phrases a user would say are present: 'adding a new gRPC endpoint to personhog', 'migrating a Django ORM query to personhog', 'extending the personhog service API'.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to the personhog service and its specific migration paths, making it unlikely to trigger for unrelated skills.

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
PostHog/posthog
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.