Sundae Bar Logo
Past Challenge
Executive Presentation Strategy Skill
SBC35

Executive Presentation Strategy Skill

Overview

This skill teaches the agent to turn a messy bundle of data, findings, and requests into a tightly reasoned executive presentation storyline.

Given a strategic input (a prose brief, a data table, a bullet findings list, or an existing deck outline) together with an audience and a decision, a good result is a complete, structured output: a single governing thought that the evidence actually supports, a MECE argument tree with two to four branches, an action-title slide list where every headline is a complete so-what sentence, per-slide content specifications, and a self-check flag report.

The submission is a SKILL.md, with optional reference files the agent opens by name when SKILL.md directs it. Strong skills teach the agent a reasoning procedure it can apply to inputs it has never seen before: how to read footnotes before forming a claim, how to test headline flow, how to match a chart type to a claim rather than to data shape. Weak skills paste in template outlines or memorised slide structures that collapse the moment surface details change.

A skill built to memorise specific scenarios will not hold up as challenges evolve.

You submit a skill: a SKILL.md and, if you need them, reference files it points at. A fixed base agent loads it and answers all 7 scenarios with it, then returns a scored breakdown. The submission that holds the top of the leaderboard accrues on-chain emissions for as long as it stays first.

We are looking for skills that demonstrate good design and help the agent perform like a capable practitioner in this domain.

Requirements (7 Tests)

Your skill is tested across 5 capability types, with 7 scenarios in total. Every submission is evaluated against all 7 scenarios. There is no sampling, so consistent quality across every capability type counts.

CategoryOverviewTest cases
Type A: Contradiction handlingThis type tests whether the agent correctly identifies that the input evidence refutes the requested conclusion rather than silently building the requested storyline. The skill must teach the agent to surface the contradiction first, offer two governing thought options (one evidence-supported, one requester-preferred), and then storyline only the evidence-supported one unless the requester explicitly redirects.1
Type B: Existing deck repairThis type tests whether the agent can diagnose and improve a deck that already exists rather than rebuild from scratch. The skill must teach the agent to extract the implicit governing thought from the current outline, run a headline-flow test across the existing slide titles, and prefer reordering and retitling over wholesale reconstruction.1
Type C: Missing decision clarificationThis type tests whether the agent stops appropriately when the input contains no actionable decision or named audience, rather than inventing one and proceeding. The skill must teach the agent to issue a focused clarifying question and to offer two or more plausible decisions the data could plausibly serve, so the requester has concrete options to react to.1
Type D: Standard storyline with counter-evidenceThis type tests whether the agent builds a complete MECE argument tree that includes material counter-evidence rather than omitting inconvenient findings. The skill must teach the agent to construct two to four branches where each branch is a one-sentence claim citing specific input evidence, and to place counter-evidence inside the tree rather than suppressing it.1
Type E: Standard storyline with footnote effectsThis type tests whether the agent reads footnotes, unit labels, and period qualifiers before forming the governing thought, rather than skimming the headline numbers. The skill must teach the agent to compute relevant deltas, check whether notes materially change what the data shows, and produce a governing thought that reflects the footnote-adjusted picture rather than the surface reading.1

Surface details such as company names, metric labels, data values, and audience roles rotate across variants, while the underlying capability being tested remains the same.

Datasets

Available Datasets

When you submit, we run your skill through a standardised base agent provided by sundae_bar. The base agent is the same for every submission and is not supplied by you. It receives the challenge's test scenarios one at a time, calls the load_skill tool to read your SKILL.md and the list of your reference files, opens a reference with read_reference when your SKILL.md tells it to, and follows the skill to answer each scenario.

Same base agent, same tests, only the submitted skill changes. Scores therefore reflect the quality of your skill, not agent configuration: the agent's answers are only as good as the procedure your skill teaches.

Graders then score each answer for output quality, correct skill use, and gaming behavior, and the per-scenario scores are averaged into your challenge score.

What is public at open: the scenario inputs, the rubric, and the sha256 hash of the sealed reference set (the same scenarios with their reference outputs and grading notes). Validators grade against the sealed set; the hash on the challenge page is your proof that it cannot change while the challenge runs.

What you see while it runs: your total, a score for every scenario and every grader, and the written notes of the gate checks (dataset derivation, skill alignment, redundancy, novelty). The quality judges' written explanations are held back, because they describe the reference answer.

What is published when the challenge closes: the sealed reference set, every judge explanation, and the full validator outputs for every submission. Check the file against the published hash and re-run any evaluation yourself.

What you submit: a folder or a .zip with SKILL.md at the top level and an optional references/ folder. A single SKILL.md is also accepted. All files are the submission.

Limits: SKILL.md is at most 10,000 bytes and is always loaded. references/ holds up to 30 files, each at most 32,000 characters, 128,000 characters in total. Text formats only: .md, .txt, .json, .yaml, .yml and .csv. Lower-case file names using letters, digits, dots, dashes and underscores. The current values are published by the platform API at GET /api/v2/submissions/limits; the submission form reads them from there.

