CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-session-insight

Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is trellis-session-insight in mindfold-ai/Trellis

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured capability skill: executable command coverage of the common cases, explicit when/when-not guidance, and clean one-level-deep reference split. The main cost is token weight from the inlined agent-path catalog and meta-commentary that the CLI reference could carry.

Suggestions

Move the per-agent storage path catalog (Claude, Codex, Devin, Grok, OpenCode, Pi, ZCode paths) out of the 'What trellis mem is' section into references/cli-quick-reference.md, keeping only the one-sentence summary that mem indexes multiple agents' local logs.

Trim the meta-commentary sentences ('It is intentionally a capability skill, not a workflow', 'Forcing every recall into a fixed file makes the file grow into noise') to a single clause — the surrounding bullet structure already conveys the point.

In 'How to call it', convert the commented code block's sequence guidance into a short ordered decision path (start with search → if session id unknown use list/projects → extract or context → choose a disposition) to make the implicit workflow explicit.

DimensionReasoningScore

Conciseness

The when-to/when-not-to sections are tight, but the agent-storage path catalog (exact paths for Devin, Grok, OpenCode, Pi, ZCode) duplicates material that belongs in the CLI reference, and meta-commentary like 'It is intentionally a capability skill, not a workflow' and 'Forcing every recall into a fixed file makes the file grow into noise' could be trimmed — matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Copy-paste-ready commands covering the stated 80% cases — 'trellis mem search "<keyword>"', 'trellis mem extract <session-id> --phase brainstorm', 'trellis mem context <session-id> --turns 3 --around 2', 'trellis mem list --cwd <project-path>' — with explanatory comments and phase-slicing semantics, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

A clear decision workflow (when to reach for it, when not to, what to do with output) with an implicit call sequence guided by comments like 'When you do not know the session id yet, start with list + filter'. It is a read-only capability skill so no validation cap applies, but the sequence lacks the explicit step numbering and checkpoints of the top anchor.

4 / 5

Progressive Disclosure

The ~75-line overview keeps only the 80% case inline and clearly signals two real one-level-deep references — 'Full CLI reference is in `references/cli-quick-reference.md`' and '`references/triggering-patterns.md` lists more verbatim user phrasings' — both of which exist as actual bundle files, matching the top anchor.

5 / 5

Total

17

/

20

Passed

Description

86%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.

A strong description with explicit what/when structure and unusually rich verbatim trigger phrasing in both English and Chinese. The only gaps are that the tool's concrete operations are not enumerated and the disposition clause mildly overlaps spec-update skill territory.

DimensionReasoningScore

Specificity

Names the domain ('past AI conversation history through the `trellis mem` CLI') and the core action ('Returns raw past dialogue') plus disposition options, but does not enumerate the tool's concrete operations (search, extract, context), matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

Explicitly answers both 'what' ('Reach into past AI conversation history through the `trellis mem` CLI... Returns raw past dialogue') and 'when' ('Use whenever the user asks...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases with synonyms in two languages — 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', '上次怎么解的', '之前讨论过吗', '想起一段对话' — exactly the comprehensive-synonym coverage the top anchor describes.

5 / 5

Distinctiveness Conflict Risk

A clear niche (past-session recall via a named CLI) with distinct triggers, but the closing disposition clause ('whether to update spec, append to task notes...') slightly blurs the boundary with spec-update skills, keeping it between the 4 and 5 anchors, closer to 4.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.