BF translation-assistant
Professional multilingual translation with domain-specific terminology handling for finance, law, and technology. Use when the user needs to: (1) translate content between Chinese and English (or other language pairs), (2) preserve formatting in Markdown, tables, code blocks, or structured documents, (3) produce bilingual (side-by-side) output for comparison, (4) ensure technical/legal/financial term consistency, (5) check translation quality or standards compliance. Primary supported pair: zh-CN ↔ en. Additional pairs on request.
Professional multilingual translation with domain-specific terminology handling for finance, law, and technology.
As a process F 51/100 · Will not run — References files that are not bundled: url, alt
How to improve
- The text references files that are not there: add them or drop the references.
- 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: Professional multilingual translation with domain-specific termino… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: url - warning
missing-refreference to a missing file: alt - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: url, alt
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (translation-assistant) differs from the folder (zcx-translation-assistant)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 39 steps
- 100Execution cost. Instruction body is 1880 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- -225 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 536: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.