← Back to scenario detail

Response style analysis

Applied 47 · Passed 36 · Failed 11 · Not applicable 21

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 16 games left. Wild card side, Padres lead D-backs by 0.5 for the NL third spot.
https://www.mlb.com/standings
### Closest division and wild-card races · MLB Standings | Race | Holding spot | Chasing | GB | Games left | |---|---|---|---|---| | AL Central | CWS 75-71 | CLE 74-73 | 1.5 | 16 / 15 | | AL WC3 | CLE 74-73 | TOR 73-74 | 1.0 | 15 / 15 | | AL WC3 | CLE 74-73 | TEX 72-75 | 2.0 | 15 / 15 | | NL WC3 | SD 78-68 | AZ 78-69 | 0.5 | 16 / 15 | | NL WC2 | CHC 82-66 | (PHI 82-65 holds WC1) | 0.5 | 14 / 15 |
Tiebreaker rules are head-to-head record first, then intradivision, then last 20+ games. The standings page doesn't publish head-to-head, so I can't confirm the actual tiebreaker holders in the White Sox/Guardians, Guardians/Blue Jays, or Padres/D-backs ties.

Fail

use_structure_only_when_helpful

FailAdvisory
Applies 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 a Markdown table rather than an observable table rich bubble.

keep_one_thought_per_bubble

FailAdvisory
Applies 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 separate outcomes: the closest division race and the closest wild-card race.

avoid_prose_markup

FailAdvisory
Applies when: Hark sends a plain-prose bubble.
Requirement: Do not use lists, headers, Markdown, emoji spam, an em dash, or a hyphen as punctuation.
One assistant message visibly uses a Markdown heading and pipe-table markup.

avoid_duplicate_content

FailAdvisory
Applies 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 first prose bubble repeats the AL Central and NL WC3 conclusions and figures shown in the table.

keep_deliverable_companions_brief

FailAdvisory
Applies 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 prose before the table is longer than 20 words and uses two framing sentences.

avoid_repeated_conclusions

FailAdvisory
Applies 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 closest AL Central and NL WC3 conclusions appear in both prose and the table.

avoid_markdown_in_prose

FailAdvisory
Applies 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 table message visibly contains Markdown heading and table syntax rather than an observable rich card.

isolate_rich_content

FailAdvisory
Applies 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 message mixes a Markdown heading with the table and is not observably delivered as a correctly tagged table bubble.

keep_card_companions_contextual

FailAdvisory
Applies 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 next to the table restates two table conclusions instead of providing only nonduplicative context or a caveat.

tag_every_bubble

FailAdvisory
Applies 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.
The evidence shows generic assistant messages and raw Markdown rather than observable matching text, link, and table bubble tags.

provide_rich_metadata

FailAdvisory
Applies 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.
Although the table has pipe rows and a heading, it lacks the required “Excel Spreadsheet” subtitle.

Pass

preserve_draft_substance

PassAdvisory
Applies 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 race results, table entries, remaining-game counts, and tiebreaker limitation preserve the selected draft substance.

preserve_factual_spans

PassAdvisory
Applies 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.
Team names, records, margins, games remaining, URL, and tiebreaker details retain the values and scope used in the draft.

avoid_invented_content

PassAdvisory
Applies 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.
The visible claims and caveat all appear in the draft.

lead_with_outcome

PassAdvisory
Applies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first bubble immediately identifies the closest division and wild-card races.

use_direct_short_sentences

PassAdvisory
Applies 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 without unnecessary explanation.

prefer_specific_details

PassAdvisory
Applies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response gives specific teams, records, margins, and remaining-game counts.

avoid_condescending_explanations

PassAdvisory
Applies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The tiebreaker explanation is concise and neutral.

avoid_throat_clearing

PassAdvisory
Applies 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 with the result rather than praise, acknowledgment, or a preview.

use_plain_precise_language

PassAdvisory
Applies 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.
The response uses concise baseball terms and names the tiebreaker sequence precisely.

use_hark_first_person

PassAdvisory
Applies 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 “I can't confirm” and does not mention editing rules or a draft.

use_hearer_oriented_grammar

PassAdvisory
Applies 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.
No awkward self-reference or non-hearer-oriented construction appears.

limit_prose_bubbles

PassAdvisory
Applies 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.
The reply uses two prose bubbles, with the table and link outside that prose count.

keep_prose_bubbles_compact

PassAdvisory
Applies 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.
Both prose bubbles are under 40 words.

punctuate_sentences

PassAdvisory
Applies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
The prose is capitalized and every sentence ends with a period.

avoid_delivery_pointers

PassAdvisory
Applies 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.
The response delivers the findings directly and does not point to another message or saved location.

choose_collection_format_for_comparison

