Why Use This This skill provides specialized capabilities for jeremylongshore's codebase.
Use Cases Developing new features in the jeremylongshore repository Refactoring existing code to follow jeremylongshore standards Understanding and working with jeremylongshore's codebase structure
Install Guide 2 steps 1 2 Install inside Ananke
Click Install Skill, paste the link below, then press Install.
https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/saas-packs/lindy-pack/skills/lindy-security-basics Skill Snapshot Auto scan of skill assets. Informational only.
Valid SKILL.md Checks against SKILL.md specification
Source & Community
Updated At Jan 9, 2026, 12:57 AM
Skill Stats
SKILL.md 199 Lines
Total Files 1
Total Size 4.6 KB
License MIT
---
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 <[email protected] >
---
# 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
```typescript
// 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
```bash
# .env.development
LINDY_API_KEY=lnd_dev_xxx
LINDY_ENVIRONMENT=development
# .env.production
LINDY_API_KEY=lnd_prod_xxx
LINDY_ENVIRONMENT=production
```
```typescript
// 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
```typescript
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
```typescript
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
```markdown
[ ] 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
```typescript
// 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
- [Lindy Security](https://docs.lindy.ai/security)
- [API Key Best Practices](https://docs.lindy.ai/security/api-keys)
- [SOC 2 Compliance](https://lindy.ai/security)
## Next Steps
Proceed to `lindy-prod-checklist` for production readiness.