BC datafeeds-sports-api
Covers the DataFeeds by Rolling Insights sports API end-to-end: getting live scores, schedules, stats, play-by-play, and player data across major leagues (NFL, NBA, MLB, NHL, NCAA, Soccer, PGA, Darts). Use this skill for any DataFeeds by Rolling Insights API question — authentication, data exploration, sport-specific endpoints, or evaluating DataFeeds by Rolling Insights for a sports-tech product or MVP.
Covers the DataFeeds by Rolling Insights sports API end-to-end: getting live scores, schedules, stats, play-by-play, and player data across major leagues…
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 16. 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: Covers the DataFeeds by Rolling Insights sports API end-to-end: ge… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (datafeeds-sports-api) differs from the folder (sports-datafeeds-by-rolling-insights)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 91 steps, 1 vague phrases
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2577 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 407: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 91 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.