Skip to content
Agentmart
Submit a tool

thinking-lindy-effect

Use when longevity of a non-perishable option matters.

Skill by tjboudreaux

IndexedMIT★ 1,668
Write a review

Chalk Labs

Need help deploying thinking-lindy-effect?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tjboudreaux-thinking-lindy-effect

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/thinking-lindy-effect

What's inside

Skill name
thinking-lindy-effect
Description
Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.
License
MIT
Instructions
46 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Lindy Effect

For non-perishable ideas, technologies, and practices, expected remaining life scales with current survival age. Prefer proven survivors unless the new option clears a burden of proof or the domain has drifted.

## When to Use

- Choosing languages, frameworks, databases, protocols, patterns, or dependencies where long-term survival matters.
- Skill or architecture bets whose value depends on lasting relevance.
- Ranking options when ages differ materially and the choice outlives a short experiment.

## When NOT to Use

- Perishable targets: specific SaaS vendors, hardware, fashion, or products that can shut down regardless of concept age.
- Active paradigm discontinuity where age in the old regime is weak evidence.
- Throwaway work where longevity is irrelevant — optimize for fit and speed.
- Treating "older" as "optimal for a new requirement"; survival predicts further survival, not best fit.

## Procedure

1. **Confirm non-perishable scope.** Concept/tech/practice continues; vendor/device → score fit/risk only and stop.
2. **Record survival age.** First significant production use and current age (ecosystem-relative if the ecosystem is young).
3. **Form the Lindy prior.** Expected remaining life ≈ current age; mark confidence from age and continued active use.
4. **Run domain-drift checks.** Problem class changed? Paradigm shift invalidating old assumptions? New option uniquely closes a real present gap?
5. **Assign burden of proof.** Default to the older adequate option. Accept newer only for a stated necessary advantage the Lindy option cannot meet at acceptable cost.
6. **Decide with residual risk.** Pick primary; note impact if the prior is wrong and any fallback.

**Stop condition:** Primary chosen with age prior, drift check, and why new did or did not meet burden of proof.

## Output

```text
Options: <name, age, Lindy prior>
Drift: stable | discontinuous — <note>
Burden: on new | waived because <gap>
Decision: <primary>
Rejected: <one line each>
If Lindy wrong: <impact + fallback>
```

## Verification

- Falsify if age was used without non-perishable scope, or a paradigm shift was ignored.
- Falsify if a new option was rejected solely for youth despite a documented necessary gap.
- Over-application guard: skip throwaway prototypes and perishable vendor bets where fit and exit cost dominate.

From tjboudreaux/cc-thinking-skills, MIT.

More from tjboudreaux/cc-thinking-skills

Signals

Stars
1,668
Forks
185
Open issues
2
Last commit (this folder)
Jul 17, 2026 (3 months ago)
Last release
Aug 4, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tjboudreaux

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get thinking-lindy-effect running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying thinking-lindy-effect?

CallGet help
Cite this page

thinking-lindy-effect skill. Agent Mart. https://agentmart.dev/skills/tjboudreaux-thinking-lindy-effect (last updated 2026-10-24)