Individual skill

saas-security

Wiring your application to a third-party SaaS platform: verifying an inbound webhook against the vendor's own scheme rather than a generalized one, why a valid signature identifies the sender and not the user in the payload, replay windows, one credential per integration and per environment, least-privilege scopes, and treating a bulk export as a data boundary. Use when writing a webhook receiver, an OAuth integration, a SCIM endpoint, or any code that authenticates to or from a SaaS vendor.

skills/saas-security/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings): 23
Repository last updated: Aug 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-skills Repository topic
llm Repository topic
security Repository topic
skills Repository topic
writing Derived category
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 9,019 bytes
references/verifying-findings.mddoc · 4,746 bytes
rules/atlassian.jsonasset · 6,398 bytes
rules/bamboohr.jsonasset · 3,772 bytes
rules/calendly.jsonasset · 4,547 bytes
rules/google_chat.jsonasset · 3,146 bytes
rules/google_workspace.jsonasset · 7,226 bytes
rules/hubspot.jsonasset · 4,508 bytes
rules/larksuite.jsonasset · 4,904 bytes
rules/microsoft_teams.jsonasset · 4,907 bytes
rules/netsuite.jsonasset · 5,974 bytes
rules/notion.jsonasset · 4,180 bytes
rules/odoo.jsonasset · 4,703 bytes
rules/salesforce.jsonasset · 6,184 bytes
rules/slack.jsonasset · 6,132 bytes
rules/workday.jsonasset · 5,028 bytes
rules/zoom.jsonasset · 5,414 bytes
tests/corpus.jsonasset · 4,271 bytes

Read excerpt


# SaaS Integration Security

## Rules (for AI agents)

### ALWAYS
- Verify an inbound webhook against **that vendor's documented scheme**, and do not
  generalize from another one. Vendors differ in the header, in the secret, and — the
  part that breaks a generalized implementation — in the **canonical string** that gets
  signed. Some sign the raw body, some sign a version prefix plus a timestamp plus the
  body, some sign the HTTP method and path as well. Read the vendor's page for the
  vendor you are integrating; a signature routine copied from a different vendor
  produces a receiver that rejects every legitimate event, and the fix someone reaches
  for is to turn verification off.
- Verify against the **raw request body**, exactly as received, before any parsing or