CtrlK
BlogDocsLog inGet started
Tessl Logo

extending-personhog-test-harness

When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new failure mode to test (crashes, drains, zombies, lag, failover); or when a new correctness property needs asserting during runs. Trigger terms: personhog gate, chaos scenario, test harness, leader path regression, handoff bug, eviction, writer lag, acked write.

76

Quality

93%

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%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.

Excellent content: concise, concrete, and workflow-driven with explicit validation checkpoints and copy-paste commands. It assumes Claude's intelligence while providing every project-specific detail needed to act.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence, names specific files/enums/signals without padding, and avoids explaining basic concepts Claude already knows.

5 / 5

Actionability

Fully actionable guidance: concrete file paths (src/cli.rs, src/scenarios/gate.rs), specific flag/enum names (GateArgs, ChaosEvent, chaos_timeline()), explicit signals (SIGKILL/SIGTERM/SIGSTOP), and a copy-paste cargo build/run command.

5 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint ("three consecutive green runs is the bar") and feedback guidance (make deterministic rather than accepting flakes), plus explicit red-before/green-after verification for fixes.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a single one-level reference to the harness README; no nested references and no bundle files, appropriate for a focused single-purpose skill.

5 / 5

Total

20

/

20

Passed

Description

87%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.

A strong, well-targeted description that explicitly covers both what the skill does and when to invoke it, with a dedicated trigger-terms list. Minor room to broaden synonym coverage and enumerate capabilities more fully.

DimensionReasoningScore

Specificity

Lists several concrete actions ("add scenarios, chaos events, and invariants") tied to a named domain, with minor gaps in coverage; not a maximally comprehensive enumeration of all capabilities.

4 / 5

Completeness

Clearly answers both what (adding scenarios, chaos events, invariants) and when ("Use after fixing a bug or regression", "when adding a new failure mode", "when a new correctness property needs asserting") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit "Trigger terms" list provides good natural keywords ("test harness", "leader path regression", "handoff bug", "eviction", "writer lag", "acked write") but a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, product-specific niche (personhog leader path, rust/personhog-test-harness) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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
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.