BF universal-content-synthesizer
Intelligent universal content processor that reads ANY file format KIMI can handle, extracts meaningful information using optimal parsing strategies, and synthesizes new content based on user prompts. Automatically detects file types, handles errors gracefully, and produces structured outputs. Trigger: "process this file", "extract from", "summarize this", "analyze document", "create from file", "synthesize content".
As a process F 39/100 · Will not run — References files that are not bundled: URL
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: Intelligent universal content processor that reads ANY file format… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 10831 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: URL
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: URL
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (universal-content-synthesizer) differs from the folder (my-study-summarizer)
- 40Execution cost. Instruction body is 10831 tokens: crowds the task out of the window
- 60Steps. 431 steps, 6 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100Failures and branches. 3 branches, has a failure section
- 100Progress reporting. Reports progress
- low 16 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 420: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 431 items
- +3Output format is stated explicitly
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.