New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lindy Install Auth

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

Set up a Lindy account and authenticated webhook trigger. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check: notesBackend & APIs

Install Lindy Install Auth

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-install-auth -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-install-auth --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-install-auth .claude/skills/lindy-install-auth && 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-install-auth
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
482 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Set up a Lindy account and authenticated webhook trigger. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 4 steps: Create the Webhook Trigger → Configure Bearer Authentication → Verify Authorized Connectivity → …
  • Onboarding to Lindy
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 5 more sections
  • Calls curl; reaches public.lindy.ai; needs LINDY_TRIGGER_SECRET

What it does

Lindy Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up a Lindy account and authenticated webhook trigger. Use when onboarding to Lindy, configuring bearer authentication for webhook triggers, or connecting Lindy agents to your application. Trigger with phrases like "install lindy", "setup lindy", "lindy auth", "configure lindy webhook", "lindy webhook secret".

Its SKILL.md is about 1.2k 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 Backend & APIs, covering Webhooks and Authentication. 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

  • Onboarding to Lindy
  • Configuring bearer authentication for webhook triggers
  • Connecting Lindy agents to your application
  • With phrases like install lindy

Example prompts

  • “install lindy”
  • “setup lindy”
  • “lindy auth”
  • “/lindy-install-auth”

Requirements

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

Workflow steps

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

  1. Create the Webhook Trigger
  2. Configure Bearer Authentication
  3. Verify Authorized Connectivity
  4. Verify Rejection Without Authentication

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

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • public.lindy.ai

    Also links to:

    • docs.lindy.ai
    • lindy.ai
    • status.lindy.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LINDY_TRIGGER_SECRET

    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 Install Auth loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 482 words of instructions outside code blocks.

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

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

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:123
    - [ ] `.env` files ignored and limited to development fixtures

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). 482 words, ~1,233 tokens.

Download SKILL.mdSave it as .claude/skills/lindy-install-auth/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lindy-install-auth
description
Set up a Lindy account and authenticated webhook trigger. Use when onboarding to Lindy, configuring bearer authentication for webhook triggers, or connecting Lindy agents to your application. Trigger with phrases like "install lindy", "setup lindy", "lindy auth", "configure lindy webhook", "lindy webhook secret".
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, api, authentication

Lindy Install & Auth

Overview

Lindy AI is a no-code/low-code AI agent platform. Agents ("Lindies") are built in its web dashboard. This setup uses Lindy's documented webhook trigger: Lindy provides the trigger URL, and the caller authenticates with a bearer secret.

Prerequisites

  • Lindy account with permission to create or edit an agent
  • A secret manager for the trigger credential
  • curl or another HTTP client for a synthetic connectivity check
  • A non-production test payload that contains no customer data

Instructions

Step 1: Create the Webhook Trigger
  1. Open the target agent in the Lindy dashboard.
  2. Add a webhook trigger and copy its generated URL.
  3. Store the complete URL as a secret because its unique path identifies the trigger.
  4. Record only the host and a redacted path in setup receipts.
Step 2: Configure Bearer Authentication

In the webhook trigger's authentication controls, click Generate Secret and copy the Lindy-generated value into your secret manager. Store it separately from any credential used by an HTTP Request action to call your application.

bash
# Load the copied Lindy URL and generated secret from a secret manager.
export LINDY_TRIGGER_URL="https://public.lindy.ai/api/v1/webhooks/YOUR_WEBHOOK_ID"
export LINDY_TRIGGER_SECRET="replace-with-the-lindy-generated-secret"

Callers must include that generated value as bearer authentication in every request.

Step 3: Verify Authorized Connectivity
bash
curl --fail-with-body -X POST "$LINDY_TRIGGER_URL" \
  -H "Authorization: Bearer $LINDY_TRIGGER_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"event":"setup.verify","fixture":"synthetic"}'

Confirm that exactly one task is created and retain its task ID.

Step 4: Verify Rejection Without Authentication
bash
status="$(curl -sS -o /dev/null -w '%{http_code}' \
  -X POST "$LINDY_TRIGGER_URL" \
  -H "Content-Type: application/json" \
  -d '{"event":"setup.reject","fixture":"synthetic"}')"
case "$status" in
  2??)
    echo "unauthenticated request unexpectedly succeeded with HTTP $status" >&2
    exit 1
    ;;
  *) echo "unauthenticated request rejected with HTTP $status" ;;
esac

Any non-2xx response proves only transport rejection. Also inspect task history; do not continue if the unauthenticated request created a task.

Output

Deliver a sanitized setup receipt naming the target workspace and environment, the secret-manager references used for the trigger and callback credentials, the webhook host with its unique path redacted, and the results of one authorized and one unauthorized connectivity check. Never place credential values or a complete private webhook URL in the receipt.

