Agent skill

Lindy Core Workflow B

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure Lindy triggers, scheduling, multi-agent delegation, and automation.

MITAuto-check passedProductivity & Automation

Install Lindy Core Workflow B

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-core-workflow-b --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-core-workflow-b .claude/skills/lindy-core-workflow-b && rm -rf skills-src

Use ~/.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/

Facts

Skill name
lindy-core-workflow-b
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
695 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure Lindy triggers, scheduling, multi-agent delegation, and automation.

  • Works in 8 steps: Configure Trigger Filters → Multiple Triggers (Same Workflow) → Multiple Workflows (Different Triggers) → …
  • Setting up trigger-based workflows
  • SKILL.md covers Overview, Prerequisites, Instructions and Trigger Types Quick Reference, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lindy Core Workflow B is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Productivity & Automation, covering Multi-agent orchestration and Workflow automation. 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

  • Setting up trigger-based workflows
  • Scheduling agents
  • Building multi-agent societies
  • Configuring agent delegation

Example prompts

  • “lindy automation”
  • “schedule lindy agent”
  • “lindy workflow automation”
  • “/lindy-core-workflow-b”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Configure Trigger Filters
  2. Multiple Triggers (Same Workflow)
  3. Multiple Workflows (Different Triggers)
  4. Schedule-Based Triggers
  5. Calendar Event Trigger
  6. Multi-Agent Delegation (Societies of Lindies)
  7. Linked Actions & Channels
  8. Looping

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:

    • Read
    • Write
    • Edit
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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):

    • lindy.ai
    • docs.lindy.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 Core Workflow B loads about 1.6k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 695 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

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). 695 words, ~1,639 tokens.

Download SKILL.mdSave it as .claude/skills/lindy-core-workflow-b/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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:*)
compatibility
Designed for Claude Code
version
1.20.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, lindy, workflow

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
    • +5 = trigger 5 minutes AFTER event starts
  3. Use case: Pre-meeting briefing agent pulls attendee data and sends summary
Step 6: Multi-Agent Delegation (Societies of Lindies)

Build modular agent systems where specialized agents collaborate:

Architecture:

[Lead Generator Lindy]
    ↓ Agent Send Message
[Outreach Lindy]
    ↓ Agent Send Message
[Meeting Scheduler Lindy]

Setup:

  1. Give the receiving agent an Agent Message Received trigger
  2. In the sending agent, add action: Agent Send Message
  3. Select the target Lindy from the dropdown (shows all agents with Agent triggers)
  4. Choose what context to pass — selective context reduces token cost

Benefits:

  • Modularity: Change one agent without affecting others
  • Cost savings: Send only relevant context, not full history
  • Specialization: Each agent excels at one task
  • Shared memory: Societies share memory across tasks
Step 7: Linked Actions & Channels

Linked Actions create downstream execution paths after an action completes:

  • Standard linked action: Immediate follow-up (email sent -> log to sheet)
  • Channel: Listen for future events (email sent -> wait for reply -> process reply)

Multi-channel example:

Send Email → [Channel: Email Reply Received]
           → [Channel: Slack Message Received]
Each channel maintains its own conversation thread.
Show full SKILL.md (295 more words)Show less
Step 8: Looping

For batch processing (e.g., process 50 leads from a spreadsheet):

  1. Add a Loop step
  2. Configure:
    • Items: Static list, dynamic data, or AI-generated
    • Max Cycles: Limit iterations (prevent runaway)
    • Max Concurrent: Parallel execution limit
    • Output: Data passed from inside the loop to subsequent steps
  3. Only defined loop output is accessible outside the loop

Trigger Types Quick Reference

TriggerFilter OptionsUse Case
Webhook ReceivedHeaders, body fieldsExternal API integration
Email ReceivedSender, subject, labelInbox automation
ScheduleTime, recurrenceRecurring reports
Chat MessageUser, contentInteractive bot
Slack MessageChannel, keyword, userTeam automation
Agent MessageSending agentMulti-agent delegation
Calendar EventEvent type, offsetMeeting automation
Google Sheets RowSheet, column valuesData pipeline

Error Handling

IssueCauseSolution
Trigger fires too oftenNo filter configuredAdd trigger filters with AND/OR conditions
Delegation failsTarget agent missing Agent triggerAdd Agent Message Received trigger to target
Schedule not firingTimezone mismatchVerify timezone in agent settings
Loop runs foreverNo max cycles setAlways set Max Cycles limit
Channel never activatesReply sent to wrong threadVerify thread context in channel config
Context too largePassing full history to delegateUse selective context in Agent Send Message

