技能创建器
skill-creator
创建、改进和评估自定义技能,把专业流程转化为可重复使用的 AI 能力。
dispatch【数据与研究】Routes hockey analytics requests to the right 2-3 skills. Load this FIRST when a hockey data or analytics request comes in and you are unsure which skills to activate. Prevents loading all 28 skills when only 2-3 are needed. Also handles first-use persona detection.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
When a hockey analytics request comes in, match it to a pattern below. Load those skills. Don't load everything.
Default data tool: puckapi-tool -- covers most data needs. Load it alongside the relevant strategy skill unless the request specifically needs a different tool.
On first interaction, identify which path the user is on:
| Signal | Persona | Start With |
|---|---|---|
| "What games are tonight?" / exploring data | Explorer | game-lookup + puckapi-tool |
| "Help me build a model" / "I want to predict" | Builder | hockey-analytics + feature-engineering |
| "What are tonight's best bets?" / "Give me picks" | Daily User | daily-card + odds-explorer |
| "I have a model, is it any good?" | Validator | walk-forward-validation + probability-calibration |
| "I'm new to hockey analytics" | Learner | hockey-analytics + ai-hockey-workflow |
| "I'm new to betting" | New Bettor | odds-analysis + edge-detection |
game-lookup -- find games by date, team, seasonpuckapi-tool -- get_games, get_schedule endpointsteam-analysis -- standings, stats, rankings, SOSpuckapi-tool -- get_standings, get_team_statsplayer-scouting -- search, stats, comparison, NHLepuckapi-tool -- search_players, get_player_statsgoalie-analysis -- leaderboard, workload, xG-adjusted metricspuckapi-tool -- get_goalie_statsodds-explorer -- multi-book comparison, line movementpuckapi-tool -- get_odds, get_line_movementodds-analysisnl-to-query -- translate natural language to structured queriespuckapi-tool -- routes to appropriate endpointai-hockey-workflow for follow-up hypothesis testinghockey-analytics -- metric definitions, formulas, contextpuckapi-tool -- pull real data to demonstrateai-hockey-workflow -- prompt patterns, hypothesis testing, iterationdata-pipeline -- GitHub Actions, scheduling, model versioningpuckapi-tool for endpoint costs in automation budgetfeature-engineering -- rolling windows, leakage detection, shift(1)puckapi-tool -- historical data endpointshockey-analyticswalk-forward-validation -- temporal CV, anti-leakage, significance testingprobability-calibration for probability verificationmodel-building -- model selection, training, evaluationwalk-forward-validation -- correct evaluation methodfeature-engineering -- if features aren't built yetelo-engineering -- 5 variants, tuning, carryoverpuckapi-tool -- get_games for historical resultsprobability-calibration -- reliability diagrams, scaling methodsmodel-building firstodds-analysis -- conversion, devigging, no-vig linespuckapi-tool -- get_odds for real numbers to work withedge-detection -- EV calculation, Kelly sizing, CLVodds-explorer -- current market oddsprobability-calibration -- verify model probabilities firstbacktesting -- walk-forward backtest, strategy simulationpuckapi-tool -- historical odds (heavy credits)xg-model-building -- full xG pipeline from play-by-playhockey-analytics for xG concepttotals-modeling -- pace, goalie matchup quality, under biaspuckapi-tool -- get_odds for totals linesprop-modeling -- TOI projection, per-60 rates, matchup adjustmentplayer-scouting -- player datapuckapi-tool -- get_player_statswar-gar-decomposition -- RAPM ridge regression, component GARplayer-scouting -- player data for contextplayoff-simulation -- Monte Carlo, bracket simulationelo-engineering -- if rating system needed as inputpuckapi-tool -- remaining schedulegame-preview -- compound skill, loads data internallypuckapi-tool -- multiple endpoints (~34 credits)daily-card -- slate analysis, edge rankingsbet-tracker -- prediction logging, CLV, significancebacktesting for auditvisualization -- chart type selection, code generationdocs/hockey-glossary.mddocs/betting-glossary.mddocs/tool-routing.mddocs/season-logic.mdSingle-skill requests don't need dispatch. If someone says "devig these odds: +150 / -180" -> just load odds-analysis.