CtrlK
BlogDocsLog inGet started
Tessl Logo

record-session

Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An exemplary instruction-only skill body: lean, fully actionable with exact commands, a clearly sequenced two-step workflow with verification and error-reporting feedback loops, and clean section organization with no unnecessary external references. No substantive weaknesses found.

DimensionReasoningScore

Conciseness

The ~80-line body is lean: exact commands, a compact auto-completes checklist, and a command reference table, with no explanation of concepts Claude already knows; even the dense portability rule consists of operational clauses that each earn their place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with real flags (get_context.py --mode record, add_session.py with --stdin heredoc, task.py archive) and concrete verification commands, matching the level-3 anchor rather than the pseudocode level 2.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1 context/tasks, Step 2 add session) with explicit validation checkpoints ("verify with: git log -1 --oneline; git status --short") and a feedback loop ("report the exact blocker instead of claiming the session was recorded"), matching the clear-sequence-with-validation anchor; it is not level 2 because checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

No bundle files are provided (references/scripts/assets absent) and the skill needs none; the body is well-organized into "Record Work Progress" and "Script Command Reference" sections, which per the simple-skills scoring note earns a 3 for a self-contained, well-structured skill.

3 / 3

Total

12

/

12

Passed

Description

85%

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, third-person description that states concrete capabilities and an explicit Use-when trigger tied to a distinctive trellis workflow. The main weakness is trigger-term naturalness, which leans toward process jargon over phrases a user would naturally say.

Suggestions

Broaden trigger terms with natural user phrasings such as "session summary", "session log", or "record what was done this session" in addition to the current process-oriented triggers.

Consider mentioning the deliverable artifact name (e.g. "journal entry") earlier so users searching for "journal" or "session notes" land on this skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Records completed work progress", "Captures session summaries, commit hashes", and "updates developer index files" — matching the multiple-specific-actions anchor rather than the single-action level 2.

3 / 3

Completeness

Explicitly answers both what (records progress, captures summaries/commit hashes, updates index files) and when via the "Use when a coding session is complete, after the human has committed code, or to persist session knowledge..." clause, matching the level-3 anchor; it is not level 2 because the trigger is explicit rather than implied.

3 / 3

Trigger Term Quality

Triggers like "coding session is complete", "after the human has committed code", and "persist session knowledge" are relevant but process-oriented and miss common user variations (e.g. "session summary", "session log"), so this sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The trellis-specific journaling niche ("to .trellis/workspace/ journal files", developer index files) with distinct commit-after-testing triggers makes conflict with other skills unlikely, matching the clear-niche anchor.

3 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhukunpenglinyutong/desktop-cc-gui
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.