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.

66

Quality

79%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./negentropy-lens/skills/negentropy-lens/SKILL.md
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 strong on completeness and trigger term coverage, with a clear 'Use when' clause and numerous explicit keyword triggers. However, the actual capabilities described are somewhat abstract (evaluates, surfaces gaps) rather than listing concrete outputs, and the very broad situational triggers (any decision point, any architecture review) create meaningful overlap risk with other skills. The proactive nudge instruction is unusual and could cause unwanted activations.

Suggestions

Add more specific concrete outputs/actions, e.g., 'Produces entropy/negentropy scorecards, identifies decay vectors, maps tacit knowledge dependencies, generates comparative option matrices'

Narrow the situational triggers to reduce conflict risk — consider scoping to only when the entropy/negentropy lens is explicitly requested or when tacit knowledge analysis is needed, rather than any generic decision point

DimensionReasoningScore

Specificity

The description names the domain ('decision-support framework') and mentions evaluating systems, architectures, and strategies through a specific lens, but the concrete actions are somewhat abstract — 'evaluates', 'surfacing tacit knowledge gaps' — rather than listing multiple specific, tangible outputs or operations.

2 / 3

Completeness

Clearly answers both 'what' (a decision-support framework evaluating through entropy/negentropy lens while surfacing tacit knowledge gaps) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios and keyword triggers). Also includes a proactive nudge activation condition.

3 / 3

Trigger Term Quality

Excellent coverage of trigger terms including natural phrases like 'architecture decisions', 'evaluating system designs', 'reviewing technical approaches', 'choosing between options', 'auditing existing systems', and explicit keyword triggers like 'entropy', 'negentropy', 'tacit knowledge', 'knowledge engine', 'flip the switch', and 'apply the negentropy lens'.

3 / 3

Distinctiveness Conflict Risk

The unique 'entropy/negentropy lens' and 'tacit knowledge' framing provide some distinctiveness, but 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

77%

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

This is a well-structured decision-support framework with strong actionability and clear workflow sequencing. The 5-phase process is concrete and well-ordered, with appropriate context-dependent output formatting. The main weakness is moderate verbosity — the entropy/negentropy sign lists and some explanatory text could be tightened given Claude's existing conceptual knowledge, and the lengthy inline content could benefit from being split into reference files for better progressive disclosure.

Suggestions

Trim the 'Two States' section significantly — Claude understands entropy and negentropy conceptually; focus only on the domain-specific indicators that are non-obvious (e.g., 'stasis traps' is valuable, but 'technical debt compounds silently' is obvious).

Consider moving the anti-patterns catalog and the detailed tacit knowledge questions into a separate reference file (e.g., `references/anti-patterns.md` and `references/tacit-questions.md`) to keep the main skill leaner.

DimensionReasoningScore

Conciseness

The skill is well-written but somewhat verbose for a thinking framework. The 'Two States' section with entropy/negentropy signs could be tightened — Claude already understands these concepts. The anti-patterns section, while useful, adds length. The term definitions section asking Claude to define terms inline on first use is good operational guidance, but the detailed sign lists are somewhat redundant with Claude's existing knowledge.

2 / 3

Actionability

The 5-phase decision process provides concrete, sequenced steps with specific questions to ask and specific evaluation criteria. The output formatting section gives clear guidance for different contexts (architecture reviews, quick decisions, nudges). The anti-patterns section provides specific named patterns to watch for with concrete examples.

3 / 3

Workflow Clarity

The 5-phase process is clearly sequenced with explicit ordering ('Organize first. Challenge second.'). Each phase has clear steps and criteria. Phase 3 is marked as 'non-negotiable,' providing a validation checkpoint. The workflow handles different complexity levels through the output formatting section, which tells Claude when to skip phases.

3 / 3

Progressive Disclosure

The skill references `references/origin-essay.md` twice for conceptual origins, which is good progressive disclosure. However, the skill is quite long (~180 lines of substantive content) and could benefit from splitting detailed content (e.g., the full list of tacit knowledge questions, the anti-patterns catalog) into separate reference files. No bundle files were provided to verify the referenced path exists.

2 / 3

Total

10

/

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.