Skip to content

ericrisco/rsc-harness / skills/webhooks

webhooks

Verified

Use when building the receiving end of a webhook — a provider-agnostic endpoint that proves pushed events are authentic and never processes one twice: raw-body HMAC, ~5-min replay window, idempotency on the event id, fast-ack-then-queue. NOT the Stripe-Signature scheme (that is stripe), NOT outbound clients you call (that is api-connector-builder).

FileKindSize
SKILL.mdskill md12.0 KB
evals/README.mdmarkdown1.0 KB
evals/cases.yamlconfig4.1 KB
references/framework-raw-body.mdmarkdown3.5 KB
references/signature-schemes.mdmarkdown3.5 KB
scripts/verify.shexecutablescript6.3 KB

evals/README.md

View on GitHub
# Evals — webhooks

These cases are descriptive routing/capability checks, not an automated test
suite. To run them, feed each `should_trigger` prompt to the skill router and
confirm `webhooks` is selected (the `why` explains the intent, including the
non-obvious raw-body and fast-ack symptoms); feed each `should_not_trigger`
prompt and confirm the router picks the named sibling in `route_to` instead
(these guard the boundaries against `stripe`, `email-connector`,
`api-connector-builder`, `automation-flows` and `redis`). The `capability` case
is graded by generation: have the skill produce the Express handler and check
the output against the `must_include` rubric — every line should be present
(raw-body HMAC, constant-time compare, 5-min window, dedupe-on-event-id with a
TTL that outlives retries, 2xx-after-enqueue, secret-from-env, 400/401 on a bad
signature). `scripts/verify.sh` is a complementary static linter for those same
invariants against real handler files; it is advisory, not part of this eval.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall