continual-learning
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
45
47%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./continual-learning/skills/continual-learning/SKILL.mdQuality
Discovery
17%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 uses internal jargon and lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. While it references specific tools (agents-memory-updater, AGENTS.md), the overall framing is too abstract and does not include natural trigger terms a user would employ.
Suggestions
Add an explicit 'Use when...' clause describing the situations that should trigger this skill, e.g., 'Use when the user wants to update agent memory from conversation transcripts or refresh AGENTS.md with new learnings.'
Replace jargon like 'orchestrate continual learning' and 'transcript mining' with natural language terms users would actually say, such as 'update agent knowledge', 'learn from past conversations', or 'refresh agent configuration.'
List concrete actions more explicitly, e.g., 'Extracts key information from conversation transcripts and updates AGENTS.md files to keep agent instructions current.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a domain (continual learning) and some actions (delegating transcript mining, AGENTS.md updates), but the actions are somewhat abstract—'orchestrate' and 'delegating' are meta-level rather than concrete end-user-facing capabilities. | 2 / 3 |
Completeness | There is no explicit 'Use when...' clause or equivalent trigger guidance. The description only partially addresses 'what' (orchestrate learning via delegation) and does not address 'when' at all, which caps this at a low score. | 1 / 3 |
Trigger Term Quality | The terms used ('orchestrate continual learning', 'transcript mining', 'agents-memory-updater') are highly technical and internal jargon. A user would not naturally say these phrases when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of specific artifacts like 'agents-memory-updater' and 'AGENTS.md' provides some distinctiveness, but the broader framing around 'continual learning' and 'transcript mining' could overlap with other memory or knowledge management skills. | 2 / 3 |
Total | 6 / 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 well-scoped, concise orchestration skill that clearly defines its boundaries and keeps the parent flow minimal. Its main weakness is the lack of concrete invocation details for calling the subagent and the absence of a navigable reference to the subagent's definition. For a simple delegation skill, it's effective but could benefit from slightly more actionable specifics.
Suggestions
Add a concrete example of how to invoke `agents-memory-updater` (e.g., the exact tool call or subagent invocation syntax).
Include a reference or link to the `agents-memory-updater` skill file so the relationship is navigable (e.g., 'See [agents-memory-updater/SKILL.md](../agents-memory-updater/SKILL.md) for the subagent's behavior').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely lean—every line serves a purpose. It assumes Claude knows what subagents are and how to call them, with no unnecessary explanation. | 3 / 3 |
Actionability | The workflow says 'Call agents-memory-updater' but provides no concrete invocation syntax, tool call format, or example of how to actually call the subagent. The guidance is clear in intent but lacks executable specifics. | 2 / 3 |
Workflow Clarity | For this simple two-step orchestration skill (call subagent, return result), the sequence is unambiguous. The guardrails clearly bound what the parent should and should not do, which serves as implicit validation. | 3 / 3 |
Progressive Disclosure | The skill references 'agents-memory-updater' as a subagent but provides no link or path to its definition. With no bundle files provided, there's no way to verify the reference or navigate to the subagent's details. A clear reference (e.g., a link to the subagent's skill file) would improve discoverability. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- cursor/plugins
- Commit
b8f2564
- 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.