
Negentropy Lens
Apply a decay-versus-growth (entropy vs negentropy) lens when deciding whether to accept defaults or redesign personal and product systems.
Overview
Negentropy Lens is a journey-wide agent skill that frames decisions as choosing deliberate growth (negentropy) over default decay (entropy)—usable whenever a solo builder needs to reorient before committing.
Install
npx skills add https://github.com/bencium/bencium-marketplace --skill negentropy-lensWhat is this skill?
- Core frame: every system is in decay (entropy) or deliberate growth (negentropy)
- Personal narrative shows flipping default “slow decay” medical optimization into active negentropy habits
- Applies to life routines and by extension product and business system design
- Useful when agent or founder defaults optimize for maintenance instead of compounding upside
- Reflective essay format—no CLI; meant as decision vocabulary for the agent
Adoption & trust: 1.1k installs on skills.sh; 273 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You and your agent keep accepting “good enough” maintenance paths that extend runway but never compound capability or health.
Who is it for?
Reflective solo builders who want a shared metaphor with their agent when prioritizing roadmaps, habits, or turnaround efforts.
Skip if: Builders who need step-by-step technical runbooks, measurable KPI templates, or security exploit guidance.
When should I use this skill?
Before accepting expert or agent defaults on health, product, or ops plans, when you need to classify the path as decay optimization or deliberate negentropy growth.
What do I get? / Deliverables
You name whether a plan optimizes decay or growth and steer specs, habits, and roadmaps toward negentropy-aligned actions.
- Clear decay-vs-growth classification for the decision at hand
- Reframed priorities or spec bullets aligned with negentropy
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
You compare two niches and ask whether each path compounds skills or only slows obsolescence.
A thin MVP scope would ship fast but entrenches decay—negentropy lens prompts a growth-oriented prototype bet.
Backlog grooming defaults to bug fixes; you reclassify items as entropy maintenance versus negentropy investments.
Content calendar is reactive; you redesign it as a compounding distribution system.
On-call patches repeat weekly—you ask whether to invest in removal of the decay source.
How it compares
Mindset and planning lens—not a checklist generator, integration, or analytics skill.
Common Questions / FAQ
Who is negentropy-lens for?
Solo and indie builders who want a simple growth-versus-decay frame for personal and product decisions inside agent chats.
When should I use negentropy-lens?
Use it in Idea when choosing what to build; in Validate when deciding if a landing page merely maintains interest; in Build when debating refactor versus feature entropy; in Launch and Grow when distribution feels maintenance-only; and in Operate when incident response devolves i
Is negentropy-lens safe to install?
It is narrative guidance only—review the Security Audits panel on this page; do not treat essay anecdotes as medical or legal advice.
SKILL.md
READMESKILL.md - Negentropy Lens
# Flipping the Switch: From Decay to Growth ## How a health crisis taught me a system view that now governs my life and work It was winter 2021. I was 49 years old. Six independent cardiologists diagnosed an atherosclerosis. The options were medications that would damage my liver (collateral I would need to accept) and surgery (13 stents and bypasses, but chances were I would not wake up). The alternative was death within 2 years. "And what's the good news?" I asked. My cardiologists' collective verdict had an effect on me which I did not anticipate: I wasn't scared of dying, just mad as a hornet. This was the energy I needed to build the person I always desired to be, but never even tried: Strong and healthy. Then I started doing things that strong and healthy people do: Weightlifting, clean diet, rest, repeat. Fast forward 2026, I have no symptoms, I take no medication, no surgery. I do routine cardiology checks. It's just a routine that confirms my health. Only later did I find the vocabulary for what had actually happened in that moment of rage. **Every system has two states: decay (entropy) or growth (negentropy).** When doctors recommend statins and stents, it's perfectly aligned assuming decay of my cardiovascular system. They optimize to extend my life, or looking from the systemic perspective, slow down the decay. In my state of being mad as a hornet, I flipped the switch. Instead of accepting my body in entropy, I declared negentropy. It was exactly that moment of declaring in which direction I wanted my physical system of blood vessels, muscles, and neurons to pivot: downward, or upward spiral. The thing about flipping that switch once, when your life is genuinely at stake, is that it teaches you something you can't learn from a book. It teaches you humility, discipline, rigor, and awareness. And once you have that vocabulary, you start seeing these two states everywhere. Including in my own field. ## How an observation about knowledge changed the trajectory of my career I have been in data and AI literacy consulting for nearly a decade. During that time, I made an observation that changed everything: One particular domain of knowledge stands out. **Tacit knowledge.** We all know it exists. We call it tribal knowledge, institutional memory, "the way things really get done around here." It often overrides explicit knowledge: Standard Operating Procedures, employee handbooks, product blueprints, and company policies. Everyone nods when you say this. But here is what's fascinating: we make assumptions about tacit knowledge constantly, yet we have nearly zero evidence for how it manifests, how it impacts how a company operates, or how it interacts with explicit knowledge. Most companies and their vendors act under the presumption that tacit knowledge lives in conversations, in emails, in Slack threads. This is unstructured knowledge, but is it tacit knowledge? Do conversations on Slack capture how things "really" get done? And even if they do, how do you ingest large volumes of that data and filter signal from noise? This is a huge technical challenge and a data privacy challenge. It might feel to employees as if the company is spying on them. The more I dug into this, the clearer it became: we don't have a clear definition of what tacit knowledge actually is, and we have no methodology to analyze it, let alone put it to work. This presents a challenge for two reasons. First, as companies move into Agentic AI, explicit knowledge alone is insufficient. The systems need to reflect how the organization actually operates, not just what the handbook says. Second, if we fail to understand tacit knowledge, we risk increasing the entropic drive. The motivational posters scream innovation and progress, but the tacit undertone is: "not invented here." This was not a gap in the market. This was an entire category that did not exist yet. And it pulled me in. I started hunting for it. Designing science exp