agentsclimarketplace

Lindy prod checklist

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/saas-packs/lindy-pack/skills/lindy-prod-checklist

'Production readiness checklist for Lindy AI agent deployments.From its SKILL.md

Install
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill lindy-prod-checklist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.1 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

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
  • .env files 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

CategoryGoNo-Go
SecurityAll keys in secret managerAny hardcoded credentials
AuthAll integrations authorizedAny expired OAuth tokens
PromptReviewed with constraintsGeneric/placeholder prompt
MonitoringAlerts configuredNo failure notification
CreditsBudget approvedNo credit plan
TestingAgent tested end-to-endUntested workflow paths

Error Handling

Check FailureSeverityAction
API key invalidCriticalBlock launch, regenerate key
Integration expiredHighRe-authorize before launch
No trigger filtersMediumAdd filters to prevent credit waste
No monitoringMediumSet up alerts before launch
Missing documentationLowDocument within first week

Resources

Next Steps

Proceed to lindy-upgrade-migration for version management.

What ships with it: 1 file

3.8 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.