distill-protocol
蒸馏协议：为个人数字资料生成人类可读条款与机器可读 manifest；戏称「牛马保护法」仅为传播梗，非法律意见。
43
45%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./distill-protocol-skill/SKILL.mdQuality
Discovery
17%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a niche concept (distillation protocol for personal digital data) and mentions two outputs, but it is written in highly specialized jargon without natural trigger terms users would employ. It lacks an explicit 'Use when...' clause, making it very difficult for Claude to know when to select this skill. The disclaimer about '牛马保护法' consumes space without aiding skill selection.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms such as 'personal data rights', 'data usage terms', 'digital asset protection', 'AI training opt-out', or equivalent Chinese terms users would actually say.
Replace or supplement the jargon '蒸馏协议' with plain-language descriptions of what the skill does, e.g., 'Generates terms-of-use documents and machine-readable manifests that define how personal digital content may be used for AI training or data mining.'
Remove or minimize the '牛马保护法' disclaimer from the description field—move it to the skill body instead—and use the freed space to list specific actions and trigger scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('蒸馏协议' / distillation protocol for personal digital data) and mentions two concrete outputs ('人类可读条款' human-readable terms and '机器可读 manifest' machine-readable manifest), but does not list multiple specific actions beyond generation of these two artifacts. | 2 / 3 |
Completeness | While there is a partial 'what' (generate human-readable terms and machine-readable manifest for personal digital data), there is no explicit 'when' clause or trigger guidance. The note about '牛马保护法' being a meme and not legal advice is a disclaimer, not a usage trigger. Missing 'Use when...' caps this at 2 per guidelines, and the 'what' itself is also vague, so score is 1. | 1 / 3 |
Trigger Term Quality | The description uses highly specialized jargon ('蒸馏协议', 'manifest', '牛马保护法') that users would almost never naturally say when requesting this kind of skill. There are no common natural-language trigger terms like 'data rights', 'personal data policy', 'terms of use', or similar phrases a user might actually type. | 1 / 3 |
Distinctiveness Conflict Risk | The niche topic of generating distillation protocols for personal digital data is somewhat distinctive, but the description is vague enough that it could overlap with general document generation, policy writing, or legal drafting skills. The unique terminology helps somewhat but is not well-defined enough to clearly carve out a niche. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill that provides clear, actionable guidance for generating distill protocol files. Its main strengths are the concrete CLI commands and the well-organized phase structure. The primary weakness is the lack of explicit validation/error-recovery steps after file generation, and some minor verbosity in disclaimers that could be tightened.
Suggestions
Add explicit validation steps in Phase 2-3: specify what to check in the generated LICENSE-DISTILL.md and manifest.json (e.g., verify owner name, tier, file paths) and what to do if the output is incorrect.
Consolidate the repeated disclaimer about '牛马保护法' into a single concise note rather than mentioning it in both '何时激活' and '重要声明' sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like the language selection rule and the repeated emphasis on the meme name disclaimer. The path conventions and multiple ways to run the script add slight redundancy. | 2 / 3 |
Actionability | Provides concrete, executable bash commands with specific flags and arguments. The tier table, phase-by-phase instructions, and copy-paste ready commands make this fully actionable. | 3 / 3 |
Workflow Clarity | The phases are clearly sequenced (0-5), but validation checkpoints are weak — Phase 2-3 only says 'check the generated files' without specifying what to validate or what to do if generation fails. For a file-generation workflow, explicit validation steps would be expected. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, references to template files and the aggregation entry point (FOR_AI.md), and appropriate use of a tier table. The skill is concise enough that no content needs to be split into separate files, and references are one level deep. | 3 / 3 |
Total | 10 / 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.