auction-first-price-shading
Computes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
What this skill does
# Auction First-Price Shading
## Table of Contents
- [Example](#example)
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
## Example
**Scenario**: Domain-neutral sealed-bid auction. A bidder must submit a blind bid for an item whose private value to them is 28 units of budget currency. Six other bidders are expected to compete. Values across bidders look roughly uniform. The bidder is mildly risk-averse (0.2) and has 89 units of budget remaining.
**Inputs**:
- `true_value = 28`
- `n_bidders_estimate = 6`
- `value_distribution = "uniform"`
- `risk_aversion = 0.2`
- `budget_remaining = 89`
**Core computation**:
```
shade_fraction_base = (N - 1) / N = 5 / 6 = 0.833
shaded_bid_base = true_value x shade_fraction_base = 28 x 0.833 = 23.33
```
**Risk-aversion adjustment** (raise the bid toward true value to boost win probability):
```
shade_fraction' = shade + risk_aversion x (1 - shade) x 0.4
= 0.833 + 0.2 x (1 - 0.833) x 0.4
= 0.833 + 0.0133
= 0.847
shaded_bid' = 28 x 0.847 = 23.72
```
**Budget + safety cap**:
```
cap = min(shaded_bid', 0.9 x true_value, budget_remaining)
= min(23.72, 25.2, 89)
= 23.72 -> round to 24
```
**Output**:
- `shaded_bid = 24`
- `shade_fraction = 0.847`
- `rationale = "Uniform-values equilibrium shades to (N-1)/N = 0.833 at N=6. Mild risk aversion (0.2) nudges bid up to 0.847 of true value to raise win probability. Final bid capped below 0.9x true_value and well under budget. Expected to win against 5 rivals drawing values from a comparable uniform distribution."`
- `assumptions_flagged = ["uniform private-value distribution", "N=6 is an estimate, not observed", "risk_aversion=0.2 is a modeling choice"]`
## Workflow
Copy this checklist and track progress:
```
Auction Shading Progress:
- [ ] Step 1: Validate inputs (true_value > 0, 1 <= N <= 12, distribution known)
- [ ] Step 2: Compute base shade from (N-1)/N
- [ ] Step 3: Apply distribution adjustment (uniform / log-normal / empirical)
- [ ] Step 4: Apply risk-aversion adjustment
- [ ] Step 5: Apply budget and safety caps
- [ ] Step 6: Emit shaded_bid, shade_fraction, rationale, assumptions_flagged
```
**Step 1: Validate inputs**
Reject or flag bad inputs before computing. See [resources/template.md](resources/template.md#input-contract) for the full input contract.
- [ ] `true_value` is a non-negative number
- [ ] `n_bidders_estimate` is an integer, clamp to `[1, 12]`
- [ ] `value_distribution` is one of `"uniform"`, `"log-normal"`, `"empirical"`
- [ ] `risk_aversion` is in `[0, 1]` (default 0 if missing)
- [ ] `budget_remaining` is a non-negative number (if missing, treat as effectively infinite and flag)
**Step 2: Compute base shade from `(N-1)/N`**
For risk-neutral bidders drawing values from a uniform distribution on `[0, v_max]`, the symmetric Bayes-Nash equilibrium bidding strategy is `b(v) = v x (N-1)/N`. See [resources/methodology.md](resources/methodology.md#uniform-value-equilibrium-derivation) for the derivation.
- [ ] `shade_fraction = (N - 1) / N`
- [ ] Edge case `N = 1`: shade = 0, bid the minimum increment (monopsonist — no competition)
- [ ] `shaded_bid = true_value x shade_fraction`
**Step 3: Apply distribution adjustment**
Uniform values give the clean `(N-1)/N` rule. Real-world value distributions are often clustered (log-normal) or empirically lumpy. See [resources/methodology.md](resources/methodology.md#distribution-adjustment).
- [ ] If `"uniform"`: no adjustment; shade = `(N-1)/N`.
- [ ] If `"log-normal"`: values cluster around a mode with a long right tail. Shift shade toward `1 - 1/(N x spread)` where `spread >= 1` captures the coefficient of variation. Default `spread = 1.5` shifts shade up (bid closer to value) because rivals' values are less likely to be extreme.
- [ ] If `"empirical"`: distribution learned from prior auctions; pass through a shade-lookup table if available, otherwise fall back to the log-normal formula with spread inferred from observed history.
**Step 4: Apply risk-aversion adjustment**
Risk-averse bidders accept a smaller expected surplus in exchange for a higher win probability. They bid closer to true value (shade less). See [resources/methodology.md](resources/methodology.md#risk-aversion-adjustment).
- [ ] `shade_fraction' = shade + risk_aversion x (1 - shade) x 0.4`
- [ ] `risk_aversion = 0`: no change.
- [ ] `risk_aversion = 1`: shade moves 40 percent of the way from its base value to 1 (i.e., toward bidding true value).
- [ ] The 0.4 scaling factor caps the adjustment; it never closes the full gap because a fully-closed gap gives zero surplus.
**Step 5: Apply budget and safety caps**
The final bid is clamped three ways:
- [ ] `cap_value = 0.9 x true_value` — never pay more than 90 percent of what the item is worth; this preserves at least 10 percent expected surplus.
- [ ] `cap_budget = budget_remaining` — never bid more than available budget.
- [ ] `shaded_bid = min(raw_shaded_bid, cap_value, cap_budget)`.
- [ ] Flag in `assumptions_flagged` whenever a cap binds so downstream consumers know which constraint is active.
**Step 6: Emit outputs**
Return the four-field output:
- [ ] `shaded_bid` (number, rounded to the precision the caller expects — integers for most budget systems)
- [ ] `shade_fraction` (0-1, the effective shade actually used)
- [ ] `rationale` (one or two sentences explaining which rule applied and why)
- [ ] `assumptions_flagged` (string array — every assumption the downstream consumer may need to revisit)
Validate using [resources/evaluators/rubric_auction_first_price_shading.json](resources/evaluators/rubric_auction_first_price_shading.json). Minimum standard: weighted score of 3.5 or above.
## Common Patterns
**Pattern 1: Generic sealed-bid auction (uniform values, risk-neutral)**
- **When it applies**: Values are drawn from roughly the same distribution for all bidders, no unique information, no risk aversion.
- **Shade**: `(N-1)/N`. At N=2 shade to 50 percent. At N=6 shade to 83 percent. At N=8 shade to 87.5 percent.
- **Downstream examples**: Fantasy sports waiver auctions (FAAB) for private-value targets, sealed procurement bids, silent-auction pledges.
**Pattern 2: Clustered values (log-normal or empirical)**
- **When it applies**: Most bidders' valuations cluster around a shared estimate (common-value component), with a thin tail of outliers. Typical of well-known targets where public information narrows the spread of valuations.
- **Shade**: move toward `1 - 1/(N x spread)`. Higher spread means more disagreement and permits deeper shading. Low spread (tight cluster) means less room to shade — bidders must be near consensus to win.
- **Downstream examples**: FAAB bids on headline call-ups, prediction-market limit orders on well-priced contracts, M&A sealed-bid rounds with shared public data.
**Pattern 3: Risk-averse bidder**
- **When it applies**: The bidder values winning more than maximizing expected surplus — for example, a fantasy manager who must fill a lineup slot this week, or a procurement team that must secure supply.
- **Shade adjustment**: `shade' = shade + risk_aversion x (1 - shade) x 0.4`. Pushes the bid closer to true value.
- **Watch for**: never lets shade reach 1 (never bids true value), because that yields zero expected surplus. The cap at `0.9 x true_value` enforces this hard.
**Pattern 4: Budget-constrained bidder (corner solution)**
- **When it applies**: The unconstrained shaded bid exceeds `budget_remaining`. The bidder must either accept a lower win probability or forgo the auction.
- **Shade adjustment**: output equals `budget_remaining`, effective shade = `budget_remaining / true_value`. Flag that the budget constraint binds so downstream logic can decide whether to skip the auction or accept the lower probability.
- **Watch for**: If `budget_remaining < (N-1)/N x true_value`, the bidder is unRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".