opencontext
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
Install with Tessl CLI
npx tessl i github:supercent-io/skills-template --skill opencontext70
Quality
55%
Does it follow best practices?
Impact
96%
2.13xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/opencontext/SKILL.mdDiscovery
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.
The description identifies a specific tool (OpenContext) and general capabilities but lacks explicit trigger guidance for when Claude should select this skill. The actions described are somewhat vague ('keep context', 'store conclusions') and could benefit from more concrete examples. Without a 'Use when...' clause, Claude may struggle to reliably select this skill from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'remember this', 'save for later', 'recall previous conversation', 'persistent memory', or 'cross-session context'.
Make actions more concrete by specifying what types of conclusions are stored and what document search workflows look like (e.g., 'index documents for semantic search', 'retrieve previously saved notes').
Include natural user phrases that would trigger this skill, such as 'don't forget', 'store this information', or 'look up what we discussed before'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (memory/context management) and some actions ('store conclusions', 'provide document search workflows'), but lacks comprehensive concrete actions. 'Keep context' is somewhat vague. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('memory', 'context', 'sessions', 'OpenContext') but missing common variations users might say like 'remember', 'recall', 'save for later', 'persistent storage', or 'knowledge base'. | 2 / 3 |
Distinctiveness Conflict Risk | 'OpenContext' is a specific tool name which helps distinctiveness, but 'memory and context management for AI agents' could overlap with other memory/state management skills. The scope across 'sessions/repos/dates' is broad. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill with excellent actionability and workflow clarity, providing concrete CLI commands and clear multi-step processes. The main weaknesses are moderate verbosity (marketing language, problem/solution framing that Claude doesn't need) and a monolithic structure that could benefit from splitting advanced topics into separate reference files.
Suggestions
Remove the 'Problem' section and marketing tagline - Claude doesn't need motivation, just instructions
Consider moving sections 5-6 (MCP Tools, Multi-Agent workflow) to separate reference files and linking to them
Trim the 'Core concepts' section to just the workflow diagram and default paths table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content (e.g., 'Problem' section explaining context loss, marketing-style tagline). The tables and command references are well-organized but could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands, concrete code examples, and copy-paste ready workflows. Commands like `oc init`, `oc folder create`, and `oc search` are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit sequences (Before/During/After work pattern, Multi-Agent orchestration pattern). The daily workflow section provides clear checkpoints and the practical example shows a complete flow. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (could benefit from splitting detailed sections like MCP tools or Multi-Agent workflows into separate files). References to external docs are present but inline content is heavy. | 2 / 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.
- Reviewed
Table of Contents
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.