Agent skill · marketing growth · jeremylongshore
lindy-rate-limits
Manage Lindy AI credits, rate limits, and usage optimization.
Why this skill is useful
Provides specific strategies and code snippets for optimizing Lindy AI credit usage and managing rate limits that the AI wouldn't reliably generate on its own.
What it needs
Requires lindy account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Rate Limits and Credits Overview Build application-side controls for Lindy webhook-trigger traffic and workspace usage. Lindy plan terms, prices, credit rules, and service limits can vary or change; obtain them from the current workspace and contract instead of copying fixed commercial numbers into code. Use Read to inspect the caller and Write or Edit to implement its policy. This skill does not assume an undocumented Lindy REST API or SDK. Prerequisites The exact webhook URL generated by the target Lindy trigger. A nonempty secret generated for that trigger and stored in a secret manager. Current workspace or contract evidence for credits, quotas, and entitlements. A shared atomic store for admission control and idempotency when more than one process or instance can send triggers. A durable queue with dead-letter handling for work that may need retries. An approved bounded payload schema and a synthetic, non-sensitive test case. Instructions Step 1: Establish current limits and a local safety policy Record the evidence source and review date for every Lindy-provided credit or service constraint. Then choose application-owned controls independently: maximum admitted events per tenant and workload; maximum queue depth and age; maximum serialized payload size; retry count and total retry deadline; concurrency per worker pool; and warning, shedding, and stop thresholds. These are local risk controls, not claims about Lindy's service limits. Review them from observed traffic, task outcomes, and the organization's budget. Step 2: Fail closed before attaching the trigger secret Parse the configured URL; require protocol https:, hostname exactly public.lindy.ai, no username or password, and the expected webhook path. Reject an empty trigger secret. Never send the trigger secret to a callback receiver or reuse a callback secret for the outbound trigger. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-rate-limits