메뉴
Use when the task involves constructing or optimizing a college baseball batting order, evaluating lineup balance, building platoon splits for lineup decisions, or generating a lineup card with sabermetric rationale.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Read the BSI Conference Power Index correctly. Interpret strength-of-schedule adjusted conference rankings, cross-conference comparisons, and how SOS adjustments change the story. Use when comparing programs across different conferences, explaining why a team's record alone doesn't tell the full story, or when doing postseason bracket projection. Pairs with bsi_get_conference_power_index from the cbb-sabermetrics plugin.
Interpret advanced college baseball metrics (wOBA, wRC+, FIP, ERA-, BABIP, ISO, K%, BB%) correctly in context. Use when explaining a player's or team's advanced stats, when comparing programs, when translating raw numbers into analytical conclusions, or when converting a leaderboard into a scouting takeaway. Pairs with bsi_get_team_sabermetrics, bsi_get_player_stats, and bsi_get_leaderboard from the cbb-sabermetrics plugin.
Texas Longhorns baseball intelligence for scouting reports, game analysis, roster evaluation, SEC positioning, player development, historical comparisons, NIL efficiency, and editorial content. Use when the user wants Texas-specific college baseball analysis that combines program doctrine with live MCP data from the cbb-sabermetrics plugin. For current stats, standings, and performance claims, fetch MCP tools before stating facts.
Use when the task involves ingesting, normalizing, storing, or processing college baseball game data — including box scores, play-by-play events, lineup data, and pitching logs — from NCAA stats, Baseball Reference, BSI's pipeline, or manually entered game sheets.
Use when the task involves evaluating a college baseball pitcher or pitching staff — including pitch-mix analysis, sequencing strategy, matchup scouting, platoon splits, and role recommendations (starter vs. reliever vs. closer).
Use when the task involves computing, interpreting, or displaying advanced baseball statistics for college teams or players. Covers rate stats, context-neutral metrics, park and era adjustments (where applicable in NCAA), and narrative generation from raw numbers.
| name | lineup-optimizer |
| description | Use when the task involves constructing or optimizing a college baseball batting order, evaluating lineup balance, building platoon splits for lineup decisions, or generating a lineup card with sabermetric rationale. |
Use this skill when the goal is to produce an analytically grounded batting order recommendation or evaluate an existing lineup's structural strengths and weaknesses. The output should be directly useful to a coaching staff or a content team building a pre-series analysis piece.
Before building or evaluating a lineup, establish:
Lineup decisions are context-specific. The optimal order for Friday's lights-out RHP is not the same as for Sunday's lefty with a low K rate.
| Slot | Primary Job | Desired Profile |
|---|---|---|
| 1 | Get on base, set the table | High OBP (.380+), K rate < 20%, speed |
| 2 | Advance runners, make contact | Best bat control, OBP + contact; can have power |
| 3 | Drive in runs, best overall hitter | Highest wRC+, solid OBP, gap-to-gap power |
| 4 | Drive in runs, most power | ISO > .200, walks, does not need speed |
| 5 | Secondary run producer | ISO > .160, walks, protects the 4-hole |
| 6 | Contact, depth | OBP-oriented, low strikeout rate |
| 7 | Balance or platoon advantage | Matchup-dependent |
| 8 | Weakest bat on the day | Minimize exposure, get on base to lead off next inning |
| 9 | Varies by philosophy | Traditional: weakest bat. Modern: second leadoff type with OBP |
Recommend the modern approach when the team has a capable OBP bat with modest power stuck outside the top 6. Flag if the coach has historically preferred traditional construction.
When wOBA data is available, sort players by wOBA descending. Then apply these adjustments:
When facing a LHP starter:
When facing a RHP starter:
Minimum threshold to make a platoon start decision: 50 career PA vs. that handedness, or a clear historical trend across two seasons.
When generating a lineup card recommendation, use this structure:
Lineup vs. [Opponent], [Date], [LHP/RHP: Starter Name]
1. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
2. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
3. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
4. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
5. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
6. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
7. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
8. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
9. [Name], [POS], [B/T] | OBP .XXX | wRC+ XXX | Note
SP: [Name], ERA X.XX / FIP X.XX
Rationale: [2–3 sentence explanation of the key slot decisions]
Keep the rationale focused on the non-obvious choices — the slot 2 selection, a platoon start, or a modern slot 9 choice. Do not explain every slot.
When building or evaluating a UT Austin lineup specifically: