BD jimeng-prompter
Privacy-first universal prompt engineer for Jimeng AI (即梦) — Seedance 2.0 video + Seedream 4.0/4.5/5.0 image generation. v3.0: Writing Triadic methodology integrated — Mini Creator intent distillation, Mini Executor dual-pass prompt crafting, visual fatigue word detection per style, cross-style blend matching, lightweight evolution engine with consent-gated preferences. v3.0.1: PRIVACY.md, consent gates for evolution memory write/read, privacy notices. v3.1.0: Missing PRIVACY.md fix, 2026 visual fatigue word expansion.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5239 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 49/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 70Execution cost. Instruction body is 5239 tokens
- 100Tools and files. No external tools needed
- 100Steps. 78 steps
- 100Consistency. Name and required fields are in place
- low 19 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
- -244 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 524: enough signal without eating the budget
- +4Structure: 65 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (24 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.