CtrlK
BlogDocsLog inGet started
Tessl Logo

strategic-compact

任意の自動コンパクションではなく、タスクフェーズを通じてコンテキストを保持するための論理的な間隔での手動コンパクションを提案します。

50

Quality

54%

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/ja-JP/skills/strategic-compact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is concise, well-structured, and provides concrete hook configuration, but it relies on an external script not shown inline and lacks explicit validation/feedback checkpoints in its workflow. Strengthening the workflow with explicit checkpoints and surfacing the core script logic would raise the score.

Suggestions

Add explicit validation/checkpoint steps to the workflow (e.g. 'after compaction, verify the plan/context is retained before proceeding'), with a retry loop if context was lost.

Inline the core logic of suggest-compact.js (or a minimal excerpt) so the skill is self-contained rather than depending on an unseen script.

Tighten the 'なぜ戦略的コンパクションか?' rationale section, which restates general knowledge about auto-compaction that Claude already knows.

DimensionReasoningScore

Conciseness

The body is efficient and well-sectioned, only mildly over-explaining concepts like the rationale for compaction that could be tightened; every section mostly earns its tokens.

4 / 5

Actionability

It provides concrete, copy-paste-ready hook configuration JSON and named configuration variables (COMPACT_THRESHOLD), though it references a script (suggest-compact.js) whose source is not shown, leaving a minor gap.

4 / 5

Workflow Clarity

The 'how it works' steps are listed as a sequence, but there are no validation checkpoints or feedback loops, and the body itself notes the user decides whether to act — guidance is present but checkpoints are only implicit.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections with a single external link and a single script reference one level deep, with good signaling of plugin-vs-manual install paths.

4 / 5

Total

15

/

20

Passed

Description

41%Weight 40%Scale 1-5

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 third person and clearly states a niche purpose, but it is written in technical Japanese with no natural user trigger terms and lacks an explicit "Use when..." clause, capping completeness at 3. Adding concrete trigger conditions would substantially improve it.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill (e.g. long sessions, multi-step tasks, approaching context limits).

Include natural trigger terms users would actually say (e.g. 'compact', 'context window full', 'long conversation', 'running out of context').

Optionally provide an English description or bilingual keywords to improve trigger matching for users who don't phrase requests in technical Japanese.

DimensionReasoningScore

Specificity

The description names the domain (manual compaction) and one concrete action ("suggests" manual /compact), but the action is minimal/generic and offers no list of specific capabilities.

2 / 5

Completeness

It states clearly what the skill does (suggests manual compaction at logical intervals) but provides no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

It relies on technical jargon ("自動コンパクション", "コンテキストを保持", "タスクフェーズ") with no natural user-facing trigger phrases such as "compact", "context window", or "long session" that a user would actually say.

2 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (context-window management via strategic compaction) distinct from most skills, with only minor overlap risk with general context-management skills.

4 / 5

Total

11

/

20

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
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.