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.

64

Quality

75%

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 ./docs/zh-TW/skills/strategic-compact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The content is concise, actionable, and clearly structured, with concrete hook configuration and a well-sequenced explanation suitable for a simple advisory skill. No bundle files were present to verify, but the inline structure is self-contained and well-organized.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows; every section (rationale, hook setup, config, best practices) earns its place.

3 / 3

Actionability

Provides concrete, copy-ready guidance: a complete hooks JSON block, the exact env var COMPACT_THRESHOLD with default 50, and explicit plugin-vs-manual install handling, which is actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The hook behavior is clearly sequenced (track calls → threshold detection → periodic reminder) and the best-practices list gives ordered guidance; the skill is advisory ("Hook tells you when, you decide whether"), so no destructive-operation validation is required.

3 / 3

Progressive Disclosure

Under ~50 lines with well-organized sections and no nested references; the only links are a one-level external URL and a plugin-internal script path, satisfying the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 in clear third person and names a specific, distinguishable capability, but it omits an explicit "Use when..." trigger clause and natural user keywords, capping completeness and trigger quality at the mid-level.

Suggestions

Add an explicit trigger clause, e.g. "Use when a task spans many tool calls, before long multi-step implementations, or when the user mentions context running low."

Include natural user-facing keywords such as "compact", "/compact", and "context window" so it surfaces for the way users actually phrase the need.

Name the concrete actions more comprehensively (e.g. "Suggests manual /compact at logical task boundaries — after exploration, at milestones, and before context shifts") to lift specificity.

DimensionReasoningScore

Specificity

Names a concrete action ("Suggests manual context compaction") and the domain ("task phases"), but lists only a single action rather than multiple specific concrete actions, so it stops short of 3.

2 / 3

Completeness

The "what" is clear, but "when" is only implied ("at logical intervals") with no explicit "Use when..." clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Relevant terms like "context compaction" and "task phases" appear, but there are no natural user-facing trigger keywords (e.g. "compact", "context running out") and common variations are missing, so it is above 1 but not a 3.

2 / 3

Distinctiveness Conflict Risk

The niche (manual compaction timing) is fairly distinct and unlikely to trigger unrelated skills, but the absence of explicit trigger guidance keeps it from a clear 3.

2 / 3

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ysyecust/everything-claude-code
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.