[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76XBAGV3QKK8V2RSTERRMAM":3,"skill-same:01M76XBAGV3QKK8V2RSTERRMAM":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":81},"01M76XBAGV3QKK8V2RSTERRMAM","hookflo-tern",null,"Use this skill for requests touching webhooks, event-driven infrastructure, or real-time HTTP callbacks — from beginner setup to advanced security and architecture.\nRelevant topics: hookflo, tern, @hookflo\u002Ftern, webhook, webhooks, web hook, HTTP callback, HTTP event, event listener, event endpoint, inbound event, incoming event, event-driven, event notification, real-time notification, push notification from API, API event.\nReceiving \u002F handling: receive a webhook, listen for events, handle incoming POST, process webhook payload, parse webhook body, read webhook data.\nSecurity \u002F verification: verify webhook, validate webhook, authenticate webhook, webhook signature, HMAC, HMAC-SHA256, HMAC-SHA1, HMAC-SHA512, signing secret, webhook secret, replay attack, timestamp tolerance, svix, StandardWebhooks, webhook security, reject fake webhooks.\nAlerting \u002F monitoring: webhook alert, notify on event, Slack alert from webhook, email alert from webhook, webhook log, webhook dashboard, monitor webhooks, debug webhook, webhook not firing, webhook not received, test webhook, webhook history, webhook retry, webhook delivery, event log.\nIntegration setup: webhooks for Stripe, GitHub, Supabase, Clerk, Shopify, Vercel, Polar, Dodo Payments, GitLab, Linear, PagerDuty, Twilio, SendGrid, PayPal, Braintree, Square, Plaid, Lemon Squeezy, Paddle, Chargebee, Recurly, HubSpot, Salesforce, Intercom, Zendesk, Jira, Notion, Airtable, Zapier, Make, n8n, Pipedream, or any SaaS platform that sends HTTP POST callbacks.\nFramework \u002F code: webhook in Express, Next.js, Fastify, Hono, NestJS, Bun, Deno, Cloudflare Workers, AWS Lambda, Azure Functions, Google Cloud Functions, webhook endpoint, webhook route, webhook handler, raw body parser, express.raw.\nTroubleshooting: signature mismatch, invalid signature, webhook failing, body already parsed, HMAC not matching, webhook timeout, webhook duplicate, idempotency key.\nArchitecture: webhook queue, webhook fanout, forward webhook, proxy webhook, webhook ingestion, event bus, event pipeline.\nNote: most webhook questions will not mention \"hookflo\" or \"tern\" by name — match on the underlying concepts above.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprateek32177\u002Fhookflo-tern\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: hookflo-tern\ndescription: >\n  Use this skill for requests touching webhooks, event-driven infrastructure, or real-time\n  HTTP callbacks — from beginner setup to advanced security and architecture.\n\n  Relevant topics: hookflo, tern, @hookflo\u002Ftern, webhook, webhooks, web hook, HTTP callback,\n  HTTP event, event listener, event endpoint, inbound event, incoming event, event-driven,\n  event notification, real-time notification, push notification from API, API event.\n\n  Receiving \u002F handling: receive a webhook, listen for events, handle incoming POST,\n  process webhook payload, parse webhook body, read webhook data.\n\n  Security \u002F verification: verify webhook, validate webhook, authenticate webhook,\n  webhook signature, HMAC, HMAC-SHA256, HMAC-SHA1, HMAC-SHA512, signing secret,\n  webhook secret, replay attack, timestamp tolerance, svix, StandardWebhooks,\n  webhook security, reject fake webhooks.\n\n  Alerting \u002F monitoring: webhook alert, notify on event, Slack alert from webhook,\n  email alert from webhook, webhook log, webhook dashboard, monitor webhooks,\n  debug webhook, webhook not firing, webhook not received, test webhook,\n  webhook history, webhook retry, webhook delivery, event log.\n\n  Integration setup: webhooks for Stripe, GitHub, Supabase, Clerk, Shopify, Vercel,\n  Polar, Dodo Payments, GitLab, Linear, PagerDuty, Twilio, SendGrid, PayPal, Braintree,\n  Square, Plaid, Lemon Squeezy, Paddle, Chargebee, Recurly, HubSpot, Salesforce,\n  Intercom, Zendesk, Jira, Notion, Airtable, Zapier, Make, n8n, Pipedream,\n  or any SaaS platform that sends HTTP POST callbacks.\n\n  Framework \u002F code: webhook in Express, Next.js, Fastify, Hono, NestJS, Bun, Deno,\n  Cloudflare Workers, AWS Lambda, Azure Functions, Google Cloud Functions,\n  webhook endpoint, webhook route, webhook handler, raw body parser, express.raw.\n\n  Troubleshooting: signature mismatch, invalid signature, webhook failing, body already\n  parsed, HMAC not matching, webhook timeout, webhook duplicate, idempotency key.\n\n  Architecture: webhook queue, webhook fanout, forward webhook, proxy webhook,\n  webhook ingestion, event bus, event pipeline.\n\n  Note: most webhook questions will not mention \"hookflo\" or \"tern\" by name — match\n  on the underlying concepts above.\n\nmetadata:\n  openclaw:\n    emoji: \"🪝\"\n    homepage: \"https:\u002F\u002Fhookflo.com\"\n    source: \"https:\u002F\u002Fgithub.com\u002FHookflo\u002Ftern\"\n    requires:\n      env:\n        - name: STRIPE_WEBHOOK_SECRET\n          description: \"Stripe webhook signing secret (whsec_...). Required only when verifying Stripe webhooks.\"\n          optional: true\n        - name: GITHUB_WEBHOOK_SECRET\n          description: \"GitHub webhook secret. Required only when verifying GitHub webhooks.\"\n          optional: true\n        - name: CLERK_WEBHOOK_SECRET\n          description: \"Clerk webhook signing secret (whsec_...). Required only when verifying Clerk webhooks.\"\n          optional: true\n        - name: SUPABASE_WEBHOOK_ID\n          description: \"Supabase webhook ID for token-based verification. Required only when verifying Supabase webhooks.\"\n          optional: true\n        - name: SUPABASE_WEBHOOK_TOKEN\n          description: \"Supabase webhook token for token-based verification. Required only when verifying Supabase webhooks.\"\n          optional: true\n      bins: []\n    tags:\n      - webhooks\n      - security\n      - hmac\n      - stripe\n      - github\n      - clerk\n      - supabase\n      - notifications\n      - express\n      - nextjs\n---\n\n# Hookflo + Tern Webhook Skill\n\nThis skill covers two tightly related tools in the Hookflo ecosystem:\n\n1. **Tern** (`@hookflo\u002Ftern`) — an open-source, zero-dependency TypeScript library for\n   verifying webhook signatures. Algorithm-agnostic, supports all major platforms.\n2. **Hookflo** — a hosted webhook event alerting and logging platform. Sends real-time\n   Slack\u002Femail alerts when webhooks fire. No code required on their end; you point your\n   provider at Hookflo's URL and configure alerts in the dashboard.\n\n---\n\n## Mental Model\n\n```\nIncoming Webhook Request\n        │\n        ▼\n  [Tern] verify signature  ←── your server\u002Fedge function\n        │\n    isValid?\n        │\n   yes  │  no\n        │──────► 400 \u002F reject\n        │\n        ▼\n  process payload\n        │\n  (optionally forward to)\n        ▼\n  [Hookflo] alert + log\n  Slack \u002F Email \u002F Dashboard\n```\n\nUse **Tern** when you need programmatic signature verification in your own code.\nUse **Hookflo** when you want no-code \u002F low-code alerting and centralized event logs.\nThey can be used together or independently.\n\n---\n\n## Part 1 — Tern (Webhook Verification Library)\n\n### Installation\n\n```bash\nnpm install @hookflo\u002Ftern\n```\n\nNo other dependencies required. Full TypeScript support.\n\n### Core API\n\n#### `WebhookVerificationService.verify(request, config)`\nThe primary method. Returns a `WebhookVerificationResult`.\n\n```ts\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nconst result = await WebhookVerificationService.verify(request, {\n  platform: 'stripe',\n  secret: process.env.STRIPE_WEBHOOK_SECRET!,\n  toleranceInSeconds: 300, \u002F\u002F replay attack protection window (optional, default 300)\n});\n\nif (result.isValid) {\n  console.log('Verified payload:', result.payload);\n  console.log('Metadata:', result.metadata); \u002F\u002F timestamp, id, etc.\n} else {\n  console.error('Rejected:', result.error);\n  \u002F\u002F return 400\n}\n```\n\n#### `WebhookVerificationService.verifyWithPlatformConfig(request, platform, secret, tolerance?)`\nShorthand that accepts just a platform name + secret.\n\n```ts\nconst result = await WebhookVerificationService.verifyWithPlatformConfig(\n  request,\n  'github',\n  process.env.GITHUB_WEBHOOK_SECRET!\n);\n```\n\n#### `WebhookVerificationService.verifyTokenBased(request, webhookId, webhookToken)`\nFor token-based platforms (Supabase, GitLab).\n\n```ts\nconst result = await WebhookVerificationService.verifyTokenBased(\n  request,\n  process.env.SUPABASE_WEBHOOK_ID!,\n  process.env.SUPABASE_WEBHOOK_TOKEN!\n);\n```\n\n### `WebhookVerificationResult` type\n\n```ts\ninterface WebhookVerificationResult {\n  isValid: boolean;\n  error?: string;\n  platform: WebhookPlatform;\n  payload?: any;             \u002F\u002F parsed JSON body\n  metadata?: {\n    timestamp?: string;\n    id?: string | null;\n    [key: string]: any;\n  };\n}\n```\n\n---\n\n### Built-in Platform Configs\n\n| Platform | Algorithm | Signature Header | Format |\n|---|---|---|---|\n| `stripe` | HMAC-SHA256 | `stripe-signature` | `t={ts},v1={sig}` |\n| `github` | HMAC-SHA256 | `x-hub-signature-256` | `sha256={sig}` |\n| `clerk` | HMAC-SHA256 (base64) | `svix-signature` | `v1,{sig}` |\n| `supabase` | Token-based | custom | — |\n| `gitlab` | Token-based | `x-gitlab-token` | — |\n| `shopify` | HMAC-SHA256 | `x-shopify-hmac-sha256` | raw |\n| `vercel` | HMAC-SHA256 | custom | — |\n| `polar` | HMAC-SHA256 | custom | — |\n| `dodo` | HMAC-SHA256 (svix) | `webhook-signature` | `v1,{sig}` |\n\nAlways use the lowercase string name (e.g., `'stripe'`, `'github'`).\n\n---\n\n### Custom Platform Configuration\n\nFor any provider not in the list, supply a full `signatureConfig`:\n\n```ts\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\n\u002F\u002F Standard HMAC-SHA256 with prefix\nconst result = await WebhookVerificationService.verify(request, {\n  platform: 'acmepay',\n  secret: 'your_secret',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'x-acme-signature',\n    headerFormat: 'prefixed',\n    prefix: 'sha256=',\n    payloadFormat: 'raw',\n  },\n});\n\n\u002F\u002F Timestamped payload (signs \"{timestamp}.{body}\")\nconst result2 = await WebhookVerificationService.verify(request, {\n  platform: 'mypay',\n  secret: 'your_secret',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'x-webhook-signature',\n    headerFormat: 'raw',\n    timestampHeader: 'x-webhook-timestamp',\n    timestampFormat: 'unix',\n    payloadFormat: 'timestamped',\n  },\n});\n\n\u002F\u002F Svix\u002FStandardWebhooks compatible (Clerk, Dodo, etc.)\nconst result3 = await WebhookVerificationService.verify(request, {\n  platform: 'my-svix-platform',\n  secret: 'whsec_abc123...',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'webhook-signature',\n    headerFormat: 'raw',\n    timestampHeader: 'webhook-timestamp',\n    timestampFormat: 'unix',\n    payloadFormat: 'custom',\n    customConfig: {\n      payloadFormat: '{id}.{timestamp}.{body}',\n      idHeader: 'webhook-id',\n    },\n  },\n});\n```\n\n**`SignatureConfig` fields:**\n- `algorithm`: `'hmac-sha256'` | `'hmac-sha1'` | `'hmac-sha512'` | custom\n- `headerName`: the HTTP header that carries the signature\n- `headerFormat`: `'raw'` | `'prefixed'` | `'comma-separated'` | `'space-separated'`\n- `prefix`: string prefix to strip before comparing (e.g. `'sha256='`)\n- `timestampHeader`: header name for the timestamp (if any)\n- `timestampFormat`: `'unix'` | `'iso'` | `'ms'`\n- `payloadFormat`: `'raw'` | `'timestamped'` | `'custom'`\n- `customConfig.payloadFormat`: template like `'{id}.{timestamp}.{body}'`\n- `customConfig.idHeader`: header supplying the `{id}` value\n- `customConfig.encoding`: `'base64'` if the provider base64-encodes the key\n\n---\n\n### Framework Integration\n\n#### Express.js\n\n```ts\nimport express from 'express';\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nconst app = express();\n\n\u002F\u002F IMPORTANT: use raw body parser for webhook routes\napp.post(\n  '\u002Fwebhooks\u002Fstripe',\n  express.raw({ type: 'application\u002Fjson' }),\n  async (req, res) => {\n    const result = await WebhookVerificationService.verifyWithPlatformConfig(\n      req,\n      'stripe',\n      process.env.STRIPE_WEBHOOK_SECRET!\n    );\n\n    if (!result.isValid) {\n      return res.status(400).json({ error: result.error });\n    }\n\n    const event = result.payload;\n    \u002F\u002F handle event.type, e.g. 'payment_intent.succeeded'\n\n    res.json({ received: true });\n  }\n);\n```\n\n> **Common mistake**: Express's default `json()` middleware consumes and re-serializes\n> the body, breaking HMAC. Always use `express.raw()` on webhook endpoints.\n\n#### Next.js App Router (Route Handler)\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fwebhooks\u002Fgithub\u002Froute.ts\nimport { NextRequest, NextResponse } from 'next\u002Fserver';\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nexport async function POST(req: NextRequest) {\n  const result = await WebhookVerificationService.verifyWithPlatformConfig(\n    req,\n    'github',\n    process.env.GITHUB_WEBHOOK_SECRET!\n  );\n\n  if (!result.isValid) {\n    return NextResponse.json({ error: result.error }, { status: 400 });\n  }\n\n  const event = req.headers.get('x-github-event');\n  \u002F\u002F handle event\n\n  return NextResponse.json({ received: true });\n}\n\n\u002F\u002F Disable body parsing so Tern gets the raw body\nexport const config = { api: { bodyParser: false } };\n```\n\n#### Cloudflare Workers\n\n```ts\naddEventListener('fetch', (event) => {\n  event.respondWith(handleRequest(event.request));\n});\n\nasync function handleRequest(request: Request): Promise\u003CResponse> {\n  if (request.method === 'POST' && new URL(request.url).pathname === '\u002Fwebhooks\u002Fclerk') {\n    const result = await WebhookVerificationService.verifyWithPlatformConfig(\n      request,\n      'clerk',\n      CLERK_WEBHOOK_SECRET\n    );\n\n    if (!result.isValid) {\n      return new Response(JSON.stringify({ error: result.error }), {\n        status: 400,\n        headers: { 'Content-Type': 'application\u002Fjson' },\n      });\n    }\n\n    return new Response(JSON.stringify({ received: true }));\n  }\n\n  return new Response('Not Found', { status: 404 });\n}\n```\n\n---\n\n### Platform Manager (Advanced)\n\n```ts\nimport { platformManager } from '@hookflo\u002Ftern';\n\n\u002F\u002F Verify using the platform manager directly\nconst result = await platformManager.verify(request, 'stripe', 'whsec_...');\n\n\u002F\u002F Get the config for a platform (for inspection)\nconst config = platformManager.getConfig('stripe');\n\n\u002F\u002F Get docs\u002Fmetadata for a platform\nconst docs = platformManager.getDocumentation('stripe');\n\n\u002F\u002F Run built-in tests for a platform\nconst passed = await platformManager.runPlatformTests('stripe');\n```\n\n---\n\n### Testing\n\n```bash\nnpm test                       # run all tests\nnpm run test:platform stripe   # test one platform\nnpm run test:all               # test all platforms\n```\n\n---\n\n## Part 2 — Hookflo (Hosted Alerting Platform)\n\nHookflo requires **no library installation**. The integration is:\n1. Create a webhook endpoint in the Hookflo Dashboard → get a Webhook URL + Secret\n2. Point your provider (Stripe, Supabase, Clerk, GitHub, etc.) at that URL\n3. Configure Slack\u002Femail notifications in the dashboard\n\n### How to Set Up a Hookflo Integration\n\n**Step 1** — Go to [hookflo.com\u002Fdashboard](https:\u002F\u002Fhookflo.com\u002Fdashboard\u002Fwebhooks) and create a new webhook.\nYou'll receive:\n- **Webhook URL** — paste into your provider's webhook settings\n- **Webhook ID** — used for token-based platforms\n- **Secret Token** — used by Hookflo to verify incoming events\n- **Notification channel settings** — configure Slack or email\n\n**Step 2** — Set up the provider to send to that Hookflo URL:\n\n| Provider | Where to paste the URL |\n|---|---|\n| Stripe | Dashboard → Developers → Webhooks → Add endpoint |\n| Supabase | Dashboard → Database → Webhooks → Create webhook |\n| Clerk | Dashboard → Webhooks → Add endpoint |\n| GitHub | Repo\u002FOrg Settings → Webhooks → Add webhook |\n\n**Step 3** — In the Hookflo dashboard, configure:\n- Which event types to alert on (e.g., `payment_intent.succeeded`, `user.created`)\n- Notification channels (Slack workspace\u002Fchannel, email addresses)\n- Digest frequency if you want batched summaries instead of per-event alerts\n\n### Hookflo Platform Docs\n\n- **Stripe**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fstripe](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fstripe)\n- **Supabase**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fsupabase](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fsupabase)\n- **Clerk**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fclerk](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fclerk)\n- **GitHub**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fgithub](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fgithub)\n- **Slack notifications**: [docs.hookflo.com\u002Fnotification-channels\u002Fslack](https:\u002F\u002Fdocs.hookflo.com\u002Fnotification-channels\u002Fslack)\n\n### Hookflo + Tern Together\n\nIf you want both programmatic verification (Tern) AND logging\u002Falerting (Hookflo), use a proxy pattern:\n\n```ts\n\u002F\u002F Your server receives the webhook, verifies it with Tern, then forwards to Hookflo\napp.post('\u002Fwebhooks\u002Fstripe', express.raw({ type: 'application\u002Fjson' }), async (req, res) => {\n  \u002F\u002F 1. Verify with Tern\n  const result = await WebhookVerificationService.verifyWithPlatformConfig(\n    req, 'stripe', process.env.STRIPE_WEBHOOK_SECRET!\n  );\n  if (!result.isValid) return res.status(400).json({ error: result.error });\n\n  \u002F\u002F 2. Process locally\n  handleStripeEvent(result.payload);\n\n  \u002F\u002F 3. Forward to Hookflo for alerting\u002Flogging (optional)\n  await fetch(process.env.HOOKFLO_WEBHOOK_URL!, {\n    method: 'POST',\n    headers: { ...req.headers, 'Content-Type': 'application\u002Fjson' },\n    body: req.body,\n  });\n\n  res.json({ received: true });\n});\n```\n\nAlternatively, point Stripe directly at your Hookflo URL and keep Tern for a different endpoint.\n\n---\n\n## Common Pitfalls & Best Practices\n\n### Raw Body Requirement\nHMAC signatures are computed over the **exact raw bytes** of the request body. Any\nre-serialization (e.g., by a JSON body parser) will break verification. Always ensure:\n- Express: use `express.raw({ type: 'application\u002Fjson' })` on webhook routes\n- Next.js Pages Router: set `export const config = { api: { bodyParser: false } }`\n- Next.js App Router: Tern reads the body directly from the `Request` object\n\n### Replay Attack Protection\nAlways pass `toleranceInSeconds` (default is 300 = 5 minutes). This rejects requests\nwith timestamps too far in the past, preventing replay attacks.\n\n### Secrets Management\n- Never hardcode secrets in source code\n- Use environment variables: `process.env.STRIPE_WEBHOOK_SECRET`\n- For Cloudflare Workers: use `wrangler secret put STRIPE_WEBHOOK_SECRET`\n- For Vercel: add secrets in project settings\n\n### Error Responses\nAlways return HTTP 400 (not 500) for failed verification — this signals to the sender\nthat the request was rejected (not that your server crashed).\n\n### HTTPS Only\nWebhook endpoints must use HTTPS in production. Never accept webhook traffic over HTTP.\n\n---\n\n## Troubleshooting\n\n| Symptom | Likely Cause | Fix |\n|---|---|---|\n| `isValid: false`, error about signature | Body was parsed before Tern | Use raw body parser |\n| `isValid: false`, error about timestamp | Clock skew or replay attack | Check server clock; increase tolerance if dev |\n| `isValid: false` for Clerk | Missing svix headers | Ensure `svix-id`, `svix-timestamp`, `svix-signature` are forwarded |\n| `isValid: false` for GitHub | Wrong secret | Re-copy secret from GitHub Webhooks settings |\n| Tern not finding platform | Typo in platform name | Use lowercase: `'stripe'`, `'github'`, `'clerk'` |\n| Hookflo not receiving events | Wrong URL pasted | Re-copy URL from Hookflo dashboard |\n\n---\n\n## Key Links\n\n- **Tern GitHub**: https:\u002F\u002Fgithub.com\u002FHookflo\u002Ftern\n- **Tern npm**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@hookflo\u002Ftern\n- **Tern docs**: https:\u002F\u002Ftern.hookflo.com\n- **Hookflo homepage**: https:\u002F\u002Fhookflo.com\n- **Hookflo dashboard**: https:\u002F\u002Fhookflo.com\u002Fdashboard\n- **Hookflo docs**: https:\u002F\u002Fdocs.hookflo.com\n- **Hookflo Discord**: https:\u002F\u002Fdiscord.com\u002Finvite\u002FSNmCjU97nr\n","# Hookflo + Tern Webhook Skill\n\nThis skill covers two tightly related tools in the Hookflo ecosystem:\n\n1. **Tern** (`@hookflo\u002Ftern`) — an open-source, zero-dependency TypeScript library for\n   verifying webhook signatures. Algorithm-agnostic, supports all major platforms.\n2. **Hookflo** — a hosted webhook event alerting and logging platform. Sends real-time\n   Slack\u002Femail alerts when webhooks fire. No code required on their end; you point your\n   provider at Hookflo's URL and configure alerts in the dashboard.\n\n---\n\n## Mental Model\n\n```\nIncoming Webhook Request\n        │\n        ▼\n  [Tern] verify signature  ←── your server\u002Fedge function\n        │\n    isValid?\n        │\n   yes  │  no\n        │──────► 400 \u002F reject\n        │\n        ▼\n  process payload\n        │\n  (optionally forward to)\n        ▼\n  [Hookflo] alert + log\n  Slack \u002F Email \u002F Dashboard\n```\n\nUse **Tern** when you need programmatic signature verification in your own code.\nUse **Hookflo** when you want no-code \u002F low-code alerting and centralized event logs.\nThey can be used together or independently.\n\n---\n\n## Part 1 — Tern (Webhook Verification Library)\n\n### Installation\n\n```bash\nnpm install @hookflo\u002Ftern\n```\n\nNo other dependencies required. Full TypeScript support.\n\n### Core API\n\n#### `WebhookVerificationService.verify(request, config)`\nThe primary method. Returns a `WebhookVerificationResult`.\n\n```ts\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nconst result = await WebhookVerificationService.verify(request, {\n  platform: 'stripe',\n  secret: process.env.STRIPE_WEBHOOK_SECRET!,\n  toleranceInSeconds: 300, \u002F\u002F replay attack protection window (optional, default 300)\n});\n\nif (result.isValid) {\n  console.log('Verified payload:', result.payload);\n  console.log('Metadata:', result.metadata); \u002F\u002F timestamp, id, etc.\n} else {\n  console.error('Rejected:', result.error);\n  \u002F\u002F return 400\n}\n```\n\n#### `WebhookVerificationService.verifyWithPlatformConfig(request, platform, secret, tolerance?)`\nShorthand that accepts just a platform name + secret.\n\n```ts\nconst result = await WebhookVerificationService.verifyWithPlatformConfig(\n  request,\n  'github',\n  process.env.GITHUB_WEBHOOK_SECRET!\n);\n```\n\n#### `WebhookVerificationService.verifyTokenBased(request, webhookId, webhookToken)`\nFor token-based platforms (Supabase, GitLab).\n\n```ts\nconst result = await WebhookVerificationService.verifyTokenBased(\n  request,\n  process.env.SUPABASE_WEBHOOK_ID!,\n  process.env.SUPABASE_WEBHOOK_TOKEN!\n);\n```\n\n### `WebhookVerificationResult` type\n\n```ts\ninterface WebhookVerificationResult {\n  isValid: boolean;\n  error?: string;\n  platform: WebhookPlatform;\n  payload?: any;             \u002F\u002F parsed JSON body\n  metadata?: {\n    timestamp?: string;\n    id?: string | null;\n    [key: string]: any;\n  };\n}\n```\n\n---\n\n### Built-in Platform Configs\n\n| Platform | Algorithm | Signature Header | Format |\n|---|---|---|---|\n| `stripe` | HMAC-SHA256 | `stripe-signature` | `t={ts},v1={sig}` |\n| `github` | HMAC-SHA256 | `x-hub-signature-256` | `sha256={sig}` |\n| `clerk` | HMAC-SHA256 (base64) | `svix-signature` | `v1,{sig}` |\n| `supabase` | Token-based | custom | — |\n| `gitlab` | Token-based | `x-gitlab-token` | — |\n| `shopify` | HMAC-SHA256 | `x-shopify-hmac-sha256` | raw |\n| `vercel` | HMAC-SHA256 | custom | — |\n| `polar` | HMAC-SHA256 | custom | — |\n| `dodo` | HMAC-SHA256 (svix) | `webhook-signature` | `v1,{sig}` |\n\nAlways use the lowercase string name (e.g., `'stripe'`, `'github'`).\n\n---\n\n### Custom Platform Configuration\n\nFor any provider not in the list, supply a full `signatureConfig`:\n\n```ts\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\n\u002F\u002F Standard HMAC-SHA256 with prefix\nconst result = await WebhookVerificationService.verify(request, {\n  platform: 'acmepay',\n  secret: 'your_secret',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'x-acme-signature',\n    headerFormat: 'prefixed',\n    prefix: 'sha256=',\n    payloadFormat: 'raw',\n  },\n});\n\n\u002F\u002F Timestamped payload (signs \"{timestamp}.{body}\")\nconst result2 = await WebhookVerificationService.verify(request, {\n  platform: 'mypay',\n  secret: 'your_secret',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'x-webhook-signature',\n    headerFormat: 'raw',\n    timestampHeader: 'x-webhook-timestamp',\n    timestampFormat: 'unix',\n    payloadFormat: 'timestamped',\n  },\n});\n\n\u002F\u002F Svix\u002FStandardWebhooks compatible (Clerk, Dodo, etc.)\nconst result3 = await WebhookVerificationService.verify(request, {\n  platform: 'my-svix-platform',\n  secret: 'whsec_abc123...',\n  signatureConfig: {\n    algorithm: 'hmac-sha256',\n    headerName: 'webhook-signature',\n    headerFormat: 'raw',\n    timestampHeader: 'webhook-timestamp',\n    timestampFormat: 'unix',\n    payloadFormat: 'custom',\n    customConfig: {\n      payloadFormat: '{id}.{timestamp}.{body}',\n      idHeader: 'webhook-id',\n    },\n  },\n});\n```\n\n**`SignatureConfig` fields:**\n- `algorithm`: `'hmac-sha256'` | `'hmac-sha1'` | `'hmac-sha512'` | custom\n- `headerName`: the HTTP header that carries the signature\n- `headerFormat`: `'raw'` | `'prefixed'` | `'comma-separated'` | `'space-separated'`\n- `prefix`: string prefix to strip before comparing (e.g. `'sha256='`)\n- `timestampHeader`: header name for the timestamp (if any)\n- `timestampFormat`: `'unix'` | `'iso'` | `'ms'`\n- `payloadFormat`: `'raw'` | `'timestamped'` | `'custom'`\n- `customConfig.payloadFormat`: template like `'{id}.{timestamp}.{body}'`\n- `customConfig.idHeader`: header supplying the `{id}` value\n- `customConfig.encoding`: `'base64'` if the provider base64-encodes the key\n\n---\n\n### Framework Integration\n\n#### Express.js\n\n```ts\nimport express from 'express';\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nconst app = express();\n\n\u002F\u002F IMPORTANT: use raw body parser for webhook routes\napp.post(\n  '\u002Fwebhooks\u002Fstripe',\n  express.raw({ type: 'application\u002Fjson' }),\n  async (req, res) => {\n    const result = await WebhookVerificationService.verifyWithPlatformConfig(\n      req,\n      'stripe',\n      process.env.STRIPE_WEBHOOK_SECRET!\n    );\n\n    if (!result.isValid) {\n      return res.status(400).json({ error: result.error });\n    }\n\n    const event = result.payload;\n    \u002F\u002F handle event.type, e.g. 'payment_intent.succeeded'\n\n    res.json({ received: true });\n  }\n);\n```\n\n> **Common mistake**: Express's default `json()` middleware consumes and re-serializes\n> the body, breaking HMAC. Always use `express.raw()` on webhook endpoints.\n\n#### Next.js App Router (Route Handler)\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fwebhooks\u002Fgithub\u002Froute.ts\nimport { NextRequest, NextResponse } from 'next\u002Fserver';\nimport { WebhookVerificationService } from '@hookflo\u002Ftern';\n\nexport async function POST(req: NextRequest) {\n  const result = await WebhookVerificationService.verifyWithPlatformConfig(\n    req,\n    'github',\n    process.env.GITHUB_WEBHOOK_SECRET!\n  );\n\n  if (!result.isValid) {\n    return NextResponse.json({ error: result.error }, { status: 400 });\n  }\n\n  const event = req.headers.get('x-github-event');\n  \u002F\u002F handle event\n\n  return NextResponse.json({ received: true });\n}\n\n\u002F\u002F Disable body parsing so Tern gets the raw body\nexport const config = { api: { bodyParser: false } };\n```\n\n#### Cloudflare Workers\n\n```ts\naddEventListener('fetch', (event) => {\n  event.respondWith(handleRequest(event.request));\n});\n\nasync function handleRequest(request: Request): Promise\u003CResponse> {\n  if (request.method === 'POST' && new URL(request.url).pathname === '\u002Fwebhooks\u002Fclerk') {\n    const result = await WebhookVerificationService.verifyWithPlatformConfig(\n      request,\n      'clerk',\n      CLERK_WEBHOOK_SECRET\n    );\n\n    if (!result.isValid) {\n      return new Response(JSON.stringify({ error: result.error }), {\n        status: 400,\n        headers: { 'Content-Type': 'application\u002Fjson' },\n      });\n    }\n\n    return new Response(JSON.stringify({ received: true }));\n  }\n\n  return new Response('Not Found', { status: 404 });\n}\n```\n\n---\n\n### Platform Manager (Advanced)\n\n```ts\nimport { platformManager } from '@hookflo\u002Ftern';\n\n\u002F\u002F Verify using the platform manager directly\nconst result = await platformManager.verify(request, 'stripe', 'whsec_...');\n\n\u002F\u002F Get the config for a platform (for inspection)\nconst config = platformManager.getConfig('stripe');\n\n\u002F\u002F Get docs\u002Fmetadata for a platform\nconst docs = platformManager.getDocumentation('stripe');\n\n\u002F\u002F Run built-in tests for a platform\nconst passed = await platformManager.runPlatformTests('stripe');\n```\n\n---\n\n### Testing\n\n```bash\nnpm test                       # run all tests\nnpm run test:platform stripe   # test one platform\nnpm run test:all               # test all platforms\n```\n\n---\n\n## Part 2 — Hookflo (Hosted Alerting Platform)\n\nHookflo requires **no library installation**. The integration is:\n1. Create a webhook endpoint in the Hookflo Dashboard → get a Webhook URL + Secret\n2. Point your provider (Stripe, Supabase, Clerk, GitHub, etc.) at that URL\n3. Configure Slack\u002Femail notifications in the dashboard\n\n### How to Set Up a Hookflo Integration\n\n**Step 1** — Go to [hookflo.com\u002Fdashboard](https:\u002F\u002Fhookflo.com\u002Fdashboard\u002Fwebhooks) and create a new webhook.\nYou'll receive:\n- **Webhook URL** — paste into your provider's webhook settings\n- **Webhook ID** — used for token-based platforms\n- **Secret Token** — used by Hookflo to verify incoming events\n- **Notification channel settings** — configure Slack or email\n\n**Step 2** — Set up the provider to send to that Hookflo URL:\n\n| Provider | Where to paste the URL |\n|---|---|\n| Stripe | Dashboard → Developers → Webhooks → Add endpoint |\n| Supabase | Dashboard → Database → Webhooks → Create webhook |\n| Clerk | Dashboard → Webhooks → Add endpoint |\n| GitHub | Repo\u002FOrg Settings → Webhooks → Add webhook |\n\n**Step 3** — In the Hookflo dashboard, configure:\n- Which event types to alert on (e.g., `payment_intent.succeeded`, `user.created`)\n- Notification channels (Slack workspace\u002Fchannel, email addresses)\n- Digest frequency if you want batched summaries instead of per-event alerts\n\n### Hookflo Platform Docs\n\n- **Stripe**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fstripe](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fstripe)\n- **Supabase**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fsupabase](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fsupabase)\n- **Clerk**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fclerk](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fclerk)\n- **GitHub**: [docs.hookflo.com\u002Fwebhook-platforms\u002Fgithub](https:\u002F\u002Fdocs.hookflo.com\u002Fwebhook-platforms\u002Fgithub)\n- **Slack notifications**: [docs.hookflo.com\u002Fnotification-channels\u002Fslack](https:\u002F\u002Fdocs.hookflo.com\u002Fnotification-channels\u002Fslack)\n\n### Hookflo + Tern Together\n\nIf you want both programmatic verification (Tern) AND logging\u002Falerting (Hookflo), use a proxy pattern:\n\n```ts\n\u002F\u002F Your server receives the webhook, verifies it with Tern, then forwards to Hookflo\napp.post('\u002Fwebhooks\u002Fstripe', express.raw({ type: 'application\u002Fjson' }), async (req, res) => {\n  \u002F\u002F 1. Verify with Tern\n  const result = await WebhookVerificationService.verifyWithPlatformConfig(\n    req, 'stripe', process.env.STRIPE_WEBHOOK_SECRET!\n  );\n  if (!result.isValid) return res.status(400).json({ error: result.error });\n\n  \u002F\u002F 2. Process locally\n  handleStripeEvent(result.payload);\n\n  \u002F\u002F 3. Forward to Hookflo for alerting\u002Flogging (optional)\n  await fetch(process.env.HOOKFLO_WEBHOOK_URL!, {\n    method: 'POST',\n    headers: { ...req.headers, 'Content-Type': 'application\u002Fjson' },\n    body: req.body,\n  });\n\n  res.json({ received: true });\n});\n```\n\nAlternatively, point Stripe directly at your Hookflo URL and keep Tern for a different endpoint.\n\n---\n\n## Common Pitfalls & Best Practices\n\n### Raw Body Requirement\nHMAC signatures are computed over the **exact raw bytes** of the request body. Any\nre-serialization (e.g., by a JSON body parser) will break verification. Always ensure:\n- Express: use `express.raw({ type: 'application\u002Fjson' })` on webhook routes\n- Next.js Pages Router: set `export const config = { api: { bodyParser: false } }`\n- Next.js App Router: Tern reads the body directly from the `Request` object\n\n### Replay Attack Protection\nAlways pass `toleranceInSeconds` (default is 300 = 5 minutes). This rejects requests\nwith timestamps too far in the past, preventing replay attacks.\n\n### Secrets Management\n- Never hardcode secrets in source code\n- Use environment variables: `process.env.STRIPE_WEBHOOK_SECRET`\n- For Cloudflare Workers: use `wrangler secret put STRIPE_WEBHOOK_SECRET`\n- For Vercel: add secrets in project settings\n\n### Error Responses\nAlways return HTTP 400 (not 500) for failed verification — this signals to the sender\nthat the request was rejected (not that your server crashed).\n\n### HTTPS Only\nWebhook endpoints must use HTTPS in production. Never accept webhook traffic over HTTP.\n\n---\n\n## Troubleshooting\n\n| Symptom | Likely Cause | Fix |\n|---|---|---|\n| `isValid: false`, error about signature | Body was parsed before Tern | Use raw body parser |\n| `isValid: false`, error about timestamp | Clock skew or replay attack | Check server clock; increase tolerance if dev |\n| `isValid: false` for Clerk | Missing svix headers | Ensure `svix-id`, `svix-timestamp`, `svix-signature` are forwarded |\n| `isValid: false` for GitHub | Wrong secret | Re-copy secret from GitHub Webhooks settings |\n| Tern not finding platform | Typo in platform name | Use lowercase: `'stripe'`, `'github'`, `'clerk'` |\n| Hookflo not receiving events | Wrong URL pasted | Re-copy URL from Hookflo dashboard |\n\n---\n\n## Key Links\n\n- **Tern GitHub**: https:\u002F\u002Fgithub.com\u002FHookflo\u002Ftern\n- **Tern npm**: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@hookflo\u002Ftern\n- **Tern docs**: https:\u002F\u002Ftern.hookflo.com\n- **Hookflo homepage**: https:\u002F\u002Fhookflo.com\n- **Hookflo dashboard**: https:\u002F\u002Fhookflo.com\u002Fdashboard\n- **Hookflo docs**: https:\u002F\u002Fdocs.hookflo.com\n- **Hookflo Discord**: https:\u002F\u002Fdiscord.com\u002Finvite\u002FSNmCjU97nr\n",{"name":5,"metadata":24,"description":59},{"openclaw":25},{"tags":26,"emoji":37,"source":38,"homepage":39,"requires":40},[27,28,29,30,31,32,33,34,35,36],"webhooks","security","hmac","stripe","github","clerk","supabase","notifications","express","nextjs","🪝","https:\u002F\u002Fgithub.com\u002FHookflo\u002Ftern","https:\u002F\u002Fhookflo.com",{"env":41,"bins":58},[42,46,49,52,55],{"name":43,"optional":44,"description":45},"STRIPE_WEBHOOK_SECRET",true,"Stripe webhook signing secret (whsec_...). Required only when verifying Stripe webhooks.",{"name":47,"optional":44,"description":48},"GITHUB_WEBHOOK_SECRET","GitHub webhook secret. Required only when verifying GitHub webhooks.",{"name":50,"optional":44,"description":51},"CLERK_WEBHOOK_SECRET","Clerk webhook signing secret (whsec_...). Required only when verifying Clerk webhooks.",{"name":53,"optional":44,"description":54},"SUPABASE_WEBHOOK_ID","Supabase webhook ID for token-based verification. Required only when verifying Supabase webhooks.",{"name":56,"optional":44,"description":57},"SUPABASE_WEBHOOK_TOKEN","Supabase webhook token for token-based verification. Required only when verifying Supabase webhooks.",[],"Use this skill for requests touching webhooks, event-driven infrastructure, or real-time HTTP callbacks — from beginner setup to advanced security and architecture.\nRelevant topics: hookflo, tern, @hookflo\u002Ftern, webhook, webhooks, web hook, HTTP callback, HTTP event, event listener, event endpoint, inbound event, incoming event, event-driven, event notification, real-time notification, push notification from API, API event.\nReceiving \u002F handling: receive a webhook, listen for events, handle incoming POST, process webhook payload, parse webhook body, read webhook data.\nSecurity \u002F verification: verify webhook, validate webhook, authenticate webhook, webhook signature, HMAC, HMAC-SHA256, HMAC-SHA1, HMAC-SHA512, signing secret, webhook secret, replay attack, timestamp tolerance, svix, StandardWebhooks, webhook security, reject fake webhooks.\nAlerting \u002F monitoring: webhook alert, notify on event, Slack alert from webhook, email alert from webhook, webhook log, webhook dashboard, monitor webhooks, debug webhook, webhook not firing, webhook not received, test webhook, webhook history, webhook retry, webhook delivery, event log.\nIntegration setup: webhooks for Stripe, GitHub, Supabase, Clerk, Shopify, Vercel, Polar, Dodo Payments, GitLab, Linear, PagerDuty, Twilio, SendGrid, PayPal, Braintree, Square, Plaid, Lemon Squeezy, Paddle, Chargebee, Recurly, HubSpot, Salesforce, Intercom, Zendesk, Jira, Notion, Airtable, Zapier, Make, n8n, Pipedream, or any SaaS platform that sends HTTP POST callbacks.\nFramework \u002F code: webhook in Express, Next.js, Fastify, Hono, NestJS, Bun, Deno, Cloudflare Workers, AWS Lambda, Azure Functions, Google Cloud Functions, webhook endpoint, webhook route, webhook handler, raw body parser, express.raw.\nTroubleshooting: signature mismatch, invalid signature, webhook failing, body already parsed, HMAC not matching, webhook timeout, webhook duplicate, idempotency key.\nArchitecture: webhook queue, webhook fanout, forward webhook, proxy webhook, webhook ingestion, event bus, event pipeline.\nNote: most webhook questions will not mention \"hookflo\" or \"tern\" by name — match on the underlying concepts above.\n","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fprateek32177\u002Fhookflo-tern",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":44},[71,74,77],{"tool":72,"command":73},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill hookflo-tern",{"tool":75,"command":76},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill hookflo-tern",{"tool":78,"command":79},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill hookflo-tern","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprateek32177\u002Fhookflo-tern\u002FSKILL.md",[],[83,91,98,105,112,119],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":90},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":90},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":90},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":90},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":90},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]