strategic-compact

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

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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 well-structured and actionable with concrete config, decision tables, and risk-aware guidance, but is somewhat padded by tangential token-optimization material and time-sensitive version notes.

Suggestions

Move the 'Token Optimization Patterns' section into a separate reference file or trim it, since it largely covers general token hygiene unrelated to triggering strategic compaction.

Relocate the version-specific note about Claude Code 2.1.233 removing todo tools into a clearly marked 'Version notes' or 'Deprecated assumptions' section to satisfy time-sensitivity guidance.

Tighten the 'What Survives Compaction' table to only the non-obvious rows, assuming Claude already knows that files on disk and git state persist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tables and code, but includes tangential 'Token Optimization Patterns' content and a long version-specific blockquote ('2.1.233 removed the todo/task tools') that isn't in a deprecated section, both of which could be tightened.	3 / 5
Actionability	Provides copy-paste-ready hook setup JSON, a concrete environment variable (COMPACT_THRESHOLD), a phase-transition decision table, and executable commands like '/compact Focus on implementing auth middleware next', with only minor gaps.	4 / 5
Workflow Clarity	Clear sequence via the decision guide table and Best Practices, with risk-aware checkpoints ('Write before compacting', 'write the plan to a file before compacting'); minor validation gaps keep it just below 5.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep external references (the Longform Guide link, related skills); the inlined Token Optimization Patterns section is the main organization gap since no bundle files are present.	4 / 5
	Total	15 / 20 Passed

Description

53%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 clearly states what the skill does and carves out a distinct niche, but lacks an explicit 'Use when...' trigger clause and only offers one concrete action with limited keyword variations.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running long multi-phase sessions that approach context limits or before major task shifts.'

Expand concrete actions beyond 'suggests' (e.g., 'tracks tool calls, detects thresholds, reminds at intervals') to raise specificity.

Include more natural trigger terms users say, such as 'context limit', 'context full', '/compact', or 'long session'.

Dimension	Reasoning	Score
Specificity	Names the domain (context compaction) and one concrete action ('Suggests manual context compaction at logical intervals'), but offers only a single action rather than a comprehensive list.	3 / 5
Completeness	Has a clear 'what' (suggests manual compaction at logical intervals) but the 'when' is only weakly implied ('at logical intervals', 'through task phases') with no explicit 'Use when...' trigger clause, capping completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('context compaction', 'compact', 'auto-compaction') but misses common natural variations a user might say like 'context limit', 'context full', '/compact', or 'long session'.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (timing of manual compaction vs auto-compaction) with low conflict risk, though minor overlap exists with related context-management skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/strategic-compact/SKILL.md
Commit: ca185ef

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.