transcript-saver
Save and export the current Claude Code session as a shareable HTML transcript. Use this skill when the user asks to save, export, archive, or publish their current Claude Code conversation or session. Triggers on phrases like "save this transcript", "export this session", "create a transcript", "archive this conversation", "publish to gist", or "share this session". Wraps Simon Willison's claude-code-transcripts tool for in-session use.
86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It clearly states what the skill does (save/export Claude Code sessions as HTML), explicitly defines when to use it with a comprehensive list of trigger phrases, and is distinctive enough to avoid conflicts with other skills. The reference to the underlying tool adds helpful context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Save and export', 'shareable HTML transcript', and mentions wrapping a specific tool (Simon Willison's claude-code-transcripts). Uses proper third person voice throughout. | 3 / 3 |
Completeness | Clearly answers both what ('Save and export the current Claude Code session as a shareable HTML transcript') and when ('Use this skill when the user asks to save, export, archive, or publish...') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'save', 'export', 'archive', 'publish', 'transcript', 'session', 'conversation', 'publish to gist', 'share this session'. These are all phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically for Claude Code session transcripts, not general document saving. The mention of 'claude-code-transcripts tool' and specific context of 'Claude Code conversation' makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable commands for saving Claude Code transcripts with good examples and a complete command reference. However, it's somewhat verbose with explanatory content about how the underlying tool works, and could benefit from tighter organization with validation checkpoints for the gist publishing workflow.
Suggestions
Remove or significantly trim the 'How It Works' section - Claude doesn't need to know the internal mechanics of the wrapped tool
Add a validation step before gist publishing: 'First verify gh is authenticated: `gh auth status`'
Move the Command Reference and Troubleshooting to separate files and link to them from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation like 'How It Works' section explaining what the underlying tool does, which Claude doesn't need to know to use the skill. The 'Important Notes' section also contains some padding. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear options and flags. The Quick Start section is copy-paste ready, and the Command Reference gives complete option documentation. | 3 / 3 |
Workflow Clarity | For a single-command tool this is adequate, but the workflow for gist publishing lacks validation steps (e.g., checking if gh is authenticated before attempting). The troubleshooting section helps but validation should be in the main workflow. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file when the Command Reference and Troubleshooting could be separate references. The 'How It Works' section adds bulk that could be omitted or linked. | 2 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.