Agent skill · software engineering · jeremylongshore
lindy-local-dev-loop
Set up local development workflow for testing Lindy AI agent integrations.
Why this skill is useful
Adds specific commands and code snippets for setting up webhook receivers and testing Lindy AI integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires ngrok, node installed locally. Requires lindy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Local Dev Loop Overview Lindy agents run on Lindy's managed infrastructure — you do not run agents locally. Local development focuses on building and testing the webhook receivers, callback handlers, and application code that Lindy agents interact with. Use ngrok or similar tunnels to expose local endpoints for Lindy webhook triggers. Prerequisites Node.js 18+ or Python 3.10+ ngrok or Cloudflare Tunnel for HTTPS tunneling Lindy account with at least one agent configured Completed lindy-install-auth setup Instructions Step 1: Create Webhook Receiver Step 2: Expose Local Server via Tunnel Step 3: Configure Lindy Agent to Call Your Endpoint In the Lindy dashboard, add an HTTP Request action to your agent: Method: POST URL: https://abc123.ngrok.io/lindy/callback Headers: Content-Type: application/json Authorization: Bearer <development callback secret> Body (AI Prompt mode): The tunnel is the destination of the agent's HTTP Request action. A webhook trigger is the opposite direction: it uses the Lindy-hosted trigger URL to start the agent and must not be replaced with the tunnel URL. Step 4: Create Test Harness Step 5: Watch Mode Development Step 6: Environment Configuration Development Workflow Output Produce a local-test receipt containing the callback route, redacted tunnel origin, test payload fixture, authenticated and unauthenticated HTTP outcomes, Lindy task ID, callback status, and log timestamp. The receipt must not contain the tunnel's private path, either bearer credential, or any customer payload. Examples Start the receiver and tunnel, send a synthetic event with the development credential, and confirm one callback is accepted and correlated to the recorded task ID. Send the same fixture without authorization and confirm a 401 response. If the tunnel changes, update only the development configuration and rerun both checks before continuing iteration. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-local-dev-loop--8d7e99