session-log

Write a durable session log capturing completed work, findings, open questions, and next steps. Use when the user asks to log progress, save session notes, write up what was done, or create a research diary entry.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

An extremely lean, well-structured body for a simple wrapper skill: it names the exact command to run, the output location, and one useful anti-pattern to avoid, with no padding. It fully meets the simple-skill exceptions for workflow clarity and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Three lean sentences with no padding or explanation of concepts Claude already knows; the only non-obvious guidance (do not read a relative prompt-template path) earns its place. Every token contributes.	5 / 5
Actionability	Gives a concrete, copy-paste-ready command ('Run the `/log` workflow') plus the explicit output location ('notes/session-logs/'); for a single-action skill the one command unambiguously covers the common case.	5 / 5
Workflow Clarity	A simple single-task skill whose single action is unambiguous; no destructive or batch operation is involved, so the simple-skill exception applies and no validation checkpoint is required.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references; the body is well-organized with a heading and clearly separated guidance and output note, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	20 / 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.

A strong description that clearly states the capability and provides explicit, natural-sounding trigger guidance in third person. It is specific and complete with only minor gaps in action breadth and overlap risk.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Write a durable session log') and enumerates specific captured categories ('completed work, findings, open questions, and next steps'), giving several specific actions with only minor coverage gaps; not a 5 because the actions are content categories rather than a comprehensive list of distinct operations.	4 / 5
Completeness	Explicitly answers both 'what' ('Write a durable session log capturing completed work, findings, open questions, and next steps') and 'when' ('Use when the user asks to log progress, save session notes, write up what was done, or create a research diary entry') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides several natural phrases users would say ('log progress, save session notes, write up what was done, ... research diary entry'); good coverage with synonyms but a few common variations missing, so it sits just below the comprehensive-coverage anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a fairly distinct niche (session logs / research diary) with specific triggers and low conflict risk; not a 5 because it could still mildly overlap with general note-taking skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: companion-inc/feynman
Path: skills/session-log/SKILL.md
Commit: 95c51d9

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.