Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Production readiness checklist for Lindy AI agent deployments.
Install Lindy Prod Checklist
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-prod-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-prod-checklist --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-prod-checklist .claude/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .claude/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklistType 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-prod-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-prod-checklist --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-prod-checklist .agents/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .agents/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-prod-checklist --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-prod-checklist .cursor/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .cursor/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklist--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-prod-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-prod-checklist --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-prod-checklist .gemini/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .gemini/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklistInstalls 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-prod-checklist -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-prod-checklist .github/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .github/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklist -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-prod-checklist --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-prod-checklist .opencode/skills/lindy-prod-checklist && 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-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-prod-checklist into .opencode/skills/lindy-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-prod-checklist", 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-prod-checklist- GitHub stars
- 2.8k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 842 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Production readiness checklist for Lindy AI agent deployments.
- Works in 6 steps: Open an evidence record → Verify the two authentication boundaries → Prove a real synthetic task is created → …
- Preparing agents for production
- SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
- Calls curl; reaches public.lindy.ai; needs LINDY_TRIGGER_SECRET and LINDY_CALLBACK_SECRET
What it does
Lindy Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Production readiness checklist for Lindy AI agent deployments. Use when preparing agents for production, auditing live agents, or validating go-live readiness. Trigger with phrases like "lindy production", "lindy prod ready", "lindy go live", "lindy deployment checklist".
Its SKILL.md is about 2.1k 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: Compatible with AI coding agents that can read Markdown; optional verification probes require a shell with curl
It sits in DevOps & Cloud, covering Deployment. 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
- Preparing agents for production
- Auditing live agents
- Validating go-live readiness
- With phrases like lindy production
Example prompts
- “lindy production”
- “lindy prod ready”
- “lindy go live”
- “/lindy-prod-checklist”
Requirements
- A credential in LINDY_CALLBACK_SECRET
- A credential in LINDY_TRIGGER_SECRET
- Compatibility (from SKILL.md): Compatible with AI coding agents that can read Markdown; optional verification probes require a shell with curl
- 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:
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
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_SECRETLINDY_CALLBACK_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Compatible with AI coding agents that can read Markdown; optional verification probes require a shell with curl
From compatibility in the SKILL.md frontmatter.
Context cost
Lindy Prod Checklist loads about 2.1k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 842 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). 842 words, ~2,075 tokens.
Download SKILL.mdSave it as
.claude/skills/lindy-prod-checklist/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- lindy-prod-checklist
- description
- Production readiness checklist for Lindy AI agent deployments. Use when preparing agents for production, auditing live agents, or validating go-live readiness. Trigger with phrases like "lindy production", "lindy prod ready", "lindy go live", "lindy deployment checklist".
- allowed-tools
- Read, Write, Edit, Bash(curl:*)
- compatibility
- Compatible with AI coding agents that can read Markdown; optional verification probes require a shell with curl
- version
- 1.20.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, lindy, deployment, audit
Lindy Production Checklist
Overview
Create an evidence-backed go/no-go decision for a Lindy agent. Treat the Lindy dashboard and the organization's current contract, workspace configuration, and runbooks as the authorities. Do not infer product entitlements, prices, quotas, security features, support terms, or compliance commitments from this skill.
Use Read to inspect configuration and evidence, Write or Edit to
maintain the readiness record, and Bash(curl:*) only for an approved synthetic
webhook probe. Never place a secret in the record or command output.
Prerequisites
- Access to the target Lindy workspace and its Tasks view.
- An exported webhook-trigger URL and its nonempty Lindy-generated trigger secret.
- A separate, nonempty callback secret when a Lindy HTTP Request action calls your application. Never reuse the trigger secret as the callback secret.
- A synthetic test case with no production personal or confidential data and a unique correlation ID.
- Access to current contract/workspace evidence for any claim about pricing, credits, thresholds, secret rotation, SSO, SCIM, support, or a BAA.
- A durable queue when callback work cannot be completed safely within the receiver's synchronous response window.
Instructions
1. Open an evidence record
Record the workspace, agent, reviewer, date, release identifier, and links to
artifacts. Give every check one of three verdicts: PASS, FAIL, or
NOT VERIFIED. A missing entitlement or policy document is NOT VERIFIED, not
an assumed pass.
2. Verify the two authentication boundaries
For an application calling a Lindy webhook trigger:
- Confirm the URL uses HTTPS and its hostname is exactly
public.lindy.ai. - Confirm the authorization value is the secret generated for that trigger.
- Keep the URL and trigger secret in an approved secret manager; redact both from screenshots, logs, tickets, and readiness reports.
For a Lindy HTTP Request action calling your application:
- Generate and store an independent
LINDY_CALLBACK_SECRETin your application. - Configure the action to send
Authorization: Bearer <callback-secret>. - Reject a missing or mismatched value before accepting or acting on the body.
- Apply a bounded schema and payload-size limit before enqueueing work.
Lindy documents the trigger-side generated secret and configurable headers for HTTP Request actions. It does not make one secret interchangeable across both directions.
3. Prove a real synthetic task is created
Run a probe only after the URL and secret checks pass:
set -euo pipefail
: "${LINDY_TRIGGER_URL:?LINDY_TRIGGER_URL is required}"
: "${LINDY_TRIGGER_SECRET:?LINDY_TRIGGER_SECRET is required}"
case "$LINDY_TRIGGER_URL" in
https://public.lindy.ai/api/v1/webhooks/*) ;;
*) echo "Refusing to send the trigger secret to a non-Lindy host" >&2; exit 1 ;;
esac
CORRELATION_ID="prod-readiness-REPLACE_WITH_UNIQUE_ID"
HTTP_STATUS=$(curl --silent --show-error --output /dev/null \
--write-out '%{http_code}' --max-time 30 \
--request POST "$LINDY_TRIGGER_URL" \
--header "Authorization: Bearer $LINDY_TRIGGER_SECRET" \
--header 'Content-Type: application/json' \
--data "{\"correlationId\":\"$CORRELATION_ID\",\"kind\":\"readiness_probe\"}")
case "$HTTP_STATUS" in
2??) echo "Transport accepted; verify the task separately: $CORRELATION_ID" ;;
*) echo "Trigger rejected with HTTP $HTTP_STATUS" >&2; exit 1 ;;
esacThe 2xx response proves only transport acceptance. Find a task with the unique correlation ID in Lindy's Tasks view, then verify its expected actions and final state. If authentication is intentionally broken, require a non-2xx response and also verify that no task was created. Do not capture the response body in the evidence record.
4. Qualify callback durability
A callback receiver passes only if it authenticates first, validates a bounded schema, and persists accepted work to a durable queue before returning success. An in-memory promise, timer, or process-local queue is not durable enqueue. Test:
- valid callback -> one durable job and a 2xx response;
- wrong or missing callback secret -> non-2xx and no job;
- malformed or oversized payload -> non-2xx and no job;
- duplicate correlation ID -> no duplicate side effect; and
- worker interruption after enqueue -> the job remains recoverable.
Show full SKILL.md (335 more words)Show less
5. Complete the operational gate
- Exercise the happy path and each material failure path with synthetic data.
- Confirm OAuth integrations and target resources using the workspace UI.
- Establish an observed latency and task-success baseline; choose alert thresholds from the organization's risk appetite and actual workload.
- Link the incident runbook, owner, escalation path, rollback or disable procedure, data-retention decision, and monitoring evidence.
- Verify pricing, credit budget, secret-rotation cadence, SSO, SCIM, BAA, and other compliance statements only from current contract or workspace evidence. Mark unavailable or inapplicable features explicitly.
6. Make the decision
Block launch for any failed authentication boundary, unverified task creation, unauthenticated callback, nondurable accepted work, missing rollback path, or unresolved high-severity finding. The accountable owner must accept any remaining lower-severity risk in the evidence record.
Output
Produce a readiness record containing:
- release, workspace, agent, owner, reviewer, and review timestamp;
- per-check
PASS/FAIL/NOT VERIFIEDverdicts with evidence links; - synthetic correlation IDs and task identifiers, without payloads or secrets;
- callback rejection, deduplication, and durable-enqueue test results;
- contract-dependent claims with their current source and applicability;
- unresolved risks, accountable owners, and due dates; and
- a final
GOorNO-GOdecision with the approving owner.
Examples
Minimal go/no-go summary
# Release r42 readiness
- Trigger auth: PASS -- synthetic task task-123 matched correlation prod-readiness-42
- Callback auth: PASS -- wrong secret rejected; zero jobs created
- Durable enqueue: PASS -- job survived worker restart and completed once
- SSO/SCIM: NOT VERIFIED -- not required for this release; contract owner recorded
- Rollback: PASS -- agent disable procedure tested by operator
- Open risks: none above accepted severity
Decision: GO
Approver: release ownerCorrect no-go outcome
If the webhook returns 2xx but no corresponding task appears, record
Task creation: NOT VERIFIED and choose NO-GO. Do not substitute a public-host
reachability check for task-level proof.
Error Handling
| Failure | Required response |
|---|---|
Trigger URL is not HTTPS on exact public.lindy.ai host | Do not attach the trigger secret; block the probe |
| Missing or reused secret | Generate distinct secrets, store them correctly, and repeat the tests |
| 2xx without a matching task | Treat as unverified; inspect the Tasks view and agent trigger configuration |
| Rejected request creates a task | Block launch and escalate the authentication failure |
| Callback acknowledges before durable enqueue | Change the receiver contract and repeat interruption testing |
| Contract-dependent feature cannot be proven | Mark NOT VERIFIED; do not advertise or depend on it |
Resources
© 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-prod-checklist of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/implementation-guide.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Lindy Prod Checklist 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 Prod Checklist this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
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 Prod Checklist
What does Lindy Prod Checklist do?
Production readiness checklist for Lindy AI agent deployments. Lindy Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Production readiness checklist for Lindy AI agent deployments.
When should I use Lindy Prod Checklist?
Lindy Prod Checklist fits situations like: preparing agents for production; auditing live agents; validating go-live readiness; with phrases like lindy production.
How do I install Lindy Prod Checklist in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-prod-checklist -a claude-code`. Or copy the skill folder (skills/.curated/lindy-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-prod-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Lindy Prod Checklist in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-prod-checklist -a codex`. Or copy the skill folder (skills/.curated/lindy-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-prod-checklist in your project. Codex loads it when a task matches its description.
Can I use Lindy Prod Checklist 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-prod-checklist -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-prod-checklist, .gemini/skills/lindy-prod-checklist, .github/skills/lindy-prod-checklist and .opencode/skills/lindy-prod-checklist in your project.
What does Lindy Prod Checklist need to run?
Going by SKILL.md and its folder, Lindy Prod Checklist needs the command-line tools its instructions call (curl) and credentials named LINDY_TRIGGER_SECRET and LINDY_CALLBACK_SECRET. Our summary lists: A credential in LINDY_CALLBACK_SECRET; A credential in LINDY_TRIGGER_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Compatible with AI coding agents that can read Markdown; optional verification probes require a shell with curl.
Does Lindy Prod Checklist access the network?
SKILL.md names 2 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. This is read from the text; nothing was executed.
Is Lindy Prod Checklist 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 Prod Checklist use?
Lindy Prod Checklist 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 Prod Checklist use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Lindy Prod Checklist?
Skills that share tags, products or a category with Lindy Prod Checklist: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Mirrord Operator (metalbear-co/mirrord, 5.4k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lindy Prod Checklist?
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.