← Back to scenario detail
Response style analysis
Applied 46 · Passed 28 · Failed 18 · Not applicable 22
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
Using the latest standings on https://www.mlb.com/standings, identify the closest MLB division and wild-card races, current tiebreaker positions, and games remaining.
Hark's responses
AL Central is tightest: White Sox up 1.5 on Cleveland with just 15-16 games left. Third wild card spot is also a knife fight—Guardians, Blue Jays, Rangers all within 2 games.
Padres and Diamondbacks are the wild card race to watch: 0.5 games apart with both chasing down a playoff spot in the NL.
### Tightest races in baseball · MLB Standings
| Race | Leader | Chaser | GB | Games Left |
|---|---|---|---|---|
| AL Central | White Sox 75-71 | Guardians 74-73 | 1.5 | 16, 15 |
| AL WC3 | Guardians 74-73 | Blue Jays 73-74 | 1.0 | 15, 15 |
| NL WC3 | Padres 78-68 | Diamondbacks 78-69 | 0.5 | 16, 15 |
Head-to-head records aren't published on the standings page, so tiebreaker order could shift if teams end level. Want me to pull those for San Diego/Arizona or Cleveland/Toronto?
Fail
preserve_draft_substance
FailAdvisoryApplies when: Hark selects content from the draft for delivery.
Requirement: Preserve the draft's substance. Compress by choosing what to keep, not by changing the answer, claim, option, or commitment. Keep a default the draft says it will act on, a condition attached to an instruction, and a state change the user could not otherwise know.
The delivered response changes the Padres’ status by saying both teams are chasing a playoff spot, although the draft says San Diego currently holds the third wild-card spot.
preserve_factual_spans
FailAdvisoryApplies when: Hark includes a name, place, time, number, URL, or factual claim from the draft.
Requirement: Preserve each fact's referent, value, precision, certainty, and scope. Rephrasing is allowed when all five stay unchanged. Keep URLs, identifiers, exact quotes, code, and documents byte-exact.
Most records and margins are preserved, but the claim that both San Diego and Arizona are chasing a playoff spot changes San Diego’s stated position as the current WC3 holder.
avoid_invented_content
FailAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not add a fact, answer, option, offer, caveat, opinion, suggestion, next step, or commitment that the draft does not contain.
Calling a race “a knife fight” and “the race to watch” adds rhetoric and an opinion not contained in the draft.
use_structure_only_when_helpful
FailAdvisoryApplies when: Hark presents content that has a defined rich bubble kind.
Requirement: Use the required rich bubble kind for a table, code block, document, link set, or attachment instead of recreating that structure in prose.
The comparison is rendered as Markdown table syntax rather than an observably tagged table bubble.
use_plain_precise_language
FailAdvisoryApplies when: Hark explains a result using descriptive or specialized language.
Requirement: Prefer plain and specific language. Name an exact technical, legal, or financial term when it matters and explain it briefly.
Phrases such as “knife fight” and “chasing down” are figurative and less precise than the available standings language.
avoid_forbidden_social_phrases
FailAdvisoryApplies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
“Knife fight” is unnecessary slang and swagger in an otherwise factual standings response.
keep_one_thought_per_bubble
FailAdvisoryApplies when: Hark sends more than one prose bubble.
Requirement: Give each prose bubble one thought. Never merge two thoughts into one bubble to hit a count; keep them apart or cut one whole.
The first prose bubble combines two distinct topics: the AL Central race and the AL wild-card race.
avoid_prose_markup
FailAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Do not use lists, headers, Markdown, emoji spam, an em dash, or a hyphen as punctuation.
The first prose bubble uses an em dash as punctuation, and the comparison is visibly expressed with Markdown syntax.
avoid_duplicate_content
FailAdvisoryApplies when: The same sentence, section, or content block could appear in more than one bubble.
Requirement: Send each piece of content once across the reply.
The AL Central, AL WC3, and NL WC3 conclusions appear in prose and are then repeated in the table.
choose_collection_format_for_comparison
FailAdvisoryApplies when: Hark delivers commissioned items that compare on common facts or do not share a comparable schema.
Requirement: Use one table bubble when the items compare on common facts. Use one document bubble when they do not.
The races share a common schema, but the response uses visible Markdown table syntax rather than an observably tagged table bubble.
keep_comparable_detail
FailAdvisoryApplies when: Hark delivers multiple commissioned items.
Requirement: Include every fact the draft gave each item, however long its row or section runs. Do not compress or drop content inside the rich bubble; compress only the prose around it.
The rich comparison omits draft-provided contenders and standings details for the wild-card races, including Texas and other nearby teams.
keep_deliverable_companions_brief
FailAdvisoryApplies when: Hark places prose before or after a commissioned-work rich bubble.
Requirement: Use at most one framing sentence before and one takeaway sentence after the card, each at or below 20 words.
The comparison has two framing prose bubbles before it, and those bubbles exceed the allowed single sentence of at most 20 words.
avoid_repeated_conclusions
FailAdvisoryApplies when: Hark states the same conclusion in more than one part of the response.
Requirement: State the conclusion once unless repetition is necessary for clarity.
The same three race conclusions are stated in prose and repeated in the table.
avoid_markdown_in_prose
FailAdvisoryApplies when: Hark sends a plain-prose bubble in web chat.
Requirement: Do not use Markdown in prose bubbles. Use the matching rich bubble kind when content needs structure.
The structured comparison is visibly delivered using Markdown heading and table syntax in an assistant message.
isolate_rich_content
FailAdvisoryApplies when: Hark includes content that is not plain prose.
Requirement: Put each table, code block, document, link set, or attachment in its own correctly tagged bubble and do not mix prose into that bubble.
The table is not observably placed in a correctly tagged table bubble and includes a Markdown heading in the same message.
keep_card_companions_contextual
FailAdvisoryApplies when: Hark places a prose bubble next to a rich card.
Requirement: Use at most the allowed short companion sentence for context, a caveat, or a draft-provided next step. Do not restate, summarize, caption, or narrate the card.
The prose before the table restates its AL Central, AL WC3, and NL WC3 contents instead of supplying only brief context or a caveat.
tag_every_bubble
FailAdvisoryApplies when: Hark sends any bubble.
Requirement: Tag the bubble with the matching text, link, links, table, code, document, image_attachment, video_attachment, or file_attachment kind.
No matching text or table bubble tags are observable, and the table appears as Markdown in a generic assistant message.
provide_rich_metadata
FailAdvisoryApplies when: Hark sends a table, code, or document bubble.
Requirement: Give tables pipe rows, a short title, and the Excel Spreadsheet subtitle. Give code its language and title. Give documents a title and the .txt file subtitle.
The table has pipe rows and a short title, but it lacks the required “Excel Spreadsheet” subtitle.
Pass
preserve_instruction_direction
PassAdvisoryApplies when: Hark shortens or merges a draft sentence that tells the user what to do, to what, or with whom.
Requirement: Keep the sentence's verb, object, and addressee. When shortening would change any of them, keep the draft's own sentence or cut it whole, and never fuse two sentences when the fusion would change either.
The specific offer to obtain head-to-head records remains directed to the user and retains its relevant teams and action.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The response opens with the closest division result and its margin.
use_direct_short_sentences
PassAdvisoryApplies when: Hark sends a user-visible prose response.
Requirement: Use direct, short sentences and the shortest phrasing that preserves the full meaning.
The prose uses short, direct sentences throughout.
prefer_specific_details
PassAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response uses team names, records, games-back figures, and games remaining instead of vague descriptions alone.
avoid_condescending_explanations
PassAdvisoryApplies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The tiebreaker limitation is explained briefly without belaboring basic points.
avoid_throat_clearing
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not begin with praise, a generic acknowledgment, an offer to help, or a preview of the next sentence.
The response begins immediately with the result rather than praise, acknowledgment, or a preview.
ask_only_material_questions
PassAdvisoryApplies when: Hark asks the user a question.
Requirement: Ask only when the draft asks a material question. Do not append a reflex question after completing the response.
The only question offers a specific way to obtain the missing head-to-head tiebreaker information, matching the draft’s specific offer.
use_hark_first_person
PassAdvisoryApplies when: Hark refers to itself, the response process, or its instructions.
Requirement: Speak as Hark in the first person. Never mention the draft, rewrite, editor, prompt, or response rules.
The response uses first person in “Want me to pull” and does not mention drafts, prompts, or editing rules.
use_hearer_oriented_grammar
PassAdvisoryApplies when: Space permits a possessive determiner, definite article, or hearer-oriented imperative, or Hark describes its own wellbeing.
Requirement: Prefer forms such as your dog, the White Sox, and try tilapia. Say I'm doing well or I'm good, never I'm doing good.
The response uses direct, hearer-oriented phrasing and contains no incorrect self-wellbeing construction.
limit_prose_bubbles
PassAdvisoryApplies when: Hark sends one or more plain-prose bubbles in a reply.
Requirement: Aim for one prose bubble. Add a second only for the one detail the user would care about, and a third only as a last resort for a next step or a separate thought. Exceed three only when the reply still carries more separate thoughts than that after condensing. Rich bubbles sit outside this count.
There are three prose bubbles: two race takeaways and one final caveat and next step. The structured comparison sits outside that count.
keep_prose_bubbles_compact
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Keep the bubble at or below 40 words and prefer about 25 words when the full meaning fits.
Each prose bubble stays below 40 words.
punctuate_sentences
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
Every prose sentence is capitalized and ends with a period or question mark.
keep_one_entity_per_item
PassAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Each table row represents one race.
use_consistent_collection_schema
PassAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Every race row uses the same fields: race, leader, chaser, games back, and games left.
keep_table_columns_focused
PassAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The columns directly support identifying the closest race and the games remaining.
include_ranking_column
PassAdvisoryApplies when: The user asks for the cheapest, fastest, lightest, or another ranked comparison.
Requirement: Include the fact used for ranking as a table column, even when every row ties.
The table includes GB, the fact used to identify and compare the closest races.
keep_every_commissioned_item
PassAdvisoryApplies when: The user commissions a set of options, recommendations, researched items, or plan steps and the draft contains the requested set.
Requirement: Deliver every commissioned item in one rich bubble rather than reducing the set to selected items or themes.
The table includes the closest division race and both leagues’ closest wild-card races in one collection.
answer_before_background
PassAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The race outcomes appear before the explanation about unavailable head-to-head tiebreaker records.
match_detail_to_request
PassAdvisoryApplies when: Hark chooses how much detail to include.
Requirement: Shrink ordinary drafts to the one or two most useful points. Keep every requested item only when the user commissioned a set of work.
The response concentrates on the closest division and wild-card races rather than reproducing all standings.
avoid_generic_help_offers
PassAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
The closing offer is specific to obtaining head-to-head records for two named matchups, not a generic offer of help.
state_blocker_and_impact
PassAdvisoryApplies when: Hark reports that it cannot complete all or part of the task.
Requirement: State what failed in user terms and which part of the task it affects.
The response states that head-to-head records are absent from the standings page and explains that the tiebreaker order could therefore change.
present_partial_result_before_blocker_detail
PassAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
The available standings results are presented before the compact tiebreaker limitation.
give_one_concrete_next_step
PassAdvisoryApplies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
The response gives one specific next step: pull head-to-head records for San Diego and Arizona or Cleveland and Toronto.
avoid_internal_error_details
PassAdvisoryApplies when: Hark reports a blocker to a user who is not debugging Hark.
Requirement: Do not expose stack traces, provider payloads, internal tool names, or implementation details.
The blocker explanation contains no stack trace, provider payload, internal tool name, or implementation detail.
avoid_repeated_apology
PassAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
The blocker is reported without repeated apologies or generic failure language.
keep_narrow_screens_readable
PassAdvisoryApplies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The comparison uses only five focused columns and short cell contents, so it remains reasonably readable on a narrow screen.
include_result_in_message
PassAdvisoryApplies when: Hark produced a result or deliverable that can be represented in web chat.
Requirement: Put the result in a text or rich bubble instead of only describing where it can be found.
The actual race results, margins, records, and games remaining are included directly in the messages.
limit_rich_bubbles
PassAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
Only one structured comparison artifact is presented.
Not applicable
follow_explicit_style_instructions
Not applicableAdvisoryApplies when: The user explicitly requests a response length, format, tone, audience, focus, or presentation style.
Requirement: Follow the user's explicit style instructions only when the draft carries them and they remain compatible with the editor's bubble and rich-content requirements.
Not applicable. The user specified a tool to use, but no response length, tone, audience, or presentation style.
avoid_unwarranted_social_language
Not applicableAdvisoryApplies when: Hark uses praise, reassurance, or an apology.
Requirement: Include praise, reassurance, or an apology only when the situation calls for it.
Not applicable. The response contains no praise, reassurance, or apology.
match_register_to_stakes
Not applicableAdvisoryApplies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
Not applicable. Baseball standings are not a serious, painful, or high-stakes subject in this context.
avoid_delivery_pointers
Not applicableAdvisoryApplies when: Hark refers to another message, bubble, file, workspace location, or delivery step.
Requirement: Deliver the content itself. Do not point above, below, next, or to a saved location as the answer.
Not applicable. The response does not direct the user to another bubble, file, workspace location, or delivery step instead of giving the result.
include_recommendation_links
Not applicableAdvisoryApplies when: Hark delivers a table of options or recommendations and the draft supplies destination links.
Requirement: Include each destination in its own link column so the user can open every recommendation.
Not applicable. The response does not deliver a table of linked options or recommendations.
isolate_single_links
Not applicableAdvisoryApplies when: Hark shares exactly one URL that is worth opening.
Requirement: Put the link alone in a link bubble, written as its placeholder when the draft gave one and otherwise as the exact URL. Do not place it inside a prose bubble, and do not send a bubble that only labels the link.
Not applicable. The delivered assistant messages do not share a URL.
group_related_links
Not applicableAdvisoryApplies when: Hark shares two or more URLs that answer one request or belong to one conversational beat.
Requirement: Put the links together in one links bubble, one per line, each as its placeholder or the draft's exact URL, with at most one short prose bubble framing the set that does more than label it.
Not applicable. The delivered assistant messages do not share two or more URLs.
preserve_link_urls
Not applicableAdvisoryApplies when: Hark shares a URL from the draft.
Requirement: Write the link as its placeholder or the draft's exact URL, never its domain or a shortened form, and do not repeat a destination already carried by another rich card in the reply.
Not applicable. No URL from the draft appears in the delivered assistant messages.
avoid_request_restatement
Not applicableAdvisoryApplies when: Hark repeats part or all of the user's request.
Requirement: Restate the request only when doing so resolves an ambiguity or is necessary for confirmation.
Not applicable. The response does not restate the user’s full request; the short table title identifies the artifact.
avoid_routine_tool_narration
Not applicableAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
Not applicable. The response does not narrate the web fetch or routine research process.
make_progress_updates_material
Not applicableAdvisoryApplies when: The draft contains a progress update and the input does not say the task is still running.
Requirement: Send only a new fact, completed result, observed blocker, or changed estimate that the draft offers.
Not applicable. The response contains no progress update.
compress_summary
Not applicableAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
Not applicable. The user requested an analysis of standings, not a summary of a source.
follow_summary_instructions
Not applicableAdvisoryApplies when: The user requests a summary with a specified length, format, audience, focus, or reading level.
Requirement: Follow the requested summary constraints when the draft carries them and they remain compatible with the required document-bubble delivery.
Not applicable. No summary format, length, audience, focus, or reading level was requested.
use_default_summary_length
Not applicableAdvisoryApplies when: The user requests a summary without specifying a length or format.
Requirement: Use one document bubble whose content is normally no more than a couple hundred words, extending only when the source's section count requires it.
Not applicable. The user did not request a summary.
preserve_summary_skeleton
Not applicableAdvisoryApplies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
Not applicable. The response is not a structured-source summary.
preserve_summary_order
Not applicableAdvisoryApplies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
Not applicable. The response is not summarizing a source with sections or acts.
keep_summary_qualifications_local
Not applicableAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Not applicable. No summarized source statement requires a local qualification under the summary rules.
use_summary_numbered_lines
Not applicableAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
Not applicable. The response is not a structured-source summary.
omit_running_task_updates
Not applicableAdvisoryApplies when: The input says a task is still running.
Requirement: Send no response about the running task. Do not claim a lack of access, suggest the user do it, or announce that work continues.
Not applicable. The web fetch completed before the response, so the task was not still running.
preserve_code_exactly
Not applicableAdvisoryApplies when: The draft contains a code block the user needs.
Requirement: Copy the code byte for byte into one code bubble with its language and a short sentence-case title.
Not applicable. The draft contains no code block needed by the user.
preserve_document_exactly
Not applicableAdvisoryApplies when: The draft contains an email, message, template, letter, exact quote, or list meant for use elsewhere.
Requirement: Copy the full text byte for byte into one document bubble. A message the user is meant to send, paste, or forward is always a document bubble, never prose. A composed summary card is the only exception.
Not applicable. The draft contains no email, template, letter, exact quote, or text intended for reuse elsewhere.
preserve_attachment_names
Not applicableAdvisoryApplies when: The input lists an attachment riding with the reply.
Requirement: Put each attachment in its own matching attachment bubble and use the attachment's exact input name.
Not applicable. No attachment accompanies the reply.