tdg-personal/strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
59
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
40%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 identifies a clear niche around manual context compaction and is distinctive, but it lacks explicit trigger guidance ('Use when...') and misses common user-facing keywords. The single-action focus and absence of a 'when' clause significantly limit its effectiveness for skill selection among many options.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about managing context window limits, preserving conversation memory, or avoiding auto-compaction during long tasks.'
Include natural trigger terms users would actually say, such as 'context window', 'running out of context', 'long conversation', 'memory management', or 'conversation history'.
List additional concrete actions beyond just suggesting compaction, e.g., 'Identifies logical breakpoints in tasks, recommends when to compact, and explains how to preserve key context across phases.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (context compaction) and describes the core action (suggests manual context compaction at logical intervals), but it doesn't list multiple concrete actions—it's essentially one action with a rationale. | 2 / 3 |
Completeness | The description explains what the skill does (suggests manual context compaction) but lacks any explicit 'Use when...' clause or trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'context compaction', 'auto-compaction', and 'task phases', but misses common user-facing variations like 'context window', 'running out of context', 'memory management', or 'conversation length'. Users may not naturally say 'compaction'. | 2 / 3 |
Distinctiveness Conflict Risk | Context compaction is a fairly niche topic, and the description's focus on manual compaction at logical intervals vs. auto-compaction creates a clear, distinct niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable guidance with excellent decision tables for when to compact and concrete hook configuration. However, it suffers from scope creep — the 'Token Optimization Patterns' section covers topics beyond strategic compaction (lazy loading, deduplication, context-mode) that dilute the core skill. The workflow could benefit from explicit validation steps around saving context before compacting.
Suggestions
Move the 'Token Optimization Patterns' section to a separate reference file (e.g., TOKEN-OPTIMIZATION.md) and link to it, keeping SKILL.md focused on strategic compaction.
Add an explicit pre-compaction checklist or validation step: verify important context is saved to files/memory before running /compact.
Trim the 'What Survives Compaction' and 'Why Strategic Compaction?' sections — Claude understands these concepts and they can be reduced to 2-3 bullet points each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is more verbose than necessary. The 'Why Strategic Compaction?' section explains concepts Claude can infer, the 'What Survives Compaction' table is largely common knowledge for Claude, and the 'Token Optimization Patterns' section drifts into tangential topics (trigger-table lazy loading, duplicate instruction detection) that aren't core to the strategic compact skill. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready JSON configuration for hooks, a clear decision guide table for when to compact, specific commands like `/compact Focus on implementing auth middleware next`, and actionable best practices. The hook setup is fully executable. | 3 / 3 |
Workflow Clarity | The decision guide table is excellent for deciding when to compact, and the 'How It Works' section explains the mechanism. However, there's no explicit end-to-end workflow with validation checkpoints — for instance, no guidance on verifying that important context was saved before compacting, or what to do if compaction loses critical state. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear headers and tables, but the 'Token Optimization Patterns' section is a large inline block that feels tangential and could be split into a separate reference file. The 'Related' section at the end provides some navigation but the references are external links rather than well-organized companion files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents