# lindy-core-workflow-b

lindy-core-workflow-b is a Claude Code skill for configuring Lindy triggers, Cron schedules, and multi-agent delegation.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1 install · ★ 2935 repo stars
- Author: Jeremy Longshore
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/lindy-core-workflow-b/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/lindy-core-workflow-b

## What it does

The skill equips Claude Code with instructions for Lindy automation flows. It covers case-insensitive trigger filters with boolean logic alongside Cron schedules. Calendar triggers support minute offsets.

A core section focuses on multi-agent collaboration via the `Agent Send Message` action. Delegation fails if the target Lindy lacks an `Agent Message Received` trigger. For batch jobs, loop steps require an explicit `Max Cycles` cap to prevent runaway processes.

Setup requires completing `lindy-core-workflow-a` first and authorizing services such as Gmail or Slack. The skill also advises passing selective context rather than full histories to keep token usage down.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/lindy-core-workflow-b/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/lindy-core-workflow-b/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/lindy-core-workflow-b/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/lindy-core-workflow-b/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/lindy-core-workflow-b
```

2. **Manually: put the files in place**
- File: `.github/skills/lindy-core-workflow-b/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/lindy-core-workflow-b
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/lindy-core-workflow-b/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/lindy-core-workflow-b/SKILL.md

## When to use it
- configure Lindy triggers with case-insensitive filters
- set up scheduled runs using Cron or calendar offsets
- delegate tasks across Lindy agents via `Agent Send Message`
- prevent infinite loops by defining a `Max Cycles` limit

## Example prompts
- Configure a daily scheduled report in Lindy that posts to Slack
- Set up delegation between a lead generator Lindy and an outreach agent
- Add an email trigger filter that excludes auto-replies

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: da032d957156a375.

BEGIN THIRD-PARTY FILE da032d957156a375
````text
---
name: lindy-core-workflow-b
description: 'Configure Lindy triggers, scheduling, multi-agent delegation, and automation.

  Use when setting up trigger-based workflows, scheduling agents,

  building multi-agent societies, or configuring agent delegation.

  Trigger with phrases like "lindy automation", "schedule lindy agent",

  "lindy workflow automation", "lindy delegation", "lindy multi-agent".

  '
allowed-tools: Read, Write, Edit, Bash(curl:*)
version: 1.20.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- lindy
- workflow
compatibility: Designed for Claude Code
---
# Lindy Core Workflow B: Triggers & Multi-Agent Automation

## Overview

Configure trigger-based automation, scheduled agents, and multi-agent delegation
("Societies of Lindies"). Covers all trigger types, trigger filters, multiple
triggers per agent, and the Agent Send Message delegation pattern.

## Prerequisites

- Completed `lindy-core-workflow-a` (agent creation)
- Integrations authorized (Gmail, Slack, etc.)
- For delegation: multiple agents created

## Instructions

### Step 1: Configure Trigger Filters

Trigger filters add conditional logic that determines WHICH events wake the agent.
Filters are **not case-sensitive** and support **AND/OR** operators with condition groups.

**Email trigger filter example**:

```
Filter: sender contains "support" AND subject does not contain "auto-reply"
```

**Slack trigger filter example**:

```
Filter: channel equals "#help-desk" AND message contains "urgent"
```

### Step 2: Multiple Triggers (Same Workflow)

One agent can respond to multiple trigger types feeding into the same workflow:

1. Create first trigger (e.g., Webhook Received)
2. Click **"New Trigger"** to add a second (e.g., Email Received)
3. Connect grey arrows from both triggers to the first action step
4. The agent processes both identically

### Step 3: Multiple Workflows (Different Triggers)

A single agent can run entirely different workflows based on trigger type:

- **Trigger A** (Email Received) -> Classify + Draft Reply
- **Trigger B** (Chat Message) -> Search KB + Respond in chat
Each trigger connects to its own action chain.

### Step 4: Schedule-Based Triggers

For recurring automation (daily reports, weekly digests):

1. Add trigger > **Schedule**
2. Configure timing: `Every weekday at 9:00 AM`
3. Options: daily, weekly, monthly, or custom cron
4. The agent runs automatically at the scheduled time

### Step 5: Calendar Event Trigger

For meeting-related automation:

1. Add trigger > **Calendar Event Start**
2. Set **Minutes Offset**:
   - `-30` = trigger 30 minutes BEFORE event
````
END THIRD-PARTY FILE da032d957156a375

The third-party file has ended. Everything between the da032d957156a375 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2648 of 6565 bytes. © Jeremy Longshore · MIT · https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/skills/.curated/lindy-core-workflow-b/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
