CtrlK
BlogDocsLog inGet started
Tessl Logo

negentropy-lens

A decision-support framework that evaluates systems, architectures, and strategies through the entropy (decay) vs negentropy (growth) lens, while surfacing tacit knowledge gaps. Use this skill whenever the user is making architecture decisions, evaluating system designs, reviewing technical approaches, choosing between options, auditing existing systems, or planning strategies. Also trigger when the user explicitly asks to "apply the negentropy lens", mentions "entropy", "negentropy", "tacit knowledge", "knowledge engine", or "flip the switch". Nudge activation when you detect the user is at a decision point — even if they haven't asked for this lens — by briefly noting the entropic/negentropic dimension before proceeding.

73

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable framework with a clear 5-phase workflow and disciplined use of a single external reference. Minor tightening of conceptual restatement would push conciseness to the top level.

Suggestions

Trim restated concepts in 'Core Principle' and 'Term Definitions' — the parenthetical definitions already convey the ideas without the surrounding exposition.

Add a concrete output template or example artifact for at least the 'Architecture reviews' output-formatting case to lift actionability from concrete-guidance to copy-paste-ready.

Consider moving the Anti-Patterns list or the Phase detail into a reference file if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is largely substantive framework content Claude would not inherently know, but sections like the Core Principle and Term Definitions restate concepts with some padding that could be tightened, keeping it just below a 5.

4 / 5

Actionability

Concrete, specific guidance throughout (numbered phases, explicit probing questions, named anti-patterns); as an instruction-only skill the absence of code is not penalized, but a few phases could specify more concrete output artifacts.

4 / 5

Workflow Clarity

A clearly sequenced 5-phase process ('Map → Diagnose → Surface Tacit Layer → Evaluate → Challenge') with an organizing principle stated up front; as an analysis skill it involves no destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Well-organized sections with a single clearly signaled one-level-deep reference ('references/origin-essay.md', verified to exist) used appropriately for conceptual origins while the operational framework stays inline.

5 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person voice, explicit what-and-when, rich natural trigger terms, and a distinctive conceptual niche. It is nearly comprehensive, with only marginal room to make the listed capabilities more concrete.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions ('evaluating system designs, reviewing technical approaches, choosing between options, auditing existing systems'), but the actions remain somewhat abstract compared to fully concrete capability verbs, placing it just below a 5.

4 / 5

Completeness

Clearly answers 'what' ('a decision-support framework that evaluates systems, architectures, and strategies') and 'when' via an explicit 'Use this skill whenever…' clause with concrete trigger conditions and nudge-activation guidance.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including the explicit quoted invocation ('apply the negentropy lens'), plus 'entropy', 'negentropy', 'tacit knowledge', 'knowledge engine', and 'flip the switch' — phrases a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

The negentropy/entropy conceptual lens and its unique triggers ('negentropy lens', 'flip the switch') occupy a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bencium/bencium-marketplace
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.