steamer
蒸笼：蒸馏任何人的叙事入口——对齐数字永生引擎，强调生活化「蒸」与公开方法论顾问场景；委托上级 kit/personas 执行。
32
28%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./steamer-skill/SKILL.mdQuality
Discovery
7%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 description is heavily metaphorical and uses abstract, jargon-laden language that fails to communicate concrete capabilities or trigger conditions. It lacks a 'Use when...' clause, lists no specific actionable tasks, and contains no natural keywords a user would employ. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.
Suggestions
Replace metaphorical language ('数字永生引擎', '叙事入口') with concrete, specific actions the skill performs (e.g., 'Summarizes a person's life narrative', 'Creates structured biographical profiles').
Add an explicit 'Use when...' clause with natural trigger terms a user might say, such as 'Use when the user asks for biographical distillation, life story summarization, or personal narrative structuring'.
Clarify the delegation model ('委托上级 kit/personas 执行') by explaining what the skill itself does versus what it delegates, so Claude understands the skill's role in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses highly abstract and metaphorical language ('蒸馏任何人的叙事入口', '对齐数字永生引擎'). There are no concrete, actionable capabilities listed — phrases like 'distill narrative entry points' and 'align digital immortality engine' are vague buzzwords rather than specific actions. | 1 / 3 |
Completeness | The 'what' is obscured by metaphorical language and the 'when' is entirely absent — there is no 'Use when...' clause or equivalent explicit trigger guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The keywords used ('蒸笼', '蒸馏', '数字永生引擎', '叙事入口') are highly specialized jargon or metaphorical terms that no user would naturally say when seeking help. There are no common, natural trigger terms that would help Claude match this skill to a user request. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so niche and idiosyncratic that it is unlikely to conflict with other skills, but this is due to its obscurity rather than clear, well-defined boundaries. It's somewhat distinctive by virtue of being unusual, but not in a useful way. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill establishes a clear narrative wrapper ('Steamer') around an existing digital immortality engine and correctly delegates to shared tooling rather than forking. However, it suffers from over-reliance on external references without providing enough standalone actionable content—Phases 3–6 are completely opaque without reading the root SKILL.md. The workflow lacks validation checkpoints and the meta-instructions at the top add redundancy.
Suggestions
Add a one-line summary for each of Phases 3–6 inline so the skill is understandable without reading the root SKILL.md (e.g., 'Phase 3: Dimension extraction — run `python3 kit/immortal_cli.py extract ...` per dimension').
Insert explicit validation/checkpoint steps between phases (e.g., 'After Phase 2, verify collected materials with `python3 kit/immortal_cli.py validate ...` before proceeding').
Remove or condense the '复制给 AI' preamble—most of its content is repeated in the '路径约定' and '操作顺序' sections.
Provide at least one concrete end-to-end example command sequence for a public-figure scenario to make the skill copy-paste actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundant explanations (e.g., repeating path conventions multiple times, the '复制给 AI' preamble restates things the body covers). The Chinese text is reasonably tight but could be tightened further by removing the meta-instructions at the top. | 2 / 3 |
Actionability | Provides some concrete guidance (CLI commands, file paths, phase sequence) but Phases 3–6 are entirely delegated to another file with no inline summary. The skill relies heavily on external references without giving enough standalone executable detail—no concrete code examples or copy-paste-ready commands beyond the generic CLI pattern. | 2 / 3 |
Workflow Clarity | The Phase 0–6 sequence is clearly listed and ordered, but Phases 3–6 are a black-box reference to the root SKILL.md with zero inline detail. There are no explicit validation checkpoints or error-recovery feedback loops between phases, and the self-check list at the end is minimal and not integrated into the workflow steps. | 2 / 3 |
Progressive Disclosure | References to external files (root SKILL.md, personas/, recipes/, FOR_AI.md) are present and one-level deep, which is good. However, the signaling is inconsistent—some references use relative links while others just name paths—and the top '复制给 AI' section creates confusion about entry points. The delegation of Phases 3–6 entirely to another file without even a one-line summary per phase hurts navigability. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- agenmod/immortal-skill
- Commit
cdab91b
- 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.