AC football-match-performance-analysis
Explain how a completed football (soccer) match unfolded using SofaScore event statistics, incidents, lineups, and match context. Use for requests like “why did this side control the match?” or “write a post-match statistical brief”; use multi-sport-match-research for reconciling Flashscore and LiveScore records.
Explain how a completed football (soccer) match unfolded using SofaScore event statistics, incidents, lineups, and match context.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, progress reporting
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-usescripts/crawlora.sh:12Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded): "${CRAWLORA_API_KEY:?Set CRAWLORA_API_KEY first — get a free key at https://crawlora.net?utm_source=…&utm_medium=…&utm_campaign=…"quoted -
low Exfiltration
net-credential-usescripts/crawlora.sh:92Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)printf 'header = "x-api-key: %s"\n' "$CRAWLORA_API_KEY" >"$curl_config"
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 58/100
- 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
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 937 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 314: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.