tessl install https://github.com/softaworks/agent-toolkit --skill reducing-entropygithub.com/softaworks/agent-toolkit
Manual-only skill for minimizing total codebase size. Only activate when explicitly requested by user. Measures success by final code amount, not effort. Bias toward deletion.
Average Score
82%
Content
85%
Description
75%
Generated
Validations
Total score
12/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 82 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'reducing-entropy' | |
description_field 'description' field is valid (175 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples No examples detected (no code fences and no 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 2
Total score
11/12| Dimension | Score |
|---|---|
conciseness Every section earns its place. No explanation of concepts Claude knows, no padding. The content is lean and direct, using bullet points and short phrases effectively. | 3/3 |
actionability Provides clear mental frameworks and questions to ask, but lacks concrete examples of actual code deletion or measurement. No executable commands or specific code patterns to follow. | 2/3 |
workflow_clarity Clear sequence: load mindset first, then apply three questions framework. The 'Before You Begin' section establishes explicit prerequisites, and the three questions provide a clear decision process. | 3/3 |
progressive_disclosure Well-structured with clear references to external files (references/, adding-reference-mindsets.md). Content is appropriately split - philosophy here, detailed mindsets in reference files. One level deep. | 3/3 |
Suggestions
Add a concrete before/after example showing actual code reduction (e.g., '14 functions → 2 functions' with real code snippets)
Include a specific command or script for measuring lines of code before/after changes
Overall Assessment
This is a well-crafted philosophical/mindset skill that excels at conciseness and structure. It clearly establishes a decision framework with the three questions approach and properly delegates detailed content to reference files. The main weakness is the lack of concrete, executable examples - showing a before/after code comparison or specific deletion patterns would strengthen actionability.
Description
Suggestions 2
Total score
10/12| Dimension | Score |
|---|---|
specificity Names the domain (codebase size minimization) and mentions some actions ('deletion', 'measures success by final code amount'), but lacks concrete specific actions like 'remove unused imports', 'consolidate duplicate functions', or 'eliminate dead code paths'. | 2/3 |
completeness Clearly answers both what ('minimizing total codebase size', 'bias toward deletion') and when ('Only activate when explicitly requested by user', 'Manual-only skill'), providing explicit trigger guidance about requiring explicit user request. | 3/3 |
trigger_term_quality Contains some relevant terms like 'codebase size', 'deletion', and 'minimize', but misses common natural variations users might say such as 'reduce code', 'clean up', 'remove unused code', 'dead code', 'code bloat', or 'slim down'. | 2/3 |
distinctiveness_conflict_risk The 'manual-only' constraint and specific focus on 'minimizing total codebase size' with 'bias toward deletion' creates a clear niche that is unlikely to conflict with general refactoring or code quality skills. | 3/3 |
Suggestions
Add specific concrete actions like 'removes dead code, consolidates duplicate functions, eliminates unused imports and dependencies'
Include more natural trigger terms users might say: 'reduce code', 'clean up codebase', 'remove unused code', 'slim down', 'code bloat'
Overall Assessment
This description has strong completeness with explicit activation criteria and good distinctiveness through its manual-only constraint and deletion-focused approach. However, it lacks specific concrete actions and could benefit from more natural trigger terms that users would actually say when requesting code reduction.