Output

Produce a production-ready workflow handoff: trigger contract, action sequence, idempotency strategy, escalation behavior, and test results for both success and failure paths. State which downstream system owns each side effect.

Examples

For an inbox-triage workflow, receive one message event, classify it against a fixed policy, create one follow-up task only when the policy requires it, and write the event ID to the idempotency store. Replaying the fixture demonstrates that the same message cannot create a duplicate task.

Resources

Next Steps

Proceed to lindy-common-errors for troubleshooting.

© 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 1 other file (references) in skills/.curated/lindy-core-workflow-b of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lindy Core Workflow B 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.

Lindy Core Workflow B compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lindy Core Workflow B this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: PassMIT
Fastgpt Workflow GeneratorYYH211/Claude-meta-skill282—~5.5kAutomated safety check: PassMIT
cmux Agent Surface Controldisler/learning-cmux-with-agents115—~2.6kAutomated safety check: NotesMIT
GTM Engineeringtech-leads-club/agent-skills7k—~4.8kAutomated safety check: PassCustom licence
Workflow Automationruvnet/ruflo74k1 repos~440Automated safety check: PassMIT
Superset Agent Standupsuperset-sh/superset15k—~712Automated safety check: PassCustom licence

Similar skills

  • Fastgpt Workflow Generator

    YYH211/Claude-meta-skill

    Generates production-ready FastGPT workflow JSON from natural language requirements.

    282 GitHub stars~5.5k tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed
  • cmux Agent Surface Control

    disler/learning-cmux-with-agents

    Drives the cmux terminal multiplexer from natural language to open, inspect, prompt, read and close windows, workspaces, panes, surfaces and agent sessions.

    115 GitHub stars~2.6k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check: notes
  • GTM Engineering

    tech-leads-club/agent-skills

    Designs go-to-market automation and AI agent workflows for revenue teams, built on the idea that architecture and context matter more than any single tool.

    7k GitHub stars~4.8k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Workflow creation, execution, and template management. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 1 repo~440 tokens
    Productivity & AutomationAuto-check passed
  • Superset Agent Standup

    superset-sh/superset

    Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.

    15k GitHub stars~712 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Flow Nexus Swarm

    ruvnet/agentic-flow

    Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform

    817 GitHub starsUsed in 4 repos~4.2k tokens
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing 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.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • 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.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • 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.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Lindy Core Workflow B

What does Lindy Core Workflow B do?

Configure Lindy triggers, scheduling, multi-agent delegation, and automation. Lindy Core Workflow B is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Lindy triggers, scheduling, multi-agent delegation, and automation.

When should I use Lindy Core Workflow B?

Lindy Core Workflow B fits situations like: setting up trigger-based workflows; scheduling agents; building multi-agent societies; configuring agent delegation.

How do I install Lindy Core Workflow B in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code`. Or copy the skill folder (skills/.curated/lindy-core-workflow-b in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-core-workflow-b in your project. Claude Code loads it when a task matches its description.

How do I install Lindy Core Workflow B in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a codex`. Or copy the skill folder (skills/.curated/lindy-core-workflow-b in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-core-workflow-b in your project. Codex loads it when a task matches its description.

Can I use Lindy Core Workflow B 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-core-workflow-b -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-core-workflow-b, .gemini/skills/lindy-core-workflow-b, .github/skills/lindy-core-workflow-b and .opencode/skills/lindy-core-workflow-b in your project.

What does Lindy Core Workflow B need to run?

SKILL.md names no scripts, command-line tools or credentials: Lindy Core Workflow B is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Lindy Core Workflow B access the network?

SKILL.md names 2 domains. As links in the text: lindy.ai and docs.lindy.ai. This is read from the text; nothing was executed.

Is Lindy Core Workflow B 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 Core Workflow B use?

Lindy Core Workflow B 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 Core Workflow B use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 859 tokens, read only when the agent opens those files.

What are the alternatives to Lindy Core Workflow B?

Skills that share tags, products or a category with Lindy Core Workflow B: Fastgpt Workflow Generator (YYH211/Claude-meta-skill, 282 stars), cmux Agent Surface Control (disler/learning-cmux-with-agents, 115 stars), GTM Engineering (tech-leads-club/agent-skills, 7k stars) and Workflow Automation (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lindy Core Workflow B?

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.