Implement Retell AI lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Retell AI integrations, implementing pre-commit hooks, or configuring CI policy checks for Retell AI best practices. Trigger with phrases like "retellai policy", "retellai lint", "retellai guardrails", "retellai best practices check", "retellai eslint".
Implements lint rules and policy checks for Retell AI integrations via ESLint, pre-commit hooks, and CI/CD.
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install retellai-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Automated policy enforcement and guardrails for Retell AI integrations.
// eslint-plugin-retellai/rules/no-hardcoded-keys.js
module.exports = {
meta: {
type: 'problem',
docs: {
description: 'Disallow hardcoded Retell AI API keys',
},
fixable: 'code',
},
create(context) {
return {
Literal(node) {
if (typeof node.value === 'string') {
if (node.value.match(/^sk_(live|test)_[a-zA-Z0-9]{24,}/)) {
context.report({
node,
message: 'Hardcoded Retell AI API key detected',
});
}
}
},
};
},
};
// .eslintrc.js
module.exports = {
plugins: ['retellai'],
rules: {
'retellai/no-hardcoded-keys': 'error',
'retellai/require-error-handling': 'warn',
'retellai/use-typed-client': 'warn',
},
};
# .pre-commit-config.yaml
repos:
- repo: local
hooks:
- id: retellai-secrets-check
name: Check for Retell AI secrets
entry: bash -c 'git diff --cached --name-only | xargs grep -l "sk_live_" && exit 1 || exit 0'
language: system
pass_filenames: false
- id: retellai-config-validate
name: Validate Retell AI configuration
entry: node scripts/validate-retellai-config.js
language: node
files: '\.retellai\.json$'
// Enforce typed configuration
interface Retell AIStrictConfig {
apiKey: string; // Required
environment: 'development' | 'staging' | 'production'; // Enum
timeout: number; // Required number, not optional
retries: number;
}
// Disallow any in Retell AI code
// @ts-expect-error - Using any is forbidden
const client = new Client({ apiKey: any });
// Prefer this
const client = new RetellAIClient(config satisfies Retell AIStrictConfig);
# ADR-001: Retell AI Client Initialization
## Status
Accepted
## Context
We need to decide how to initialize the Retell AI client across our application.
## Decision
We will use the singleton pattern with lazy initialization.
## Consequences
- Pro: Single client instance, connection reuse
- Pro: Easy to mock in tests
- Con: Global state requires careful lifecycle management
## Enforcement
- ESLint rule: retellai/use-singleton-client
- CI check: grep for "new RetellAIClient(" outside allowed files
# retellai-policy.rego
package retellai
# Deny production API keys in non-production environments
deny[msg] {
input.environment != "production"
startswith(input.apiKey, "sk_live_")
msg := "Production API keys not allowed in non-production environment"
}
# Require minimum timeout
deny[msg] {
input.timeout < 10000
msg := sprintf("Timeout too low: %d < 10000ms minimum", [input.timeout])
}
# Require retry configuration
deny[msg] {
not input.retries
msg := "Retry configuration is required"
}
# .github/workflows/retellai-policy.yml
name: Retell AI Policy Check
on: [push, pull_request]
jobs:
policy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check for hardcoded secrets
run: |
if grep -rE "sk_(live|test)_[a-zA-Z0-9]{24,}" --include="*.ts" --include="*.js" .; then
echo "ERROR: Hardcoded Retell AI keys found"
exit 1
fi
- name: Validate configuration schema
run: |
npx ajv validate -s retellai-config.schema.json -d config/retellai/*.json
- name: Run ESLint Retell AI rules
run: npx eslint --plugin retellai --rule 'retellai/no-hardcoded-keys: error' src/
// Prevent dangerous operations in production
const BLOCKED_IN_PROD = ['deleteAll', 'resetData', 'migrateDown'];
function guardRetell AIOperation(operation: string): void {
const isProd = process.env.NODE_ENV === 'production';
if (isProd && BLOCKED_IN_PROD.includes(operation)) {
throw new Error(`Operation '${operation}' blocked in production`);
}
}
// Rate limit protection
function guardRateLimits(requestsInWindow: number): void {
const limit = parseInt(process.env.RETELLAI_RATE_LIMIT || '100');
if (requestsInWindow > limit * 0.9) {
console.warn('Approaching Retell AI rate limit');
}
if (requestsInWindow >= limit) {
throw new Error('Retell AI rate limit exceeded - request blocked');
}
}
Implement custom lint rules for Retell AI patterns.
Set up hooks to catch issues before commit.
Implement policy-as-code in CI pipeline.
Add production safeguards for dangerous operations.
| Issue | Cause | Solution |
|---|---|---|
| ESLint rule not firing | Wrong config | Check plugin registration |
| Pre-commit skipped | --no-verify | Enforce in CI |
| Policy false positive | Regex too broad | Narrow pattern match |
| Guardrail triggered | Actual issue | Fix or whitelist |
npx eslint --plugin retellai --rule 'retellai/no-hardcoded-keys: error' src/
For architecture blueprints, see retellai-architecture-variants.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.