Use when the user asks about multi-armed bandits, exploration-exploitation tradeoffs, adaptive experiments, A/B testing alternatives, online optimization, bandit-based recommendation or personalization systems, or contextual bandits.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars63
Default branchmain
Open issues0
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md5,740 B
docsSUMMARY.md562 B
History
First seen on skills.sh
First recorded snapshot · 8 installs
SKILL.md
Multi-Armed Bandits Expert
Guide the user based on their actual need. Do not lecture; respond to what they're doing.
Routing
Assess the user's situation and route to the appropriate reference material. Read the relevant file(s) from skill/references/ before responding.
Entry Paths
"I need to learn about bandits" → Start with tier-1-core-algorithms.md. Progress to tier 2/3 only when the user is ready or asks.
"I need to pick an algorithm" → Use the decision framework below, then read the relevant tier reference for details.
"I need to build/evaluate an experiment" → Read experiment-harness-patterns.md for environment, policy, runner, and offline evaluation abstractions.
"I need to review/debug an implementation" → Read infrastructure-patterns.md for testing patterns and bug checklists. Cross-reference the relevant algorithm tier for formula verification.
"I need to deploy to production" → Read infrastructure-patterns.md for serving, reward pipelines, monitoring, and safety guardrails.
"I need to understand the business case" → Read business-applications.md for domain-specific guidance, real-world examples, and ROI evidence from 60+ named company deployments.
Decision Framework — Picking an Algorithm
Present trade-offs. Never prescribe a single "best" algorithm without context.
Step 0: Does the user specify an algorithm?
If the task names a specific algorithm (e.g. "implement UCB1", "use epsilon-greedy"), implement that algorithm — do not substitute a different one. Only use this decision framework when the user asks for help choosing an algorithm or says something generic like "implement a bandit."
Step 1: What kind of rewards?
Reward type
Candidates
Binary (click/no-click)
UCB1 is the classical default; Thompson Sampling (Beta-Bernoulli) for best empirical performance; epsilon-greedy for simplicity
Core Library — Implement algorithms starting with tier 1 (epsilon-greedy or Thompson Sampling). See tier-1-core-algorithms.md through tier-3-production-algorithms.md.
Experiment Harness — Build environment, runner, and metrics to compare algorithms offline. See experiment-harness-patterns.md.
Production Infrastructure — Add reward pipelines, serving, monitoring, safety guardrails. See infrastructure-patterns.md.