Skip to content
Back to skills

Dfs Lineup Building

ASecurity

DFS lineup workflow — site rules first, projections with stated sources, deterministic optimisation via optimize_lineup, stacking/ownership as explicit judgment.

  • 6 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 2, 2026
ai-agents

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add DanielTomaro13/sportsdata-agents --skill dfs_lineup_building --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dfs Lineup Building?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dfs Lineup Building
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/danieltomaro13-dfs-lineup-building/badge)](https://www.skillsdirectory.com/skills/danieltomaro13-dfs-lineup-building)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dfs_lineup_building
description: DFS lineup workflow — site rules first, projections with stated sources, deterministic optimisation via optimize_lineup, stacking/ownership as explicit judgment.
triggers: [lineup, dfs, daily fantasy, draftkings, fanduel lineup, salary cap, optimise lineup, optimize lineup, fantasy team]
---
# DFS lineup building

Build daily-fantasy lineups: projections in, optimal lineup out — with the
judgment calls made explicit.

## Before optimising, establish (ask the user what you can't infer)
- **Site + contest rules**: roster slots, salary cap, scoring system. They differ
  (DraftKings/FanDuel/local AU sites); never assume.
- **Projection source**: the user's numbers, or build them from stats (per-game
  averages adjusted for opponent/pace/minutes). State which you used.
- **Contest type**: cash games want the highest floor (consistent scorers); GPP
  tournaments want ceiling + leverage (lower-owned players whose upside separates
  you from the field).

## Using `optimize_lineup`
- Pass EVERY candidate player with `positions`, `salary`, `projection` — the tool
  does all the math (deterministic beam search; near-optimal).
- `locked` forces players in (the user's picks or a stack); `excluded` removes
  injured/benched players. Re-run with different locks to compare builds.
- Multi-position eligibility matters: pass all listed positions; "G"/"F"/"UTIL"
  slots accept their families automatically.

## Judgment the optimiser does NOT make (you do, and say so)
- **Stacking**: correlated players (QB+WR, same-team hitters) raise ceiling for
  GPP — lock the stack, optimise the rest.
- **Late swap / news**: confirm lineups against the latest scratchings/injury
  news before presenting; flag any player whose status is uncertain.
- **Ownership leverage**: in GPP, an equal-projection pivot at lower ownership
  is usually the better tournament play.

## Honesty rules
- Projections are estimates; report the lineup's projected points as a point
  estimate, not a promise.
- Always state the slots/cap/scoring you optimised for, and the source of every
  projection. Advisory only.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.