BF cross-material-consistency-auditor
This skill should be used when two or more materials on the same topic or event need to be compared for cross-material consistency before publication. It identifies mismatched numbers, product names, fact wording, terminology, source attributions, structural promises, and cross-platform expression drift across articles, press releases, slide decks, web pages, white papers, and social posts. It produces a diff matrix with severity ratings and recommended unified wording, without modifying originals. Trigger keywords: 口径审计, 跨材料核对, 多平台一致性, 口径不一致, consistency audit, cross-material check, PR vs 稿, 初稿 vs 通稿, multi-platform review, fact drift.
This skill should be used when two or more materials on the same topic or event need to be compared for cross-material consistency before publication.
As a process F 53/100 · Will not run — References files that are not bundled: scripts/product-terms.txt
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: 9. 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: This skill should be used when two or more materials on the same t… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: scripts/product-terms.txt - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en" - note
frontmatter-keyunknown frontmatter key "not_for" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: scripts/product-terms.txt
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (cross-material-consistency-auditor) differs from the folder (cross-material-consistency-auditor-skill)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 1326 tokens
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)
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 644: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 56 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.