Show full SKILL.md (203 more words)Show less

Examples

Store the webhook credential under a development-only secret reference, send a minimal test payload, and record the resulting task ID and HTTP status. Then repeat the request without authorization and confirm it is rejected. A setup that accepts both requests, uses a production credential in development, or requires copying a secret into source code is incomplete.

Error Handling

ErrorCauseSolution
Authorized request returns 401Trigger secret differs from caller secretReplace the caller value from the correct secret reference
Unauthenticated request creates a taskAuthentication is absent or misconfiguredStop testing and require bearer authentication on the trigger
No task is createdWrong URL, inactive agent, or trigger filterRe-copy the trigger URL and inspect the agent's task history
Request times outNetwork or Lindy service problemStop retries with real data and check the Lindy status page

Security Checklist

  • Complete trigger URL and bearer secret stored in a secret manager
  • Trigger and callback credentials are distinct
  • .env files ignored and limited to development fixtures
  • HTTPS used for trigger and callback traffic
  • Authorized request creates one task; unauthenticated request creates none

Resources

Next Steps

After successful auth, proceed to lindy-hello-world for your first AI agent.

© 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-install-auth of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lindy Install Auth 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 Install Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lindy Install Auth this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: NotesMIT
API Patternsdilolabs/nosia2131 repos~2.5kAutomated safety check: PassMIT
GitHub OAuth Nango IntegrationAgentWorkforce/relay8721 repos~3.4kAutomated safety check: PassApache-2.0
Pii DetectorgoSprinto/compliance-skills133—~1.6kAutomated safety check: PassMIT
Frappe Core APIImpertio-Studio/Frappe_Claude_Skill_Package189—~3.2kAutomated safety check: PassMIT
Workosusenotra/notra260—~6.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • API Patterns

    dilolabs/nosia

    Builds REST APIs using respondto blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy.

    213 GitHub starsUsed in 1 repo~2.5k tokens
    Backend & APIsAuto-check passed

  • GitHub OAuth Nango Integration

    AgentWorkforce/relay

    A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling

    872 GitHub starsUsed in 1 repo~3.4k tokens
    Backend & APIsAuto-check passed

  • Pii Detector

    goSprinto/compliance-skills

    Proactive PII add-on — augments the main response with PII guidance.

    133 GitHub stars~1.6k tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed

  • Frappe Core API

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.

    189 GitHub stars~3.2k tokensUpdated 24 days ago
    Backend & APIsAuto-check passed

  • Workos

    usenotra/notra

    A skill your agent uses when the user asks for a WorkOS docs URL, term, or dashboard field (Sign-in endpoint, initiateloginuri, Redirect URI, WORKOS env vars), or is implementing, debugging, or…

    260 GitHub stars~6.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Clerk Auth

    davila7/claude-code-templates

    Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.

    33k GitHub starsUsed in 5 repos~376 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

Categories

Questions about Lindy Install Auth

What does Lindy Install Auth do?

Set up a Lindy account and authenticated webhook trigger. An agent skill from jeremylongshore/tons-of-skills-marketplace. Lindy Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up a Lindy account and authenticated webhook trigger.

When should I use Lindy Install Auth?

Lindy Install Auth fits situations like: onboarding to Lindy; configuring bearer authentication for webhook triggers; connecting Lindy agents to your application; with phrases like install lindy.

How do I install Lindy Install Auth in Claude Code?

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

How do I install Lindy Install Auth in Codex?

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

Can I use Lindy Install Auth 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-install-auth -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-install-auth, .gemini/skills/lindy-install-auth, .github/skills/lindy-install-auth and .opencode/skills/lindy-install-auth in your project.

What does Lindy Install Auth need to run?

Going by SKILL.md and its folder, Lindy Install Auth needs the command-line tools its instructions call (curl) and credentials named LINDY_TRIGGER_SECRET. Our summary lists: A credential in LINDY_TRIGGER_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Lindy Install Auth access the network?

SKILL.md names 4 domains. In commands or code: public.lindy.ai; the agent is likely to contact it when it follows the instructions. As links in the text: docs.lindy.ai, lindy.ai and status.lindy.ai. This is read from the text; nothing was executed.

Is Lindy Install Auth safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Lindy Install Auth use?

Lindy Install Auth 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 Install Auth use?

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

What are the alternatives to Lindy Install Auth?

Skills that share tags, products or a category with Lindy Install Auth: API Patterns (dilolabs/nosia, 213 stars), GitHub OAuth Nango Integration (AgentWorkforce/relay, 872 stars), Pii Detector (goSprinto/compliance-skills, 133 stars) and Frappe Core API (Impertio-Studio/Frappe_Claude_Skill_Package, 189 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lindy Install Auth?

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.