Apify Integration Development
apify/agent-skills
Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.
Agent skill
Lindy Migration Deep Dive
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Advanced migration strategies for moving to Lindy AI from other platforms.
Install Lindy Migration Deep Dive
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-dive --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .claude/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .claude/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-diveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-dive --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .agents/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .agents/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-dive --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .cursor/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .cursor/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/lindy-migration-deep-dive--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-dive --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .gemini/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .gemini/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-diveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .github/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .github/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-migration-deep-dive --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/lindy-migration-deep-dive .opencode/skills/lindy-migration-deep-dive && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lindy-migration-deep-dive" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-migration-deep-dive into .opencode/skills/lindy-migration-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-migration-deep-dive", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lindy-migration-deep-dive- GitHub stars
- 2.8k
- Token cost
- ~2k tokens
- SKILL.md length
- 713 words
- Files
- 3 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Advanced migration strategies for moving to Lindy AI from other platforms.
- Works in 6 steps: Inventory Source Automations → Classify Migration Complexity → Migration Strategy by Source → …
- Migrating from Zapier
- SKILL.md covers Overview, Prerequisites, Migration Source Comparison and Instructions, plus 6 more sections
- Calls make
What it does
Lindy Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Advanced migration strategies for moving to Lindy AI from other platforms. Use when migrating from Zapier, Make, n8n, custom automations, or consolidating fragmented agent systems. Trigger with phrases like "lindy migration", "migrate to lindy", "zapier to lindy", "switch to lindy", "consolidate automations".
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in Productivity & Automation, covering Workflow automation. It works with Zapier, n8n and LangChain. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Migrating from Zapier
- Custom automations
- Consolidating fragmented agent systems
- With phrases like lindy migration
Example prompts
- “lindy migration”
- “migrate to lindy”
- “zapier to lindy”
- “/lindy-migration-deep-dive”
Requirements
- Python 3
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(curl:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.lindy.ailindy.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Lindy Migration Deep Dive loads about 2k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 713 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 713 words, ~2,007 tokens.
Download SKILL.mdSave it as
.claude/skills/lindy-migration-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- lindy-migration-deep-dive
- description
- Advanced migration strategies for moving to Lindy AI from other platforms. Use when migrating from Zapier, Make, n8n, custom automations, or consolidating fragmented agent systems. Trigger with phrases like "lindy migration", "migrate to lindy", "zapier to lindy", "switch to lindy", "consolidate automations".
- allowed-tools
- Read, Write, Edit, Bash(curl:*)
- compatibility
- Designed for Claude Code
- version
- 1.20.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, lindy, migration
Lindy Migration Deep Dive
Overview
Migrate existing automation workflows from Zapier, Make (Integromat), n8n, LangChain, or custom code to Lindy AI. Key insight: Lindy replaces rigid rule-based automations with AI agents that can reason, adapt, and handle ambiguity — so migration is a redesign opportunity, not a 1:1 translation.
Prerequisites
- Inventory of existing automations (source platform)
- Lindy workspace ready with required integrations authorized
- Migration timeline approved
- Rollback plan defined for customer-facing workflows
Migration Source Comparison
| Source Platform | Lindy Equivalent | Key Difference |
|---|---|---|
| Zapier Zap | Lindy Agent | AI reasoning replaces rigid if/then |
| Make Scenario | Lindy Agent | No-code builder instead of module chains |
| n8n Workflow | Lindy Agent | Managed infra, no self-hosting |
| LangChain Agent | Lindy Agent Step | No-code, managed, no Python needed |
| Custom code | HTTP Request + Run Code | Less code, AI fills gaps |
Instructions
Step 1: Inventory Source Automations
For each existing automation, document:
| Field | Example |
|---|---|
| Name | Support Email Triage |
| Trigger | New email in support@co.com |
| Steps | 1. Parse email 2. Classify 3. Route to channel |
| Integrations | Gmail, Slack, Sheets |
| Frequency | ~50 runs/day |
| Complexity | Medium (3 steps, 1 condition) |
Step 2: Classify Migration Complexity
| Complexity | Criteria | Migration Approach | Time |
|---|---|---|---|
| Simple | 1-3 steps, no conditions | Build from scratch in Lindy | 30 min |
| Medium | 4-8 steps, conditions | Natural language description to Agent Builder | 1-2 hours |
| Complex | 9+ steps, multi-branch, loops | Redesign as multi-agent society | 1-2 days |
| Custom code | Python/JS logic | Run Code action + HTTP Request | 2-4 hours |
Step 3: Migration Strategy by Source
From Zapier:
Zapier Pattern → Lindy Pattern
────────────────────────────────
Trigger (New Email) → Trigger (Email Received)
Filter Step → Trigger Filter (more efficient)
Formatter → AI Prompt field mode (AI does formatting)
Lookup → Knowledge Base search or HTTP Request
Multi-step Zap → Single agent with conditions
Paths → Conditions (natural language branching)From Make (Integromat):
Make Pattern → Lindy Pattern
────────────────────────────────
Scenario → Agent workflow
Module → Action step
Router → Conditions
Iterator → Loop
Aggregator → Run Code action (consolidation logic)
Error Handler → Agent prompt error instructionsFrom n8n:
n8n Pattern → Lindy Pattern
────────────────────────────────
Trigger Node → Trigger
Function Node → Run Code (Python/JS)
HTTP Request Node → HTTP Request action
IF Node → Condition
Merge Node → Agent step (AI merges intelligently)From LangChain/Custom Code:
LangChain Pattern → Lindy Pattern
────────────────────────────────
Agent → Agent Step with skills
Tool → Action or HTTP Request
Memory → Lindy Memory (persistent)
Chain → Workflow steps
Vector Store → Knowledge Base
Retrieval Chain → Knowledge Base + AI PromptStep 4: Execute Migration (Phased)
Phase 1: Internal-Only Agents (Days 1-3)
- Migrate non-customer-facing automations first
- Build in Lindy using natural language description
- Test with real data for 48 hours
- Compare output quality to source automation
- Decommission source automation after verification
Phase 2: Low-Risk Customer-Facing (Days 4-7)
- Build Lindy agent alongside existing automation (parallel run)
- Route 10% of traffic to Lindy agent
- Compare results for 48 hours
- Gradually increase to 50%, then 100%
- Monitor task success rate and response quality
Phase 3: Critical Workflows (Days 8-14)
- Build Lindy agent as exact replacement
- Test extensively with staging data
- Schedule cutover during low-traffic window
- Keep source automation pausable (not deleted) for 7 days
- Monitor closely for 48 hours post-cutover
Step 5: Redesign Opportunities
Migration is a chance to improve, not just replicate:
| Old Pattern | Lindy Improvement |
|---|---|
| Rigid if/then classification | AI classifies naturally, handles edge cases |
| Template-based email responses | AI generates contextual, personalized responses |
| Multiple automations for variations | Single agent with conditions handles all |
| Manual data transformation | Run Code action or AI handles transformation |
| No error handling | Agent prompt includes fallback behavior |
Show full SKILL.md (275 more words)Show less
Step 6: Validate and Cutover
# Post-migration validation checklist
echo "=== Migration Validation ==="
# 1. Task completion rate
echo "Check: Agent Tasks tab - expect >95% success rate"
# 2. Response quality
echo "Check: Compare 10 agent outputs to old automation outputs"
# 3. Trigger coverage
echo "Check: All events triggering correctly (no missed events)"
# 4. Performance
echo "Check: Task duration within acceptable range"
# 5. Cost
echo "Check: Credit consumption within budget"Migration Checklist
- Source system inventory complete
- Each automation classified by complexity
- Lindy integrations authorized
- Phase 1 (internal) agents migrated and verified
- Phase 2 (low-risk) agents running in parallel
- Phase 3 (critical) agents tested with staging data
- Cutover window scheduled
- Rollback procedure tested
- Source automations paused (not deleted)
- 7-day post-cutover monitoring complete
- Source automations decommissioned
Output
Create a migration record that maps each source automation to its proposed Lindy workflow, risk tier, owner, test corpus, success measures, rollback trigger, and disposition. For every customer-facing cutover, retain the parallel-run comparison and the evidence used to pause, proceed, or roll back; do not treat a configured agent as proof of behavioral equivalence.
Examples
For a support-triage workflow, replay a sanitized fixed case set through both systems, compare routing and escalation outcomes, then shadow a bounded slice of live traffic without allowing duplicate customer actions. Increase traffic only after the recorded thresholds pass. If escalation recall falls below the agreed floor, route all traffic back to the source automation and preserve the failed comparison for prompt and condition redesign.
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Output quality lower | AI prompt needs tuning | Add few-shot examples to agent prompt |
| Missing edge cases | Source had specific rules | Add condition branches or prompt instructions |
| Higher cost than expected | Overuse of large models | Right-size models per step |
| Integration auth fails | OAuth not set up in Lindy | Authorize integrations before migration |
| Data format mismatch | Different field names | Map fields in Run Code action |
Resources
Next Steps
This completes the Flagship tier. Review Standard and Pro skills for comprehensive Lindy mastery.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/.curated/lindy-migration-deep-dive of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/implementation-guide.md
- references/implementation.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Lindy Migration Deep Dive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lindy Migration Deep Dive this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Apify Integration Developmentapify/agent-skills | 2.4k | — | ~3.4k | Automated safety check: Pass | None | |
| N8n Agentssickn33/agentic-awesome-skills | 47k | 1 repos | ~6k | Automated safety check: Pass | MIT | |
| N8nericrisco/rsc-harness | 180 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Zapierericrisco/rsc-harness | 180 | — | ~2.8k | Automated safety check: Notes | MIT | |
| n8n Custom Code Tool Guideczlonkowski/n8n-skills | 6.4k | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
- Official
N8n Agents
sickn33/agentic-awesome-skills
Design n8n AI agents, chains, classifiers, extractors, tool calling, memory, RAG, structured output, and human-review flows.
N8n
ericrisco/rsc-harness
A skill your agent uses when operating a live n8n instance programmatically — its REST API ({host}/api/v1, X-N8N-API-KEY) or the n8n-mcp server — to create, validate, test, activate, update, delete…
Zapier
ericrisco/rsc-harness
A skill your agent uses when operating Zapier from an agent through the official hosted Zapier MCP server — connecting with a bearer key, discovering an app's actions, enabling one, and invoking a…
n8n Custom Code Tool Guide
czlonkowski/n8n-skills
Explains the n8n Custom Code Tool's actual runtime contract so an AI-agent-callable tool doesn't get written like a regular workflow Code node.
Automation Instructions
deusXmachina-dev/memorylane
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Lindy Migration Deep Dive
What does Lindy Migration Deep Dive do?
Advanced migration strategies for moving to Lindy AI from other platforms. Lindy Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Advanced migration strategies for moving to Lindy AI from other platforms.
When should I use Lindy Migration Deep Dive?
Lindy Migration Deep Dive fits situations like: migrating from Zapier; custom automations; consolidating fragmented agent systems; with phrases like lindy migration.
How do I install Lindy Migration Deep Dive in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a claude-code`. Or copy the skill folder (skills/.curated/lindy-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-migration-deep-dive in your project. Claude Code loads it when a task matches its description.
How do I install Lindy Migration Deep Dive in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a codex`. Or copy the skill folder (skills/.curated/lindy-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-migration-deep-dive in your project. Codex loads it when a task matches its description.
Can I use Lindy Migration Deep Dive in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-migration-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lindy-migration-deep-dive, .gemini/skills/lindy-migration-deep-dive, .github/skills/lindy-migration-deep-dive and .opencode/skills/lindy-migration-deep-dive in your project.
What does Lindy Migration Deep Dive need to run?
Going by SKILL.md and its folder, Lindy Migration Deep Dive needs the command-line tools its instructions call (make). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Lindy Migration Deep Dive access the network?
SKILL.md names 2 domains. As links in the text: docs.lindy.ai and lindy.ai. This is read from the text; nothing was executed.
Is Lindy Migration Deep Dive safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lindy Migration Deep Dive use?
Lindy Migration Deep Dive is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lindy Migration Deep Dive use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Lindy Migration Deep Dive?
Skills that share tags, products or a category with Lindy Migration Deep Dive: Apify Integration Development (apify/agent-skills, 2.4k stars), N8n Agents (sickn33/agentic-awesome-skills, 47k stars), N8n (ericrisco/rsc-harness, 180 stars) and Zapier (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lindy Migration Deep Dive?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.