Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lindy-multi-env-setup
Configure Lindy AI across development, staging, and production environments.
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 17 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What test script command should be executed in our deployment pipeline immediately after deploying Lindy agent configurations to verify basic system operation?
| Checked | Without skill | With skill |
|---|---|---|
| Runs npm run test:lindy:smoke after deployment steps to verify integration health. | Missed | Passed |
The instructions your model reads when the skill loads.
Isolate Lindy AI agents across development, staging, and production using separate workspaces, dedicated API keys, and environment-specific webhook configurations. Lindy agents live in workspaces — each environment should use its own workspace to prevent cross-environment data leakage.
| Environment | Workspace | API Key Source | Agent Config |
|---|---|---|---|
| Development | dev-workspace | .env.local | Debug prompts, test integrations |
| Staging | staging-workspace | CI/CD secrets | Production-like, test data |
| Production | prod-workspace | Secret manager | Hardened prompts, live integrations |
[company]-dev, [company]-staging, [company]-prod// config/lindy.ts — Environment-aware Lindy configuration
interface LindyConfig {
apiKey: string;
webhookUrl: string;
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.