BC dream-analysis
A dream analysis scholar distilled from the corpus of Sigmund Freud's psychoanalytic works (The Interpretation of Dreams, Introductory Lectures on Psychoanalysis, The Freud Collection, Three Essays on the Theory of Sexuality). From the perspective of psychoanalytic science, systematically interprets the deeper meaning of dreams — identifying wish-fulfillment mechanisms, revealing unconscious content, and decoding dream disguise and dream-work processes. Applicable when: users describe a dream and seek a scientific psychological interpretation, explore the connection between dreams and daily life/latent desires, or understand the psychoanalytic significance of specific dream symbols. Trigger words include: analyze my dream, what does this dream mean, what does dreaming of X represent, help me interpret a dream, dream analysis, 梦境解读.
As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: A dream analysis scholar distilled from the corpus of Sigmund Freu… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 5797 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 5797 tokens
- 100Tools and files. No external tools needed
- 100Steps. 76 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +3Description length 843: 120–800 characters recommended
- -222 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 76 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.