CtrlK
BlogDocsLog inGet started
Tessl Logo

strategic-compact

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

58

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/strategic-compact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with concrete config, thresholds, and a clear decision guide, but it is over-long and monolithic, including a tangential token-optimization section that dilutes focus and adds tokens Claude does not need from this skill.

Suggestions

Remove or split out the "Token Optimization Patterns" section — it covers general context management unrelated to the compaction trigger and inflates the body.

Tighten "Why Strategic Compaction?" and "What Survives Compaction" which restate concepts Claude already knows about auto-compaction and persistence.

If the token-optimization material is kept, move it to a separate reference file and link to it one level deep from the overview.

DimensionReasoningScore

Conciseness

Most core sections are efficient and assume Claude's competence, but the "Token Optimization Patterns" section explains general token-management concepts (trigger tables, context composition, dedup tools) that are tangential to the compaction skill and pad the body.

2 / 3

Actionability

Provides copy-paste-ready hook JSON, concrete environment variable names with defaults, specific threshold numbers (160k/250k/60k/50/25), and a decision table — all directly executable guidance.

3 / 3

Workflow Clarity

The Compaction Decision Guide table gives a clear sequenced view of phase transitions with explicit compact/don't-compact guidance and rationale, and Best Practices reinforces the ordering; no destructive operation requires a validation loop here.

3 / 3

Progressive Disclosure

No reference files exist in the bundle and the body is a single ~140-line monolithic document; sections are well-organized but inline tangential material (Token Optimization Patterns) that could be split or removed keeps it from a clean overview.

2 / 3

Total

10

/

12

Passed

Description

57%

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 clearly identifies a distinct niche and uses correct third-person voice, but it stays abstract: it names a single action and implies rather than explicitly states trigger conditions, with no "Use when..." clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when running long sessions that approach context limits, switching between unrelated tasks, or completing a major milestone."

Enumerate concrete actions (e.g. "Suggests /compact, surfaces a decision guide, and tracks tool-call/context thresholds") to lift specificity.

Include natural user phrases like "long session", "context is full", or "slow responses" alongside the technical terms.

DimensionReasoningScore

Specificity

Names the domain (context compaction) and a concrete action ("Suggests manual context compaction at logical intervals"), but lists only one action rather than multiple specific concrete actions.

2 / 3

Completeness

Answers "what" (suggests manual compaction) but the "when" is only implied via "at logical intervals" / "through task phases" with no explicit "Use when..." trigger clause, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant keywords like "context compaction", "task phases", and "auto-compaction", but misses common natural variations a user might say (e.g. "context is full", "long session", "compact").

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (manual compaction timing) that is unlikely to overlap with other skills, though its triggers are stated abstractly rather than as crisp keywords.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.