How references are read: the agent always sees SKILL.md plus a list of your reference file names. It opens a reference only when SKILL.md tells it to, by name. Each read is one harness step within a cap of 10 steps per scenario, and the file's text counts against the scenario's token budget of 30,000 tokens. A reference the agent never opens does nothing for the score.

Rejected at upload: HTML comments, images, scripts, hidden or invisible characters, nested archives, disallowed file types, and anything over a limit. Text addressed to the evaluators, or that tries to override instructions, is accepted but places the entry under review and scores zero.

Important: the base-agent harness is fixed at evaluation time and its available tools are load_skill, read_reference. You submit only skill files; you cannot supply your own agent, add tools, or alter the base agent's configuration.

Tip: write your skill as though you are onboarding a capable new hire who needs a procedure, not scripting a chatbot.

Evaluation Criteria

Each scenario is graded by an LLM judge. Final scores combine four graders and a set of deterministic penalties.

CriteriaWeight

Response quality

An LLM judge scores each response against a task-specific quality bar for this challenge: how correct, complete, and usable the output is on its own terms, independent of which procedure produced it.

30 %

Skill use

An LLM judge evaluates whether the agent's output actually followed the procedures your skill teaches, rather than freelancing or pretending to use the skill.

30 %

Scenario quality

An LLM judge evaluates how well each output meets the per-type quality bar, independent of whether your skill was followed. A reference good output anchors the judge's sense of the quality bar.

30 %

Output originality

A check that your skill drives genuine per-scenario reasoning rather than emitting near-identical, templated responses. Skills that reuse one canned output across scenarios lose credit here.

10 %

Evaluation applies deterministic penalties for moves that damage output quality, such as fabricating evidence not present in the input, writing topic-label slide titles instead of so-what sentences, or building the wrong output type for the recognised situation. Scenario scores roll up to capability-type averages, which combine into the final challenge score shown on the leaderboard.

Submission

How to submit

1
Login or create a sundaebar.ai account

Create an account and add your Bittensor wallet ID to your profile to earn alpha rewards in the challenge.

2
Review the requirements

Review the reference skills (good, mediocre, gaming) to understand the quality bar and calibration points.

3
Build your skill

Draft your SKILL.md (at most 10,000 bytes; it is always loaded) and, if the method needs them, put tables, templates and worked examples in reference files under references/. Tell the agent in SKILL.md which reference to open and when, by file name. Focus on teaching procedure rather than providing templates.

4
Test locally

Run your skill against the published scenario inputs and rubric to sanity-check output quality. The reference outputs are sealed until the challenge closes.

5
Submit via the platform

Submit through the sundae_bar challenge portal by uploading your skill folder, a .zip of it, or a single SKILL.md. The folder has SKILL.md at the top level and an optional references/ folder beside it.

6
Iterate

Review your scored breakdown (a score for every scenario and every grader, plus the gate checks' notes) and resubmit. The judges' written explanations are published when the challenge closes.

Constraints

Submission format: a folder or .zip with SKILL.md (YAML frontmatter with name and description, then a Markdown body) at the top level and an optional references/ folder. A single SKILL.md is also accepted.

Limits: SKILL.md at most 10,000 bytes. Up to 30 reference files, each at most 32,000 characters and 128,000 characters in total; text formats only (.md, .txt, .json, .yaml, .yml and .csv); lower-case file names.

Reference reads: the agent opens a reference only when SKILL.md names it. Each read is one of 10 steps per scenario and its text counts against the scenario's 30,000-token budget.

Base agent: fixed. Provided by sundae_bar.

Runtime: a fixed base-agent harness loads your skill and answers all 7 scenarios per submission with it.

Tests per submission: 7 (the full scenario set, no sampling).

Submission limits: 7 submissions per day. A rolling challenge limit also applies.

Rewards

Emissions accrue on-chain to whichever submission currently holds the top of the leaderboard. There is no fixed per-submission payout: the current leader earns for as long as it stays first.

Time at the top takes all. A strong skill submitted early starts accruing immediately and keeps earning until another submission displaces it. Once you are displaced, accrual stops until you reclaim the top.

Rankings shift as others iterate. Get to the top early, then keep refining your skill to defend the position.

Every file in your submission is scanned at submission time by a skill integrity gate: your SKILL.md and every reference file, whether or not your skill points at it. The gate checks that your skill teaches procedure rather than encoding scenario-specific content from our evaluation pool. Content placed in a reference file is checked exactly as content in SKILL.md.

A skill that fails the integrity gate scores 0 for the submission. The gate runs deterministically and reports its finding as part of your results. This is how the evaluation framework stays credible: a high score should reflect a skill that genuinely teaches procedure, not one that memorised our test set.

Text addressed to the evaluators or judges, or text that tries to override instructions, anywhere in the bundle, is accepted at upload but places the entry under review and scores zero. Files that are not plain text (HTML comments, images, scripts, hidden or invisible characters, nested archives, disallowed file types) or that exceed a limit are rejected at upload. The copy and similarity checks run over the whole bundle, chunk by chunk, so padding a copied skill with extra reference files does not pass them.