kanitmann01/spirit-of-the-law
.cursor/skills/spirit-of-the-law/SKILL.md
Deep investigative analysis that challenges assumptions and uncovers hidden patterns in tournament data. Use when exploring non-obvious questions, testing common beliefs, or running targeted statistical investigations that the standard pipeline does not cover.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add kanitmann01/TitanTale-Analytics spirit-of-the-lawInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 8:37 PM179.6s1 file scanned
SKILL.md
- name:
- spirit-of-the-law
- description:
- Deep investigative analysis that challenges assumptions and uncovers hidden patterns in tournament data. Use when exploring non-obvious questions, testing common beliefs, or running targeted statistical investigations that the standard pipeline does not cover.
Spirit of the Law
Scope
Question-driven investigative analysis on data/ CSVs. Every analysis starts as
a testable question, is validated empirically, and is explained accessibly.
Does NOT duplicate work already in STATS_REPORT.md or ANALYTICAL_BRIEF.md.
Analytical Principles
- Frame every analysis as a testable question -- not a label.
- State the hypothesis before running any test.
- Always include: question, method (plain English + formal test name), key numbers, verdict.
- Verdict categories: CONFIRMED / BUSTED / INCONCLUSIVE (with confidence level).
- If a finding contradicts conventional expectations, flag it explicitly.
- Explain statistical methods accessibly -- one sentence of plain English for every formal test.
- Never duplicate analysis already in
STATS_REPORT.mdorANALYTICAL_BRIEF.md.
Workflow
- Read
ANALYTICAL_BRIEF.mdandSTATS_REPORT.mdto know what is already covered. - Run
spirit_of_the_law_analysis.py(or individual investigation functions). - Each investigation: state question -> hypothesis -> method -> key numbers -> verdict.
- Output:
SPIRIT_FINDINGS.md(report),assets/spirit/(charts),data/spirit/(derived CSVs).
Investigation Catalog
| # | Name | Question | |---|------|----------| | 1 | Snowball Effect | Does winning game 1 predict winning the series? | | 2 | Draft Order Advantage | Does picking first confer a measurable edge? | | 3 | Fatigue Factor | Does performance decay across a series? | | 4 | Comfort Picks vs. Wild Cards | Do players win more on their most-played civs? | | 5 | Clutch Factor | Who over/underperforms in deciding games? | | 6 | One-Sided Civ Matchups | Which civ pairings are most imbalanced? | | 7 | Map Specialists | Which players over/underperform on specific maps? | | 8 | Upset Probability | Do underdogs win more often than ELO theory predicts? | | 9 | Tempo Control | Does controlling game length correlate with winning? | | 10 | Meta Evolution | How do civ picks shift as tournament stakes increase? |
Output Contract
SPIRIT_FINDINGS.md-- structured report, one section per investigation.assets/spirit/-- one visualization per investigation that warrants a chart.data/spirit/-- derived CSVs (e.g.civ_matchup_matrix.csv,player_map_affinity.csv).
Token Discipline
- Read data via
.head(),.shape,.describe()only. Never dump full CSVs. - Read existing reports only to check for overlap; do not re-analyze covered ground.
Related Skills
kanitmann01/technical-writer
testing
VerifiedTrustedCommunity
Write and maintain concise documentation, runbooks, and release notes. Use when creating or updating docs, README files, schema docs, or release summaries.
SKILL.mdUpdated Apr 16, 2026
kanitmann01/qa-reviewer
development
VerifiedTrustedCommunity
Validate behavior, error handling, edge cases, and regression risk. Use when reviewing code changes, testing features, or checking for regressions before merging.
SKILL.mdUpdated Apr 16, 2026
kanitmann01/project-manager
data-ai
VerifiedTrustedCommunity
Scope work into tasks, assign owners, track progress, and maintain acceptance criteria. Use when planning sprints, breaking down features, or reviewing project status.
SKILL.mdUpdated Apr 16, 2026
kanitmann01/performance-optimizer
testing
VerifiedTrustedCommunity
Audit and improve loading speed, rendering, bundle size, caching, and token efficiency. Use when investigating slow pages, large bundles, or excessive context usage.
SKILL.mdUpdated Apr 16, 2026