parthakker/nfl-analytics

Local NFL analytics platform: DuckDB warehouse (2007+), Streamlit dashboard, AI analyst via MCP, Kalshi market tracker, auto-updating data & news

0Stars on the repository
14Mods indexed here, across every type
4d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

health-check

01

parthakker/nfl-analytics

Skill Claude CodeCodex

Nightly project health run — data audit, warehouse+api tests, smoke, log triage, freshness check. Writes docs/healthreport.md and one line to logs/health.log.

0 4d ago A 41 tokens original MIT

new-analysis

02

parthakker/nfl-analytics

Skill Claude CodeCodex

Answer an NFL analytics question with reproducible SQL — the standard analysis workflow with citations and sanity checks.

0 4d ago A 23 tokens original MIT

new-page

03

parthakker/nfl-analytics

Skill Claude CodeCodex

Scaffold a new Jarvis page end-to-end (router, client, page, nav, tests). Use when adding a page/tab/section to the web app.

0 4d ago A 37 tokens original MIT

new-view

04

parthakker/nfl-analytics

Skill Claude CodeCodex

Add a derived warehouse view properly (SQL, dictionary, invariant test, catalog). Use when creating or materially changing a v view.

0 4d ago A 30 tokens original MIT

rebuild

05

parthakker/nfl-analytics

Skill Claude CodeCodex

Rebuild the warehouse and views from already-downloaded data, then verify.

0 4d ago A 18 tokens original MIT

release

07

parthakker/nfl-analytics

Skill Claude CodeCodex

Commit ritual — test, build, docs check, conventional commit, push.

0 4d ago A 17 tokens original MIT

warehouse-queries

08

parthakker/nfl-analytics

Skill Claude CodeCodex

Schema, join keys, gotchas and canonical query patterns for nfl.duckdb. Load before writing any non-trivial SQL against the warehouse — table grains, view catalog, cross-era rules, and the traps that silently corrupt results.

0 4d ago A 51 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: