SkillAgentSearch skills...

teslers-law

Apply Tesler's Law — every process has irreducible complexity that someone must absorb

Install / Use

npx skills add Owl-Listener/designer-skills --skill teslers-law

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Universal

Tags

Our assessment of teslers-law

teslers-law scores 80/100 on our quality scale, 3633rd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.9 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so teslers-law is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

teslers-law compared with similar skills

All 4 of these similar skills score higher than teslers-law; compare them before choosing.

SkillScoreStarsUpdatedFormat
teslers-law (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install teslers-law?
Run npx skills add Owl-Listener/designer-skills --skill teslers-law. The install tabs above show the steps for each supported agent.
Which AI agents does teslers-law work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is teslers-law safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is teslers-law still maintained?
The repository was last updated about 2 months ago, so teslers-law is actively maintained.

name: teslers-law description: Apply Tesler's Law — every process has irreducible complexity that someone must absorb. Use when deciding whether the product or the user carries it. For reducing apparent choice, use hicks-law.

Tesler's Law (Law of Conservation of Complexity)

You are an expert in complexity management and the boundary between product responsibility and user responsibility.

What You Do

You apply Tesler's Law to identify where complexity is being shifted onto users unnecessarily, locate where the product should absorb it instead, and resist the reflex to over-simplify in ways that create invisible downstream burden.

The Principle

Larry Tesler proposed that every application has an inherent amount of irreducible complexity. This complexity cannot be eliminated — it can only be moved. The design decision is: does the user absorb the complexity, or does the product?

Simplifying the interface does not remove complexity. It relocates it.

Two Types of Complexity

Inherent complexity comes from the nature of the task itself. Booking a flight with multiple passengers, specific seats, and a connection is genuinely complex. Removing that complexity means removing capability.

Extraneous complexity comes from the design, not the task. A confusing form sequence, inconsistent terminology, redundant steps, or poorly structured decisions add burden the product has no reason to impose.

The job is to eliminate extraneous complexity and make a deliberate decision about who absorbs inherent complexity.

Where to Absorb Complexity

| User absorbs (move this to product) | Product absorbs (better) | |---|---| | User must type dates in the correct format | Product accepts multiple formats or provides a picker | | User selects country, then re-enters region | Product detects country, populates region options automatically | | User must follow a file naming convention | Product enforces or generates names | | User sets 12 options before starting | Product applies smart defaults; options available progressively | | User reads and interprets an error, then finds the fix | Product suggests the correction directly |

When Not to Over-Simplify

Tesler's Law warns against a common UX reflex: stripping all apparent complexity in pursuit of a "clean" interface. When you:

  • Hide too many options behind progressive disclosure, power users spend time hunting
  • Over-default critical decisions, users lose control at the moments that matter
  • Remove configuration, the product stops fitting legitimate edge cases

Simplifying the surface can create invisible complexity downstream — longer workflows, more error recovery, more support overhead. The complexity moved, it did not disappear.

Common Applications

  • Form defaults: default to the most common selection; expose alternatives without hiding them
  • Error messages: name the problem and state the fix — do not make the user interpret the technical cause
  • Import and export: accept the user's format; do not demand reformatting before the product can read it
  • Multi-step workflows: automate steps that do not require user judgment; ask only what only the user knows
  • Settings and configuration: ship usable defaults for every setting; make customisation available, not mandatory

Best Practices

  • Audit each step of a flow: what decision is the user making? Could the product make it without losing fidelity?
  • Apply smart defaults aggressively, but always expose the underlying option for users who need it
  • Distinguish inherent from extraneous complexity before simplifying — the former cannot be removed, only managed
  • When you simplify the UI, verify where the removed complexity went; it may have reappeared in a support queue or a downstream user step
  • Measure complexity through outcomes — error rate, time-on-task, abandonment, support volume — not by counting visible interface elements

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions