CtrlK
BlogDocsLog inGet started
Tessl Logo

context-recovery

Automatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.

58

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-sequenced, actionable recovery workflow with explicit guardrails, but is verbose, relies on pseudocode/placeholders for key logic, and is monolithic with no progressive disclosure of reference material.

Suggestions

Collapse the duplicate trigger lists in 'Triggers' and 'Auto-Trigger Detection' into a single section and trim the large placeholder synthesize/cache templates to essentials.

Replace the pseudocode trigger-detection block with a concrete, executable implementation and reduce reliance on <placeholder> tokens in command blocks.

Move channel-specific notes and the full recovery-context template into separate reference files (e.g. references/channels.md) referenced one level deep from SKILL.md.

DimensionReasoningScore

Conciseness

The ~230-line body duplicates trigger logic across 'Triggers' and 'Auto-Trigger Detection' and embeds large placeholder templates, so while it avoids explaining concepts Claude already knows, it could be tightened.

2 / 3

Actionability

Provides concrete bash/jq/grep commands and parameterized message:read calls with explicit thresholds, but the core trigger-detection logic is explicitly pseudocode and many blocks use placeholders rather than copy-paste-ready code.

2 / 3

Workflow Clarity

A clear 7-step sequence with adaptive-depth thresholds, hard caps, and an explicit checkpoint instructing not to claim completion when sources are partial; the constraints section functions as a checklist.

3 / 3

Progressive Disclosure

No bundle files exist and all content — channel-specific notes, the full synthesize template, example, and guardrails — lives inline in a single monolithic SKILL.md rather than being split into signaled reference files.

2 / 3

Total

9

/

12

Passed

Description

75%

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 clearly communicates a distinct niche and explicit trigger conditions, answering both what and when. It is slightly weak on natural user-facing trigger phrasing and lists only one abstract action.

DimensionReasoningScore

Specificity

Names a concrete domain and action ('recover working context after session compaction') but lists only a single abstract action rather than multiple specific concrete actions like extract/fill/merge.

2 / 3

Completeness

Explicitly answers both what ('recover working context after session compaction') and when ('when continuation is implied but context is missing'), providing equivalent explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes relevant trigger phrases ('session compaction', 'continuation is implied', 'context is missing') but they are process-oriented rather than the natural user phrasings ('continue', 'where were we') that appear only in the body, not the description.

2 / 3

Distinctiveness Conflict Risk

Has a clear niche (post-compaction context recovery across messaging channels) with distinctive triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
jdrhyne/agent-skills
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.