Knowledge Search
dataelement/bisheng
Search the user's knowledge bases and knowledge spaces (企业知识库检索).
Build and configure multi-step Lindy AI agent workflows. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Install Lindy Core Workflow A
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-a -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-core-workflow-a --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-core-workflow-a .claude/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .claude/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-aType 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-core-workflow-a -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-core-workflow-a --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-core-workflow-a .agents/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .agents/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-a -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-core-workflow-a --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-core-workflow-a .cursor/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .cursor/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-a--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-core-workflow-a -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-core-workflow-a --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-core-workflow-a .gemini/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .gemini/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-aInstalls 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-core-workflow-a -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-core-workflow-a .github/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .github/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-a -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-core-workflow-a --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-core-workflow-a .opencode/skills/lindy-core-workflow-a && 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-core-workflow-a" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-core-workflow-a into .opencode/skills/lindy-core-workflow-a/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-core-workflow-a", 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-core-workflow-a- GitHub stars
- 2.8k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 673 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build and configure multi-step Lindy AI agent workflows. An agent skill from jeremylongshore/tons-of-skills-marketplace.
- Works in 7 steps: Define Agent Specification → Create the Agent → Configure the Prompt → …
- Creating agents with triggers
- SKILL.md covers Overview, Prerequisites, Instructions and Trigger Types Reference, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lindy Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build and configure multi-step Lindy AI agent workflows. Use when creating agents with triggers, actions, conditions, knowledge bases, or agent steps. Trigger with phrases like "create lindy agent", "build lindy agent", "lindy agent workflow", "configure lindy agent", "lindy workflow".
Its SKILL.md is about 1.7k 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 Knowledge Management, covering Knowledge bases. 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
- Creating agents with triggers
- Knowledge bases
- With phrases like create lindy agent
- Build lindy agent
Example prompts
- “create lindy agent”
- “build lindy agent”
- “lindy agent workflow”
- “/lindy-core-workflow-a”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)
Workflow steps
7 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
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):
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 A loads about 1.7k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 673 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). 673 words, ~1,738 tokens.
Download SKILL.mdSave it as
.claude/skills/lindy-core-workflow-a/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-a
- description
- Build and configure multi-step Lindy AI agent workflows. Use when creating agents with triggers, actions, conditions, knowledge bases, or agent steps. Trigger with phrases like "create lindy agent", "build lindy agent", "lindy agent workflow", "configure lindy agent", "lindy workflow".
- 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 A: Agent Creation
Overview
Complete workflow for creating, configuring, and testing Lindy AI agents. Agents consist of four components: Prompt (behavioral instructions), Model (AI engine), Skills (available actions), and Exit Conditions (completion criteria).
Prerequisites
- Lindy account at
- Use case defined (support bot, email triage, data processor, etc.)
- Required integrations identified (Slack, Gmail, Sheets, etc.)
Instructions
Step 1: Define Agent Specification
Before building, document:
- Purpose: What the agent does (one sentence)
- Trigger: What wakes it up (webhook, email, schedule, chat, etc.)
- Actions: What it does (send email, update sheet, post to Slack, etc.)
- Model: GPT-4 (smart, expensive), Claude Sonnet (balanced), Gemini Flash (fast, cheap)
Step 2: Create the Agent
Option A — Natural Language (recommended):
Click New Agent at
Describe your agent in plain English:
When a customer emails support@company.com, classify the email as billing/technical/general, draft a response using our knowledge base, and post the classification to #support-triage in SlackAgent Builder auto-generates trigger + action nodes
Option B — Manual Build:
- Click New Agent > Start from scratch
- Add trigger: Click "+" > Select trigger type
- Add actions: Click "+" > Search for action
- Connect nodes by dragging arrows between steps
Step 3: Configure the Prompt
Open Settings > Prompt. Structure it with clear sections:
## Identity
You are a customer support classifier and responder for [Company].
## Instructions
1. Read the incoming email carefully
2. Classify into: billing, technical, or general
3. Search the knowledge base for relevant answers
4. Draft a professional response using the KB results
5. If no KB match found, escalate to human
## Constraints
- Never promise refunds or credits without human approval
- Keep responses under 200 words
- Always include ticket reference numberPrompt best practices (from Lindy docs):
- Use action-oriented language (imperatives)
- Break complex logic into numbered steps
- Include few-shot examples for consistent formatting
- Add constraints to prevent unwanted behavior
Step 4: Add Conditions (Branching Logic)
- Click "+" > Condition
- Write natural language condition:
"Go down this path if the email is about billing" - Add multiple branches for different classifications
- Enable "Force the agent to select a branch" for deterministic routing
Step 5: Configure Actions
For each action, set field modes:
Auto mode — Agent infers the value from all previous step data:
Best for: predictable mappings where field names alignAI Prompt mode — Give natural language instructions:
Summarize the email in 2 sentences, then include the classification.
Reference: {{email_received.body}}Set Manually mode — Exact value, no AI:
Channel: #support-triageStep 6: Add Knowledge Base (Optional)
- Go to Settings > Knowledge Base
- Add sources: PDF, DOCX, Google Drive, Notion, websites
- Configure search:
- Max Results: 4 (default) to 10
- Search Fuzziness: 0 (keyword) to 100 (semantic, recommended)
- Agent auto-searches KB when relevant to the task
Step 7: Test the Agent
- Use the Test button in the workflow editor
- Provide sample input matching your trigger type
- Review each step's output in the task detail view
- Iterate on prompt and action configuration
Show full SKILL.md (300 more words)Show less
Trigger Types Reference
| Trigger | Use Case | Configuration |
|---|---|---|
| Webhook Received | External API calls | URL + secret key |
| Email Received | Inbox automation | Gmail/Outlook + label filters |
| Schedule | Recurring tasks | Cron-style: daily, weekly, custom |
| Chat Message | Interactive bot | Lindy Chat or Embed widget |
| Slack Message | Team automation | Channel + keyword filters |
| Agent Message | Multi-agent delegation | Receives from other Lindies |
| Calendar Event | Meeting automation | Minutes offset (-30 = 30 min before) |
| Form Submission | Lead capture | Connected form integration |
Action Categories
| Category | Actions |
|---|---|
| Send Email, Draft Reply, Search Inbox, Add Label | |
| Slack | Send Channel Message, Send DM, Thread Reply |
| Sheets | Update Spreadsheet, Get Document |
| Calendar | Create Event, Reschedule, Cancel |
| Knowledge | Search Knowledge Base, Resync KB |
| Code | Run Code (Python/JS in E2B sandbox) |
| Web | HTTP Request, Web Search, Website Crawler |
| Memory | Read/Create/Update/Delete Memory |
| Phone | Make Call, Transfer Call, End Call |
| Agent | Agent Send Message (delegation) |
Error Handling
| Error | Cause | Solution |
|---|---|---|
| "No trigger configured" | Agent has no trigger | Add at least one trigger node |
| Action fails silently | Wrong field mode | Switch to AI Prompt or Set Manually |
| KB returns no results | Fuzziness too low | Increase to 100 (semantic search) |
| Condition always picks same path | Ambiguous prompt | Make conditions more specific |
| Agent loops indefinitely | No exit condition | Add measurable exit criteria |
Output
Produce an agent specification with a named trigger, explicit identity and constraints, ordered actions, safe failure behavior, and one acceptance fixture that proves the agent performs the intended task without unintended side work.
Examples
Create a lead-routing agent triggered by a tagged form submission. It validates the required fields, assigns the record only when the stated routing rule matches, and otherwise records a review task; a fixture for each branch proves the constraints are applied before any connected-system action.
Resources
Next Steps
Proceed to lindy-core-workflow-b for triggers, automation, and multi-agent delegation.
© 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-a 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 A 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 Core Workflow A this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Knowledge Searchdataelement/bisheng | 12k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence | |
| Xhs Virtual Productchenjin-cmd/xhs-virtual-product | 729 | — | ~862 | Automated safety check: Pass | MIT | |
| OpenkbVectifyAI/OpenKB | 4.8k | 1 repos | ~2k | Automated safety check: Warn | Apache-2.0 |
Similar skills
Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Find And Cite
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
Xhs Virtual Product
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
Openkb
VectifyAI/OpenKB
A skill your agent uses when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an…
Learn From Materials
dmoshehun-prog/learn-from-materials
Turns books, PDFs, slides and web pages into a source-grounded knowledge base and an interactive learning page in English or Chinese, with quizzes, relationship maps and reusable methodology notes.
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 Core Workflow A
What does Lindy Core Workflow A do?
Build and configure multi-step Lindy AI agent workflows. An agent skill from jeremylongshore/tons-of-skills-marketplace. Lindy Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build and configure multi-step Lindy AI agent workflows.
When should I use Lindy Core Workflow A?
Lindy Core Workflow A fits situations like: creating agents with triggers; knowledge bases; with phrases like create lindy agent; build lindy agent.
How do I install Lindy Core Workflow A in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-a -a claude-code`. Or copy the skill folder (skills/.curated/lindy-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-core-workflow-a in your project. Claude Code loads it when a task matches its description.
How do I install Lindy Core Workflow A in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-a -a codex`. Or copy the skill folder (skills/.curated/lindy-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-core-workflow-a in your project. Codex loads it when a task matches its description.
Can I use Lindy Core Workflow A 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-a -a cursor` (or -a -a, -a or -a for the others). To copy it by hand, put the folder in .cursor/skills/lindy-core-workflow-a, .gemini/skills/lindy-core-workflow-a, .github/skills/lindy-core-workflow-a and .opencode/skills/lindy-core-workflow-a in your project.
What does Lindy Core Workflow A need to run?
SKILL.md names no scripts, command-line tools or credentials: Lindy Core Workflow A 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 A access the network?
SKILL.md names 1 domain. As links in the text: docs.lindy.ai. This is read from the text; nothing was executed.
Is Lindy Core Workflow A 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 A use?
Lindy Core Workflow A 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 A use?
About 1.7k tokens (SKILL.md is roughly 7k 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 791 tokens, read only when the agent opens those files.
What are the alternatives to Lindy Core Workflow A?
Skills that share tags, products or a category with Lindy Core Workflow A: Knowledge Search (dataelement/bisheng, 12k stars), Capture Conversation (outline/outline, 41k stars), Find And Cite (outline/outline, 41k stars) and Xhs Virtual Product (chenjin-cmd/xhs-virtual-product, 729 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 A?
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.