CF multi-source-synthesis
Integrate multiple source findings into an attributed synthesis or comparison. Use for combine these summaries, synthesize results, merge findings or multi-source analysis. Preserve claim-level provenance, coverage, qualifiers, conflicts and uncertainty rather than repeatedly compressing narrative summaries.
Integrate multiple source findings into an attributed synthesis or comparison.
As a process F 33/100 · No process to follow — References files that are not bundled: ../summarizer/references/fidelity-rules.md, ../summarizer/references/execution-contract.md, ../summarizer/references/evidence-record.md
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../summarizer/references/fidelity-rules.md - warning
missing-refreference to a missing file: ../summarizer/references/execution-contract.md - warning
missing-refreference to a missing file: ../summarizer/references/evidence-record.md
Process rating: all ten parameters 33/100
- 0Tools and files. 3 referenced file(s) missing: ../summarizer/references/fidelity-rules.md, ../summarizer/references/execution-contract.md, ../summarizer/references/evidence-record.md
- 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
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 760 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 309: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.