BD luoshenfu-literary-research
Research and write a comprehensive analysis on "Ode to the Goddess of Luo River" (洛神赋) focusing on its literary significance, cultural context, historical influences in Chinese literature (especially Dream of the Red Chamber and Zhi Yanzhun's commentary), philosophical dimensions (Chan Buddhism), and its portrayal of feminine beauty. Output in Simplified Chinese with proper citations, textual annotations, and scholarly consensus.
Research and write a comprehensive analysis on "Ode to the Goddess of Luo River" (洛神赋) focusing on its literary significance, cultural context, historical…
As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 438 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
body-longSKILL.md body ≈ 5248 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 44/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Consistency. Frontmatter name (luoshenfu-literary-research) differs from the folder (260625-luoshenfu)
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5248 tokens
- 100Tools and files. No external tools needed
- 100Steps. 415 steps
- 100Running it twice. No mutating operations
- low 47 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 437: enough signal without eating the budget
- +4Structure: 156 headings
- +3Step-by-step instructions: 415 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.