lindy-prod-checklist
A technical audit checklist for securing and preparing Lindy AI agents for production usage.
Install
mkdir -p .claude/skills/lindy-prod-checklist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6336" && unzip -o skill.zip -d .claude/skills/lindy-prod-checklist && rm skill.zipInstalls to .claude/skills/lindy-prod-checklist
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Production readiness checklist for Lindy AI agent deployments.Key capabilities
- →Audit agent security and prompt quality
- →Verify webhook authentication and secret management
- →Validate operational readiness for go-live
- →Configure monitoring and credit usage alerts
How it works
The checklist provides a structured verification process for security, configuration, and monitoring before an agent is deployed to a production environment.
Inputs & outputs
When to use lindy-prod-checklist
- →Audit production agent security
- →Verify webhook authentication
- →Validate operational go-live readiness
- →Perform production configuration reviews
About this skill
Lindy Production Checklist
Overview
Comprehensive go-live checklist for Lindy AI agents entering production. Covers agent configuration, security, monitoring, error handling, and operational readiness.
Prerequisites
- Agents tested in development/staging environment
- Production Lindy workspace configured
- Team members assigned appropriate roles
- Credit budget approved for production usage
Production Checklist
Authentication & Security
- Production API keys generated (separate from dev/staging)
- API keys stored in secret manager (not environment files)
- Webhook secrets generated for all webhook triggers
- Webhook receivers verify Bearer token on every request
-
.envfiles excluded from version control - Key rotation schedule documented (90-day max)
- Enterprise: SSO enabled, SCIM configured
Agent Configuration
- Agent prompt reviewed for production quality
- Clear identity and role definition
- Numbered step-by-step instructions
- Explicit constraints (no unauthorized promises, data limits)
- Error handling instructions in prompt
- Few-shot examples for consistent output format
- Model selection appropriate for each step:
- Gemini Flash for simple routing/classification
- Claude Sonnet/GPT-4o-mini for standard tasks
- GPT-4/Claude Opus only where complex reasoning required
- Exit conditions defined with primary + fallback criteria
- Trigger filters configured to prevent over-firing
- Knowledge base sources current and synced
Integration Health
- All integration OAuth tokens current (not expired)
- Gmail: correct account authorized, label filters set
- Slack: bot invited to required channels
- Webhooks: endpoint URLs use production domains (not ngrok/dev)
- HTTP Request actions: target URLs are production endpoints
- Phone numbers: provisioned and tested ($10/month each)
Error Handling
- Agents have fallback behavior for common failures:
- Integration auth expired -> notify admin
- KB returns no results -> graceful fallback response
- Condition matching fails -> default "other" branch
- Agent step loops -> reasonable exit conditions
- Webhook receivers return 200 quickly (process async)
- HTTP Request action targets have health checks
- Credit usage alerts configured (50%, 80%, 95% thresholds)
Monitoring & Observability
- Regular review of agent Tasks tab scheduled
- Failed task alerts configured (email or Slack)
- Credit consumption tracked per agent
- Task completion rate monitored (failures should be <5%)
- Response time baseline established for each agent
Operational Readiness
- Runbook documented for common agent failures
- Escalation path defined (L1 -> L2 -> Lindy support)
- On-call schedule if agents are customer-facing
- Agent sharing configured (Edit/User/Template access)
- Team credit allocation set for team members ($19.99/seat on Pro)
Compliance & Documentation
- Data handling practices documented per agent
- Agent prompts include PII redaction instructions
- Knowledge base content reviewed for accuracy
- HIPAA: BAA in place if handling healthcare data
- GDPR: data retention policies defined
- Agent purpose and scope documented for team reference
Pre-Launch Validation Script
#!/bin/bash
echo "=== Lindy Production Validation ==="
# 1. API connectivity
echo "[1/4] Testing API connectivity..."
API_STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $LINDY_API_KEY" \
"https://public.lindy.ai/api/v1/webhooks/health" 2>/dev/null || echo "000")
[ "$API_STATUS" = "000" ] && echo " WARN: Could not reach Lindy API" || echo " OK: API reachable"
# 2. Webhook endpoint health
echo "[2/4] Testing webhook receiver..."
ENDPOINT_STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
"https://your-app.com/health" 2>/dev/null || echo "000")
[ "$ENDPOINT_STATUS" = "200" ] && echo " OK: Webhook receiver healthy" || echo " FAIL: Receiver returned $ENDPOINT_STATUS"
# 3. Environment variables
echo "[3/4] Checking environment..."
[ -n "$LINDY_API_KEY" ] && echo " OK: LINDY_API_KEY set" || echo " FAIL: LINDY_API_KEY missing"
[ -n "$LINDY_WEBHOOK_SECRET" ] && echo " OK: LINDY_WEBHOOK_SECRET set" || echo " FAIL: LINDY_WEBHOOK_SECRET missing"
# 4. Credit balance check
echo "[4/4] Credit status: Check at settings/billing"
echo "=== Validation Complete ==="
Go/No-Go Criteria
| Category | Go | No-Go |
|---|---|---|
| Security | All keys in secret manager | Any hardcoded credentials |
| Auth | All integrations authorized | Any expired OAuth tokens |
| Prompt | Reviewed with constraints | Generic/placeholder prompt |
| Monitoring | Alerts configured | No failure notification |
| Credits | Budget approved | No credit plan |
| Testing | Agent tested end-to-end | Untested workflow paths |
Error Handling
| Check Failure | Severity | Action |
|---|---|---|
| API key invalid | Critical | Block launch, regenerate key |
| Integration expired | High | Re-authorize before launch |
| No trigger filters | Medium | Add filters to prevent credit waste |
| No monitoring | Medium | Set up alerts before launch |
| Missing documentation | Low | Document within first week |
Resources
Next Steps
Proceed to lindy-upgrade-migration for version management.
When not to use it
- →Do not launch agents without defined fallback behaviors
- →Do not use development webhook URLs in production
Prerequisites
Limitations
- →Webhook receivers must return 200 quickly to maintain performance
How it compares
This provides a formal audit framework for production readiness instead of relying on informal testing.
Compared to similar skills
lindy-prod-checklist side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| lindy-prod-checklist (this skill) | 1 | 27d | Caution | Intermediate |
| django-verification | 5 | 4mo | Review | Intermediate |
| deployment-validation-config-validate | 1 | 4mo | Review | Advanced |
| documenso-prod-checklist | 1 | 27d | Caution | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
django-verification
affaan-m
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
deployment-validation-config-validate
sickn33
You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat
documenso-prod-checklist
jeremylongshore
Execute Documenso production deployment checklist and rollback procedures. Use when deploying Documenso integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "documenso production", "deploy documenso", "documenso go-live", "documenso launch checklist".
gh-actions-validator
jeremylongshore
Validate use when validating GitHub Actions workflows for Google Cloud and Vertex AI deployments. Trigger with phrases like "validate github actions", "setup workload identity federation", "github actions security", "deploy agent with ci/cd", or "automate vertex ai deployment". Enforces Workload Identity Federation (WIF), validates OIDC permissions, ensures least privilege IAM, and implements security best practices.
ideogram-multi-env-setup
jeremylongshore
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram config by env".
perplexity-prod-checklist
jeremylongshore
Execute Perplexity production deployment checklist and rollback procedures. Use when deploying Perplexity integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "perplexity production", "deploy perplexity", "perplexity go-live", "perplexity launch checklist".