CtrlK
BlogDocsLog inGet started
Tessl Logo

cross-channel-history-retrieval

跨会话检索聊天原文(记忆不足时再用)。在回答任何关于历史事件、日期、人物、过去对话的问题时,如果记忆中没有相关信息或不足以回答,则需要使用跨会话检索聊天原文。用 mcp_exec_command 执行 scripts/search_history.py,读 ~/.jiuwenclaw/agent/sessions/*/history.json。支持 channel、session_id、关键词、时间窗。如果搜索结果不足,尝试用不同的关键词再次搜索。

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./jiuwenclaw/jiuwenclaw/resources/agent/jiuwenclaw_workspace/skills/cross-channel-history-retrieval/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is well-structured, actionable, and concise, with executable commands, a full parameter reference, a clear time-strategy decision flow, and an output-injection workflow including no-hit handling. It could add a second worked example and explicit validation phrasing to reach top marks.

Suggestions

Add a second copy-paste example demonstrating --at plus --window-minutes for the 'only a moment is given' case.

Make the no-hit feedback loop more explicit as a validation checkpoint (e.g., 'Verify HISTORY_CONTEXT_BLOCK is non-empty; if empty, broaden window/keywords and retry').

Consider trimming the Windows parenthetical into a short note plus a one-line command to reduce token weight while preserving the guidance.

DimensionReasoningScore

Conciseness

Efficient and free of concept explanations Claude already knows; the long Windows-path parenthetical is necessary actionable detail rather than padding, with only minor instances that could be trimmed.

4 / 5

Actionability

Provides a concrete, copy-paste-ready bash command plus a complete parameter reference table; minor gaps such as no worked example for --at/--window-minutes keep it just below fully comprehensive.

4 / 5

Workflow Clarity

The 时间策略 section gives a clear 4-step decision sequence and the 输出与上下文注入 section adds a post-retrieval workflow with a no-hit feedback path; the operation is read-only so the destructive cap does not apply, but checkpoints are decision rules rather than explicit validation steps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with the actual logic appropriately split into scripts/search_history.py and referenced by path; no nested references, with only minor organization gaps keeping it from a perfect score.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 is strong: it concisely states the capability, mechanism, and explicit trigger conditions, and scopes itself to a distinct niche. Minor improvements could add more natural user phrasings and tighten the broad historical-trigger wording.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities — '用 mcp_exec_command 执行 scripts/search_history.py', '读 ~/.jiuwenclaw/agent/sessions/*/history.json', '支持 channel、session_id、关键词、时间窗' — with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (retrieve cross-session chat history via a script reading history.json) and when (when memory lacks info for questions about historical events/dates/people/past conversations) with concrete trigger guidance.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('关于历史事件、日期、人物、过去对话的问题', '记忆不足时再用') with good coverage, though a few common phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cross-session/cross-channel history retrieval) with the '记忆不足时再用' boundary limiting overlap, though broad triggers like '历史事件、日期' could marginally overlap with general knowledge queries.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
XiaoLuoLYG/GOD
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.