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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

92%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 an exemplary lean, actionable, well-sequenced workflow with strong validation checkpoints. Its one real defect is progressive disclosure: the two referenced files do not exist, so the signaled navigation leads nowhere.

Suggestions

Create the referenced files references/database-indexes.md and references/proto-conventions.md (or add the references/ bundle) so the in-body links resolve.

If those references are not yet available, inline the minimum needed index/convention details or remove the broken links until the bundle exists.

Consider adding a brief one-line note near each link describing what the reference contains, so the reader can judge whether to follow it.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — concrete file paths and commands with no padding or explanation of concepts Claude already knows; even the detailed leader-idempotency passage conveys non-obvious domain rules that earn their tokens.	5 / 5
Actionability	Fully executable guidance: exact commands (bin/generate_personhog_proto.sh, pnpm run generate:personhog-proto, cargo build -p personhog-proto), specific file paths, and clear 'follow the pattern of existing methods' instructions covering the common cases.	5 / 5
Workflow Clarity	Clear Step 0–4 sequence with an upfront eligibility gate ('stop' if the table is not listed), invariant checks (known_methods_is_sorted, index-scan requirement), compiler-driven feedback, and a final cargo build/test verification block plus a checklist.	5 / 5
Progressive Disclosure	The body is well-sectioned and signals one-level-deep references to references/database-indexes.md and references/proto-conventions.md, but no references/ directory (or any bundle) exists, so both links are dangling and navigation is broken.	3 / 5
	Total	18 / 20 Passed

Description

92%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 specific, complete, and tightly scoped to a distinct internal niche with concrete 'Use when' triggers. The only minor gap is keyword variety, since it leans on the proprietary 'personhog' name rather than broader synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions covering the full pipeline — eligibility checks, proto definition, code generation for Python/Node.js, Rust storage trait/postgres queries/service handler/router wiring, and index validation — a comprehensive, non-generic action set.	5 / 5
Completeness	Explicitly states both what the skill does (the enumerated actions) and when to use it via a 'Use when...' clause with three concrete triggers, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases ('adding a new gRPC endpoint', 'migrating a Django ORM query', 'extending the personhog service API') are present and concrete, but coverage relies on the domain-specific 'personhog' name with no synonyms or file extensions, leaving a few natural variants missing.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, named internal service niche (personhog-replica/router RPCs) with distinct, service-specific triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	19 / 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 missing	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: PostHog/posthog
Path: .agents/skills/adding-personhog-rpc/SKILL.md
Commit: 130f3a1

Reviewed: 9 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.