Cs Checkpoint Version
ChenShuo2004/cs-skills
A skill your agent uses when the user asks to save the current repository version, create a rollback point, checkpoint dirty worktree changes, preserve staged/unstaged/untracked files before risky…
Configure Lindy AI across development, staging, and production environments.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-multi-env-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-multi-env-setup --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-multi-env-setup .claude/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .claude/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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-multi-env-setupType 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-multi-env-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-multi-env-setup --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-multi-env-setup .agents/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .agents/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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-multi-env-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-multi-env-setup --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-multi-env-setup .cursor/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .cursor/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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-multi-env-setup--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-multi-env-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-multi-env-setup --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-multi-env-setup .gemini/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .gemini/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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-multi-env-setupInstalls 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-multi-env-setup -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-multi-env-setup .github/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .github/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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-multi-env-setup -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-multi-env-setup --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-multi-env-setup .opencode/skills/lindy-multi-env-setup && 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-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-multi-env-setup into .opencode/skills/lindy-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-multi-env-setup", 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.
lindy-multi-env-setupConfigure Lindy AI across development, staging, and production environments.
Lindy Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Lindy AI across development, staging, and production environments. Use when setting up isolated workspaces, per-environment secrets, or environment-specific agent configurations. Trigger with phrases like "lindy environments", "lindy staging", "lindy dev prod", "lindy environment setup", "lindy workspace isolation".
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Git worktrees. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(aws:*)Bash(gcloud:*)Bash(vault:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghawsgcloudFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
public.lindy.aiAlso links to:
docs.lindy.aiFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LINDY_API_KEYLINDY_WEBHOOK_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Lindy Multi Env Setup loads about 1.9k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 347 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
| Development | `dev-workspace` | `.env.local` | Debug prompts, test integrations |# Development — .env.local (gitignored)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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 347 words, ~1,871 tokens.
.claude/skills/lindy-multi-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Isolate Lindy AI agents across development, staging, and production using separate workspaces, dedicated API keys, and environment-specific webhook configurations. Lindy agents live in workspaces — each environment should use its own workspace to prevent cross-environment data leakage.
| Environment | Workspace | API Key Source | Agent Config |
|---|---|---|---|
| Development | dev-workspace | .env.local | Debug prompts, test integrations |
| Staging | staging-workspace | CI/CD secrets | Production-like, test data |
| Production | prod-workspace | Secret manager | Hardened prompts, live integrations |
[company]-dev, [company]-staging, [company]-prod// config/lindy.ts — Environment-aware Lindy configuration
interface LindyConfig {
apiKey: string;
webhookUrl: string;
webhookSecret: string;
workspace: string;
model: string;
}
function getLindyConfig(): LindyConfig {
const env = process.env.NODE_ENV || 'development';
const configs: Record<string, LindyConfig> = {
development: {
apiKey: process.env.LINDY_API_KEY_DEV!,
webhookUrl: process.env.LINDY_WEBHOOK_URL_DEV!,
webhookSecret: process.env.LINDY_WEBHOOK_SECRET_DEV!,
workspace: 'dev',
model: 'gemini-flash', // Cheap model for dev
},
staging: {
apiKey: process.env.LINDY_API_KEY_STAGING!,
webhookUrl: process.env.LINDY_WEBHOOK_URL_STAGING!,
webhookSecret: process.env.LINDY_WEBHOOK_SECRET_STAGING!,
workspace: 'staging',
model: 'claude-sonnet', // Match prod model
},
production: {
apiKey: process.env.LINDY_API_KEY_PROD!,
webhookUrl: process.env.LINDY_WEBHOOK_URL_PROD!,
webhookSecret: process.env.LINDY_WEBHOOK_SECRET_PROD!,
workspace: 'production',
model: 'claude-sonnet',
},
};
const config = configs[env];
if (!config) throw new Error(`Unknown environment: ${env}`);
return config;
}
export const lindyConfig = getLindyConfig();// validate-env.ts — Fail fast if Lindy config is missing
import { z } from 'zod';
const LindyEnvSchema = z.object({
LINDY_API_KEY: z.string().min(1, 'LINDY_API_KEY required'),
LINDY_WEBHOOK_SECRET: z.string().min(1, 'LINDY_WEBHOOK_SECRET required'),
LINDY_WEBHOOK_URL: z.string().url('LINDY_WEBHOOK_URL must be valid URL'),
});
export function validateLindyEnv() {
const result = LindyEnvSchema.safeParse({
LINDY_API_KEY: process.env.LINDY_API_KEY,
LINDY_WEBHOOK_SECRET: process.env.LINDY_WEBHOOK_SECRET,
LINDY_WEBHOOK_URL: process.env.LINDY_WEBHOOK_URL,
});
if (!result.success) {
console.error('Lindy environment validation failed:');
result.error.issues.forEach(i => console.error(` - ${i.path}: ${i.message}`));
process.exit(1);
}
console.log('Lindy environment validated successfully');
}# Development — .env.local (gitignored)
LINDY_API_KEY=lnd_dev_xxxxxxxxxxxx
LINDY_WEBHOOK_URL=https://public.lindy.ai/api/v1/webhooks/dev-id
LINDY_WEBHOOK_SECRET=whsec_dev_xxxxxxxxxxxx
# Staging — CI/CD secrets (GitHub Actions)
gh secret set LINDY_API_KEY_STAGING --body "lnd_staging_xxxx"
gh secret set LINDY_WEBHOOK_SECRET_STAGING --body "whsec_staging_xxxx"
# Production — Cloud secret manager
# AWS
aws secretsmanager create-secret \
--name prod/lindy/api-key \
--secret-string "lnd_prod_xxxxxxxxxxxx"
# GCP
echo -n "lnd_prod_xxxxxxxxxxxx" | \
gcloud secrets create lindy-api-key-prod --data-file=-1. Build and test agent in dev workspace
2. Share agent as Template
3. Import template into staging workspace
4. Re-authorize integrations with staging accounts
5. Update webhook URLs to staging endpoints
6. Test with staging data for 24-48 hours
7. Repeat for production workspace
8. Update webhook URLs to production endpoints
9. Verify all integrations authorized with production accountsCritical: OAuth tokens, webhook URLs, and phone numbers do NOT transfer between workspaces. Each must be reconfigured per environment.
# .github/workflows/deploy.yml
jobs:
deploy-staging:
if: github.ref == 'refs/heads/develop'
environment: staging
env:
LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_STAGING }}
LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_STAGING }}
steps:
- run: npm run deploy:staging
- run: npm run test:lindy:smoke
deploy-prod:
if: github.ref == 'refs/heads/main'
environment: production
env:
LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_PROD }}
LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_PROD }}
steps:
- run: npm run deploy:prod
- run: npm run test:lindy:smokeProduce an environment register listing each workspace, public callback host, credential reference, integration owner, promotion source, last smoke-test result, and rollback target. Record only secret identifiers and redacted URL forms; never copy credential values, private webhook paths, customer data, or production connection exports between environments.
Promote a tested development template into staging, reconnect every integration with staging-only accounts, replace callback configuration, and record a synthetic smoke-test task ID. Before production promotion, prove the staging register contains no production secret reference. If that isolation check fails, stop promotion, rotate the exposed credential, and correct the environment map.
| Issue | Cause | Solution |
|---|---|---|
| Dev agent hits prod data | Shared workspace | Use separate workspaces per environment |
| Staging integration fails | OAuth token expired | Re-authorize with staging service accounts |
| Webhook URL mismatch | Dev URL in prod config | Validate webhook URLs at startup |
| Secret not found in CI | Missing environment secret | Add via gh secret set per environment |
Proceed to lindy-observability for monitoring and alerting.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/.curated/lindy-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Lindy Multi Env Setup 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 Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Notes | MIT | |
| Cs Checkpoint VersionChenShuo2004/cs-skills | 197 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Update NanoClaw Safelynanocoai/nanoclaw | 31k | — | ~2.9k | Automated safety check: Notes | MIT | |
| Archestra Dev Resource Cleanuparchestra-ai/archestra | 4.4k | — | ~305 | Automated safety check: Pass | Custom licence | |
| Wp Playgroundbonny/WordPress-Simple-History | 317 | — | ~1k | Automated safety check: Notes | None | |
| Ship ItBlackBeltTechnology/pi-agent-dashboard | 315 | — | ~5.4k | Automated safety check: Pass | MIT |
ChenShuo2004/cs-skills
A skill your agent uses when the user asks to save the current repository version, create a rollback point, checkpoint dirty worktree changes, preserve staged/unstaged/untracked files before risky…
nanocoai/nanoclaw
Updates a customized NanoClaw install from the official upstream in a staged worktree, with state snapshots, migration gates, health checks and automatic rollback.
archestra-ai/archestra
Reclaim unused Archestra development worktrees, local branches, processes, and OrbStack Kubernetes resources while preserving the active Tilt stack and unfinished work.
bonny/WordPress-Simple-History
A skill your agent uses for quick local testing with WordPress Playground CLI.
BlackBeltTechnology/pi-agent-dashboard
Worktree-side implementation orchestrator for an OpenSpec change.
yonatangross/orchestkit
Named HTTPS .localhost URLs with portless (v0.15.x). An agent skill from yonatangross/orchestkit.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Configure Lindy AI across development, staging, and production environments. Lindy Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Lindy AI across development, staging, and production environments.
Lindy Multi Env Setup fits situations like: setting up isolated workspaces; per-environment secrets; environment-specific agent configurations; with phrases like lindy environments.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-multi-env-setup -a claude-code`. Or copy the skill folder (skills/.curated/lindy-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-multi-env-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-multi-env-setup -a codex`. Or copy the skill folder (skills/.curated/lindy-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-multi-env-setup in your project. Codex loads it when a task matches its description.
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-multi-env-setup -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-multi-env-setup, .gemini/skills/lindy-multi-env-setup, .github/skills/lindy-multi-env-setup and .opencode/skills/lindy-multi-env-setup in your project.
Going by SKILL.md and its folder, Lindy Multi Env Setup needs the command-line tools its instructions call (gh, aws and gcloud) and credentials named LINDY_API_KEY and LINDY_WEBHOOK_SECRET. Our summary lists: A credential in LINDY_API_KEY; A credential in LINDY_WEBHOOK_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*). Compatibility (from SKILL.md): Designed for Claude Code.
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.
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.
Lindy Multi Env Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.5k 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 2.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Lindy Multi Env Setup: Cs Checkpoint Version (ChenShuo2004/cs-skills, 197 stars), Update NanoClaw Safely (nanocoai/nanoclaw, 31k stars), Archestra Dev Resource Cleanup (archestra-ai/archestra, 4.4k stars) and Wp Playground (bonny/WordPress-Simple-History, 317 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.