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.

86

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

82%

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 thorough in its completeness, clearly stating both what the skill does and when to use it, with extensive trigger term coverage. However, the actual capabilities described are somewhat abstract ('evaluates', 'surfacing') rather than listing concrete deliverables, and the very broad trigger conditions (any architecture decision, any strategy planning) create significant overlap risk with other skills. The proactive nudge activation instruction is unusual and could cause unwanted triggering.

Suggestions

Replace abstract verbs like 'evaluates' and 'surfacing' with concrete deliverables, e.g., 'Generates entropy/negentropy scorecards, identifies decay vectors, maps tacit knowledge gaps, and produces structured comparison matrices for architectural options.'

Narrow the broad trigger conditions to reduce conflict risk — instead of triggering on any 'architecture decision' or 'planning strategies', specify that this skill applies specifically when the entropy/negentropy analytical lens would add value, rather than for general architecture review.

DimensionReasoningScore

Specificity

The description names the domain ('decision-support framework') and mentions some actions like 'evaluates systems, architectures, and strategies' and 'surfacing tacit knowledge gaps', but the actual concrete actions are somewhat abstract — 'evaluates' and 'surfacing' are vague compared to truly specific actions like 'generates comparison matrices' or 'scores options on entropy metrics'.

2 / 3

Completeness

Clearly answers both 'what' (evaluates systems/architectures/strategies through entropy vs negentropy lens while surfacing tacit knowledge gaps) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios, plus explicit keyword triggers and even a proactive nudge activation condition).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including 'architecture decisions', 'system designs', 'technical approaches', 'choosing between options', 'auditing existing systems', 'planning strategies', plus explicit phrases like 'apply the negentropy lens', 'entropy', 'negentropy', 'tacit knowledge', 'knowledge engine', and 'flip the switch'. These cover both natural user language and domain-specific terms.

3 / 3

Distinctiveness Conflict Risk

While the entropy/negentropy lens and specific trigger phrases like 'flip the switch' and 'negentropy lens' are distinctive, the broad triggers like 'architecture decisions', 'evaluating system designs', 'choosing between options', and 'planning strategies' could easily overlap with general architecture review or decision-making skills. The nudge activation instruction to trigger even when not asked further increases conflict risk.

2 / 3

Total

10

/

12

Passed

Implementation

85%

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

This is a strong thinking framework skill that provides clear, actionable guidance for applying an entropy/negentropy lens to decision-making. The 5-phase process is well-sequenced with good contextual adaptation in the output formatting section. The main weakness is moderate verbosity — the enumerated signs of entropy/negentropy and some explanatory text could be tightened without losing clarity, though the verbosity is less egregious than typical score-1 content since most of it serves as operational reference material.

DimensionReasoningScore

Conciseness

The skill is well-written but somewhat verbose for a thinking framework. Some sections like 'The Two States' enumerate signs that Claude could infer, and the anti-patterns section, while useful, adds length. The term definitions section requiring inline definitions on first use is good operational guidance, but the bullet-point expansions of entropy/negentropy signs are somewhat redundant given the core principle already explains the concepts.

2 / 3

Actionability

The skill provides a concrete, sequenced 5-phase decision process with specific questions to ask, specific evaluation criteria, and clear output formatting guidance for different contexts. The questions in Phase 3 are particularly actionable — they're specific probes Claude can directly use. The anti-patterns section gives concrete examples of what to watch for.

3 / 3

Workflow Clarity

The 5-phase process is clearly sequenced with explicit ordering ('Organize first. Challenge second.'), each phase has a clear purpose, and the output formatting section provides context-dependent workflow variations (full 5-phase for architecture reviews, abbreviated for quick decisions). The 'non-negotiable' marker on Phase 3 acts as a validation checkpoint ensuring tacit knowledge is always surfaced.

3 / 3

Progressive Disclosure

The skill is well-structured with clear sections that progress logically from core principle → definitions → states → process → output formatting → anti-patterns. It appropriately references `references/origin-essay.md` for conceptual background rather than inlining it. The content length is justified by the framework's complexity and stays in a single file appropriately.

3 / 3

Total

11

/

12

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.

Validation11 / 11 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.