agentleFS
Sign inStart free
khadinakbarlabskhadinakbarlabs/shopify-app-builder/skills/webhooks/SKILL.md

webhooks

Skill2 starsChanged 38 days agoMITView on GitHub

Implement and test authenticated Shopify webhooks, durable processing, retries and privacy lifecycle handlers.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use data-pipelines, incident-response and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 3 projects that use this

  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only for missing information that changes this task.

    line 13
  2. Distinctive:

    Check current topic, API version and config.

    line 17
  3. Distinctive:

    Test invalid signature, altered body, duplicates, delayed/out-of-order delivery, queue failure and cleanup.

    line 24
  4. Distinctive:

    Do not acknowledge work that can be lost immediately after response or return success for a failed cleanup.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Handle Shopify events reliably

Start here

A webhook is Shopify notifying your app about an event.

First useful outcome: Receive a valid event and reject an invalid signature in tests. Ask only for missing information that changes this task. Inspect the existing project and use synthetic data before touching a merchant store. Explain the next action and its expected result in plain language; offer a recommended default with its tradeoff.

Guided workflow

  1. Check current topic, API version and config; use the framework's supported webhook authentication over custom verification where available.
  2. For custom verification, authenticate the raw body with constant-time HMAC comparison before trusting parsed content; never log secret/payload data.
  3. Durably enqueue accepted work before acknowledgement, isolate shops, deduplicate event IDs and bound retries.
  4. Implement uninstall and applicable compliance topics with real export/deletion behavior, retention policy and tests.

Check it worked

Test invalid signature, altered body, duplicates, delayed/out-of-order delivery, queue failure and cleanup; a CLI sample alone may not verify real subscription delivery. Report what was changed, what was tested, and what still needs account access or live verification. Do not claim production readiness or approval from generated code alone.

If you get stuck

Do not acknowledge work that can be lost immediately after response or return success for a failed cleanup. Give one safe next step and a redacted error example, not a list of speculative fixes.

Safety and optional depth

Use only the user's selected project/accounts. Never read credential caches or request secrets in chat; the operator configures the application's approved secret store. Ask before live deployment, store mutations, billing, publication or paid runs unless that exact action is already authorized. No MCP service is required by this plugin.

For concrete examples in an existing project, read only the relevant section of technical-guide.md. These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with official documentation before using them.

Example request: "Use webhooks to help me with this task. Explain each change and verify it before moving on."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free