Implement security best practices for Lindy AI integrations. Use when securing API keys, configuring permissions, or implementing security controls. Trigger with phrases like "lindy security", "secure lindy", "lindy API key security", "lindy permissions".
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: lindy-security-basics description: | Implement security best practices for Lindy AI integrations. Use when securing API keys, configuring permissions, or implementing security controls. Trigger with phrases like "lindy security", "secure lindy", "lindy API key security", "lindy permissions". allowed-tools: Read, Write, Edit version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
Lindy Security Basics
Overview
Essential security practices for Lindy AI integrations.
Prerequisites
- Lindy account with admin access
- Understanding of security requirements
- Access to secret management solution
Instructions
Step 1: Secure API Key Storage
// NEVER do this
const apiKey = 'lnd_abc123...'; // Hardcoded - BAD!
// DO this instead
const apiKey = process.env.LINDY_API_KEY;
// Or use secret management
import { SecretManager } from '@google-cloud/secret-manager';
async function getApiKey(): Promise<string> {
const client = new SecretManager();
const [secret] = await client.accessSecretVersion({
name: 'projects/my-project/secrets/lindy-api-key/versions/latest',
});
return secret.payload?.data?.toString() || '';
}
Step 2: Environment-Specific Keys
# .env.development
LINDY_API_KEY=lnd_dev_xxx
LINDY_ENVIRONMENT=development
# .env.production
LINDY_API_KEY=lnd_prod_xxx
LINDY_ENVIRONMENT=production
// Validate environment
function validateEnvironment(): void {
const env = process.env.LINDY_ENVIRONMENT;
const key = process.env.LINDY_API_KEY;
if (!key) {
throw new Error('LINDY_API_KEY not set');
}
if (env === 'production' && key.startsWith('lnd_dev_')) {
throw new Error('Development key used in production!');
}
}
Step 3: Configure Agent Permissions
import { Lindy } from '@lindy-ai/sdk';
const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });
async function createSecureAgent() {
const agent = await lindy.agents.create({
name: 'Secure Agent',
instructions: 'Handle data securely.',
permissions: {
// Restrict to specific tools
allowedTools: ['email', 'calendar'],
// Prevent external network access
networkAccess: 'internal-only',
// Limit data access
dataScopes: ['read:users', 'write:tickets'],
},
});
return agent;
}
Step 4: Audit Logging
async function withAuditLog<T>(
operation: string,
fn: () => Promise<T>
): Promise<T> {
const start = Date.now();
const requestId = crypto.randomUUID();
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
timestamp: new Date().toISOString(),
status: 'started',
}));
try {
const result = await fn();
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
duration: Date.now() - start,
status: 'completed',
}));
return result;
} catch (error: any) {
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
duration: Date.now() - start,
status: 'failed',
error: error.message,
}));
throw error;
}
}
Security Checklist
[ ] API keys stored in environment variables or secret manager
[ ] Different keys for dev/staging/prod environments
[ ] Key validation on startup
[ ] Agent permissions configured (least privilege)
[ ] Audit logging enabled
[ ] Network access restricted where possible
[ ] Regular key rotation scheduled
[ ] Access reviewed quarterly
Output
- Secure API key storage patterns
- Environment-specific configuration
- Agent permission controls
- Audit logging implementation
Error Handling
| Risk | Mitigation | Implementation |
|---|---|---|
| Key exposure | Secret manager | Use cloud secrets |
| Wrong env | Validation | Check key prefix |
| Over-permission | Least privilege | Restrict agent tools |
| No audit | Logging | Log all operations |
Examples
Production-Ready Security
// security/index.ts
export async function initializeLindy(): Promise<Lindy> {
// Validate environment
validateEnvironment();
// Get key from secret manager
const apiKey = await getApiKey();
// Initialize with security options
const lindy = new Lindy({
apiKey,
timeout: 30000,
retries: 3,
});
// Verify connection
await lindy.users.me();
console.log('Lindy initialized securely');
return lindy;
}
Resources
Next Steps
Proceed to lindy-prod-checklist for production readiness.
More by jeremylongshore
View allRabbitmq Queue Setup - Auto-activating skill for Backend Development. Triggers on: rabbitmq queue setup, rabbitmq queue setup Part of the Backend Development skill category.
evaluating-machine-learning-models: This skill allows Claude to evaluate machine learning models using a comprehensive suite of metrics. It should be used when the user requests model performance analysis, validation, or testing. Claude can use this skill to assess model accuracy, precision, recall, F1-score, and other relevant metrics. Trigger this skill when the user mentions "evaluate model", "model performance", "testing metrics", "validation results", or requests a comprehensive "model evaluation".
building-neural-networks: This skill allows Claude to construct and configure neural network architectures using the neural-network-builder plugin. It should be used when the user requests the creation of a new neural network, modification of an existing one, or assistance with defining the layers, parameters, and training process. The skill is triggered by requests involving terms like "build a neural network," "define network architecture," "configure layers," or specific mentions of neural network types (e.g., "CNN," "RNN," "transformer").
Oauth Callback Handler - Auto-activating skill for API Integration. Triggers on: oauth callback handler, oauth callback handler Part of the API Integration skill category.
