建议在逻辑间隔处进行手动上下文压缩,以在任务阶段中保留上下文,而非任意的自动压缩。
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill strategic-compactOverall
score
55%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description fails as a skill description because it reads as a recommendation or best practice rather than describing a skill's capabilities. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinctive identifiers. The Chinese text essentially says 'recommend manual context compression at logical intervals to preserve context during task phases rather than arbitrary automatic compression' - which is advice, not a skill definition.
Suggestions
Rewrite as a capability description: Start with concrete actions like 'Compresses conversation context, summarizes previous exchanges, manages memory across long sessions'
Add explicit trigger guidance: Include 'Use when...' clause with natural terms users might say like 'summarize our conversation', 'compress context', 'save memory', 'long conversation'
Make distinctive: Specify the unique approach (manual vs automatic compression) and when this skill should be chosen over other context/memory management skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is vague and abstract - it mentions 'manual context compression' and 'preserving context during task phases' but doesn't describe concrete actions Claude can perform. No specific capabilities are listed. | 1 / 3 |
Completeness | This reads more like a recommendation or guideline than a skill description. It doesn't clearly answer 'what does this do' as a capability, and there is no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('上下文压缩', '逻辑间隔') that users would not naturally say. No common user-facing keywords or natural language triggers are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Context compression' and 'task phases' are generic concepts that could overlap with many other skills related to memory, context management, or task handling. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, effectively explaining the strategic compaction concept and its benefits over automatic compaction. However, it falls short on actionability by not including the actual suggest-compact.sh script content and could improve workflow clarity with more concrete examples of decision points for manual compaction.
Suggestions
Include the actual suggest-compact.sh script content or provide a direct link to it, so users can implement the hook without searching for the script
Add 1-2 concrete examples showing specific scenarios where you would/wouldn't compact (e.g., 'After researching 5 files to understand a bug, compact before implementing the fix' vs 'Don't compact while in the middle of a multi-file refactor')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, directly explaining the strategic compaction concept without unnecessary elaboration. Every section serves a clear purpose and assumes Claude understands basic concepts like hooks and environment variables. | 3 / 3 |
Actionability | Provides concrete JSON configuration and references a shell script, but the actual script implementation is not shown. The best practices are helpful but somewhat abstract without concrete examples of what a 'planning phase' or 'debugging session' looks like in practice. | 2 / 3 |
Workflow Clarity | The workflow of when to compact is explained conceptually (after exploration, after milestones, before context switches), but lacks explicit step-by-step guidance. The hook mechanism is described but the decision-making process for when to actually run /compact is left vague. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from rationale to implementation to best practices. References to external resources (long-form guide, memory persistence hooks) are appropriately signaled without deep nesting. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.