Maintaining .opencode/context-log.md for session continuity
72
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
32%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 too terse and lacks critical components for effective skill selection. While it identifies a specific file and general purpose, it fails to explain concrete actions or provide explicit trigger conditions. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'remember context', 'session notes', 'pick up where we left off', 'track progress', or 'log decisions'.
Expand the capability description with specific actions such as 'append session summaries', 'record key decisions', 'track completed tasks', or 'document context for future sessions'.
Include natural user phrases that would trigger this skill, such as 'save this for later', 'update the context log', or 'what did we do last session'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (context logging) and one action (maintaining), but lacks detail on what 'maintaining' entails - no concrete actions like 'append entries', 'summarize sessions', or 'track decisions' are mentioned. | 2 / 3 |
Completeness | Only addresses 'what' at a high level (maintaining a log file) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'context-log.md' and 'session continuity', but misses natural user phrases like 'remember this', 'pick up where we left off', 'session notes', or 'context tracking'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific file path '.opencode/context-log.md' provides some distinctiveness, but 'session continuity' is vague enough to potentially overlap with other memory, logging, or documentation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides immediately actionable templates and clear guidance on when to update the context log. The structure is clean and efficient. Minor weakness is the lack of validation/verification guidance for ensuring log integrity, though this is less critical for a non-destructive append-only operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanation of what a context log is conceptually—just shows when/how to use it. Tables and templates are efficient. | 3 / 3 |
Actionability | Provides copy-paste ready templates for both initial setup and checkpoints, with a concrete example showing exact format. The table clearly specifies when to take each action. | 3 / 3 |
Workflow Clarity | The when-to-update table provides clear triggers, but lacks explicit validation steps. No guidance on what to do if the log becomes corrupted or how to verify entries are correct. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Purpose, Location, When to Update, Templates, Example). No need for external references. | 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.
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.