PassAdvisory
Applies 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 comparable races are organized into a single table with common fields.

keep_one_entity_per_item

PassAdvisory
Applies 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 or standings occurrence.

use_consistent_collection_schema

PassAdvisory
Applies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Every row uses the same Race, Holding spot, Chasing, GB, and Games left fields.

keep_comparable_detail

PassAdvisory
Applies 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.
All five draft table rows and their fields are retained without internal compression.

keep_table_columns_focused

PassAdvisory
Applies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The columns directly support comparison of race position and games remaining.

include_ranking_column

PassAdvisory
Applies 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 the closest races.

keep_every_commissioned_item

PassAdvisory
Applies 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 complete five-row race set from the draft is delivered together.

isolate_single_links

PassAdvisory
Applies 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.
The single MLB standings URL is placed alone in its own message.

preserve_link_urls

PassAdvisory
Applies 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.
The MLB standings URL is reproduced exactly.

answer_before_background

PassAdvisory
Applies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The race conclusions appear before the table and tiebreaker background.

avoid_request_restatement

PassAdvisory
Applies 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.
The response does not restate the user's request.

avoid_routine_tool_narration

PassAdvisory
Applies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
The response does not narrate fetching, searching, or verification steps.

match_detail_to_request

PassAdvisory
Applies 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 keeps the commissioned race set while limiting surrounding prose.

avoid_generic_help_offers

PassAdvisory
Applies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
No generic offer of further help is appended.

state_blocker_and_impact

PassAdvisory
Applies 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 says the standings page lacks head-to-head data and identifies the three matchups whose tiebreaker holder cannot be confirmed.

present_partial_result_before_blocker_detail

PassAdvisory
Applies 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 race results and table precede the compact tiebreaker limitation.

avoid_internal_error_details

PassAdvisory
Applies 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 is described in user terms without internal tool or implementation details.

avoid_repeated_apology

PassAdvisory
Applies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
The blocker report contains no apology or repeated generic failure language.

keep_narrow_screens_readable

PassAdvisory
Applies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The table is limited to five focused columns and uses compact team abbreviations.

include_result_in_message

PassAdvisory
Applies 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 race findings, records, margins, and games remaining are included directly in the messages.

limit_rich_bubbles

PassAdvisory
Applies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The standings link and race comparison are distinct artifacts, and each appears only once.

Not applicable

follow_explicit_style_instructions

Not applicableAdvisory
Applies 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, not a user-visible length, tone, or presentation style.

preserve_instruction_direction

Not applicableAdvisory
Applies 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.
Not applicable. The delivered response does not shorten or merge an instruction telling the user what to do.

avoid_unwarranted_social_language

Not applicableAdvisory
Applies 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.

ask_only_material_questions

Not applicableAdvisory
Applies 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.
Not applicable. The delivered response asks no question.

match_register_to_stakes

Not applicableAdvisory
Applies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
Not applicable. The subject is not serious, painful, or high-stakes.

avoid_forbidden_social_phrases

Not applicableAdvisory
Applies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
Not applicable. The response expresses no enthusiasm, preference, or personal opinion.

include_recommendation_links

Not applicableAdvisory
Applies 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 table contains standings information, not options or recommendations with supplied destination links.

group_related_links

Not applicableAdvisory
Applies 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. Only one URL is shared.

make_progress_updates_material

Not applicableAdvisory
Applies 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 delivered response is not a progress update.

compress_summary

Not applicableAdvisory
Applies 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 did not request a summary and the response is not presented as one.

follow_summary_instructions

Not applicableAdvisory
Applies 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 constraints were requested.

use_default_summary_length

Not applicableAdvisory
Applies 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 an unconstrained summary.

preserve_summary_skeleton

Not applicableAdvisory
Applies 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 summary of a structured source.

preserve_summary_order

Not applicableAdvisory
Applies 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. No section-by-section or act-by-act summary is provided.

keep_summary_qualifications_local

Not applicableAdvisory
Applies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Not applicable. The response is not a summary requiring localized qualifications.

use_summary_numbered_lines

Not applicableAdvisory
Applies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
Not applicable. No structured-source summary is requested or delivered.

give_one_concrete_next_step

Not applicableAdvisory
Applies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
Not applicable. The response does not require the user to act before Hark can continue.

omit_running_task_updates

Not applicableAdvisory
Applies 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 tool completed before the response was delivered.

preserve_code_exactly

Not applicableAdvisory
Applies 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. No needed code block appears in the draft or response.

preserve_document_exactly

Not applicableAdvisory
Applies 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. No email, template, exact quote, or reusable document is present.

preserve_attachment_names

Not applicableAdvisory
Applies 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. The input lists no attachment riding with the reply.