Agent skill · software engineering · jeremylongshore
lindy-upgrade-migration
Manage Lindy agent configuration changes, platform updates, and migrations.
Why this skill is useful
Provides detailed migration procedures and configurations specific to the Lindy platform that the AI wouldn't reliably generate on its own.
What it needs
Requires lindy account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Upgrade and Migration Overview Plan and verify changes to Lindy workflows through the documented workspace UI. Use Lindy's Version History as the in-place restoration mechanism, the Test Panel for controlled execution, and the Tasks view for run evidence. Do not invent a Lindy SDK, API key, package upgrade, CLI, export endpoint, or control plane. Use Read to inspect the approved change record and evidence. Use Write or Edit to maintain the migration record without copying secrets or customer data. Prerequisites Authorized access to every source and target workspace in scope. A named change owner, approver, rollback owner, and acceptance owner. A known-good saved agent version visible in Version History. A current inventory of triggers, actions, conditions, integrations, knowledge sources, manual approval steps, owners, and downstream side effects. Synthetic inputs and sandboxed destinations for Test Panel runs; its tests can execute real actions and call real external systems. Baseline task receipts from the Tasks view and explicit acceptance criteria. Current Lindy documentation and workspace evidence for any transfer or feature behavior relied upon by the change. Instructions Step 1: Define the change boundary Record whether this is an in-place configuration change, restoration, template- based recreation, or workspace move. List the exact workflows, integrations, callers, secrets, data stores, approvers, and external side effects in scope. Treat anything not documented by Lindy or directly observed in the target workspace as NOT VERIFIED. Templates are starting workflows that must be configured, customized, and tested; do not assume they preserve credentials, triggers, knowledge, memories, phone or mail resources, permissions, approval rules, webhook URLs, or other workspace-bound state. Step 2: Capture a rollback anchor and baseline 1. Save the current working workflow with a descriptive version name. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-upgrade-migration--0a32ef