This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.
69
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/filesystem-context/SKILL.mdQuality
Discovery
37%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 is fundamentally incomplete - it functions as a list of trigger phrases without ever explaining what the skill actually does. While the trigger terms are well-chosen and specific, the complete absence of capability description makes it impossible for Claude to understand what actions this skill enables or how it differs from other file/context-related skills.
Suggestions
Add concrete actions at the beginning describing what the skill does (e.g., 'Persists tool outputs and intermediate results to files, implements scratch pad patterns for agent workflows, and loads context on-demand to minimize token usage.')
Restructure to follow the pattern: '[What it does]. Use when [triggers]' - currently only the 'Use when' portion exists.
Convert from pure trigger-list format to include specific capabilities like 'writes context summaries', 'creates indexed scratch files', or 'manages context checkpoints'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only trigger phrases. It never explains what the skill actually does, using vague concepts like 'dynamic context discovery' and 'agent memory' without specifying concrete capabilities. | 1 / 3 |
Completeness | The description only addresses 'when' (trigger conditions) but completely omits 'what' - there is no explanation of what actions or capabilities this skill provides. The 'what does this do' question is entirely unanswered. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'offload context to files', 'reduce context window bloat', 'agent scratch pads', 'just-in-time context loading'. These are specific phrases a user working with context management would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger terms are fairly specific to context/memory management, but without knowing what the skill actually does, it could overlap with file management, memory systems, or general agent skills. The niche is somewhat clear but the lack of capability description creates ambiguity. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill with excellent actionability and workflow clarity. The concrete code examples, clear file organization patterns, and comprehensive gotchas section make it highly practical. The main weakness is moderate verbosity in explanatory sections that could be tightened without losing clarity.
Suggestions
Trim the 'Core Concepts' section - the four context failure modes could be condensed to a bullet list without the explanatory 'Fix by' clauses, as Claude can infer the remedies from the patterns that follow.
Remove phrases like 'because context windows are limited while tasks often require more information' - Claude knows this; lead with the actionable guidance instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanation (e.g., explaining why context windows are limited, what the four context failure modes are in detail). Some sections could be tightened, though it generally respects Claude's intelligence. | 2 / 3 |
Actionability | Provides concrete, executable Python code examples, specific file structures, and copy-paste ready patterns. The scratch pad, plan persistence, and tool output offloading examples are fully actionable with real code. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation guidance. The 'When to Use' criteria, file organization patterns, and gotchas section provide clear checkpoints. Example workflows show clear before/after states. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, a references section pointing to one-level-deep external files, and an integration section linking to related skills. Content is appropriately organized with quick patterns followed by detailed topics. | 3 / 3 |
Total | 11 / 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.
3ab8c94
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.