Agent skill · operations · jeremylongshore
lindy-prod-checklist
Production readiness checklist for Lindy AI agent deployments.
Why this skill is useful
Provides a comprehensive production readiness checklist that includes specific security and operational practices not commonly found in generic documentation.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Production Checklist Overview Create an evidence-backed go/no-go decision for a Lindy agent. Treat the Lindy dashboard and the organization's current contract, workspace configuration, and runbooks as the authorities. Do not infer product entitlements, prices, quotas, security features, support terms, or compliance commitments from this skill. Use Read to inspect configuration and evidence, Write or Edit to maintain the readiness record, and Bash(curl:) only for an approved synthetic webhook probe. Never place a secret in the record or command output. Prerequisites Access to the target Lindy workspace and its Tasks view. An exported webhook-trigger URL and its nonempty Lindy-generated trigger secret. A separate, nonempty callback secret when a Lindy HTTP Request action calls your application. Never reuse the trigger secret as the callback secret. A synthetic test case with no production personal or confidential data and a unique correlation ID. Access to current contract/workspace evidence for any claim about pricing, credits, thresholds, secret rotation, SSO, SCIM, support, or a BAA. A durable queue when callback work cannot be completed safely within the receiver's synchronous response window. Instructions 1. Open an evidence record Record the workspace, agent, reviewer, date, release identifier, and links to artifacts. Give every check one of three verdicts: PASS, FAIL, or NOT VERIFIED. A missing entitlement or policy document is NOT VERIFIED, not an assumed pass. 2. Verify the two authentication boundaries For an application calling a Lindy webhook trigger: Confirm the URL uses HTTPS and its hostname is exactly public.lindy.ai. Confirm the authorization value is the secret generated for that trigger. Keep the URL and trigger secret in an approved secret manager; redact both from screenshots, logs, tickets, and readiness reports. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-prod-checklist