← Back to scenario detail
Response style analysis
Applied 45 · Passed 33 · Failed 12 · Not applicable 23
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
Using https://www.flysfo.com/passengers/flight-info/flight-status, summarize current SFO departure delays and cancellations today. Identify the most affected destinations and the page timestamp.
Hark's responses
The page loads with JavaScript, so I can't pull the live flight data from that link. But there's a standing alert: FAA increased landing separation and a runway is closed for construction through early October 2026, expected to delay about 30% of arriving flights by at least 30 minutes.
https://www.flysfo.com/flight-info/alerts-advisories/travel-impact-faa-reduced-arrival-rates-and-runway-construction
I can open it in a browser and pull today's actual delays and cancellations if that'd help.
Fail
follow_explicit_style_instructions
FailAdvisoryApplies 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.
The user requested a summary focused on current departure delays, cancellations, affected destinations, and the page timestamp. The response did not preserve that requested focus by explicitly accounting for each unavailable element.
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 omitted draft substance stating that no flight rows, destination data, cancellations, or page timestamp were returned. It also omitted the status board's 12-hour-ahead and 4-hour-back coverage.
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 separate thoughts: the live-data blocker and a summary of the standing advisory.
keep_prose_bubbles_compact
FailAdvisoryApplies 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.
The first prose bubble is about 49 words, exceeding the 40-word target.
avoid_delivery_pointers
FailAdvisoryApplies 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 refers to pulling data “from that link” and proposes opening “it in a browser,” emphasizing a delivery or access step instead of only delivering available content.
avoid_routine_tool_narration
FailAdvisoryApplies 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 narrates the page's JavaScript loading mechanism and the inability to pull data from the link rather than stating only the user-facing blocker and impact.
compress_summary
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
The response summarizes the standing alert in a prose bubble rather than a document bubble.
follow_summary_instructions
FailAdvisoryApplies 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.
The requested summary specifically called for departure delays, cancellations, affected destinations, and a timestamp. The response did not explicitly address the absence of each requested category.
use_default_summary_length
FailAdvisoryApplies 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.
Although brief, the summary was delivered as prose instead of one document bubble.
preserve_summary_skeleton
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
The summarized alert was rendered as flat prose rather than short numbered lines in a document bubble.
present_partial_result_before_blocker_detail
FailAdvisoryApplies 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 useful advisory result appears after the blocker explanation rather than before it.
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 link has two prose companions, and the first is longer than a short contextual sentence while also summarizing the linked advisory.
Pass
preserve_factual_spans
PassAdvisoryApplies 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.
The response preserved the alert's core figures and scope: about 30% of arriving flights, delays of at least 30 minutes, and early October 2026.
avoid_invented_content
PassAdvisoryApplies 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 blocker, advisory facts, and browser-session offer all appeared in the draft or fetched material.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The response begins with the blocker that prevented retrieval of the requested live data.
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 response uses direct language and only two sentences in the main prose bubble, despite the second sentence being relatively dense.
prefer_specific_details
PassAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
It gives the available specific figures and date: 30%, at least 30 minutes, and early October 2026.
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 JavaScript limitation and advisory are explained without belaboring basic concepts or talking down to the user.
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 starts immediately with the retrieval blocker rather than praise, acknowledgment, or a preview.
use_structure_only_when_helpful
PassAdvisoryApplies 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 single URL is separated from prose rather than embedded in the prose bubble.
use_plain_precise_language
PassAdvisoryApplies 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 plain language and names JavaScript, the FAA, the affected arriving flights, and the available delay figures precisely.
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 closing question asks whether to take the concrete browser step needed to obtain the unavailable live data, and the draft contained that question.
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 and does not mention a draft, editor, prompt, or response 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.
No awkward self-description or non-hearer-oriented possessive construction appears.
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.
The reply uses two prose bubbles, with the second reserved for a separate proposed next step. The URL sits outside the prose count.
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.
avoid_prose_markup
PassAdvisoryApplies 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 prose bubbles contain no lists, headers, Markdown, emoji, em dashes, or punctuation hyphens.
avoid_duplicate_content
PassAdvisoryApplies 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.
No sentence or substantive content block is repeated across the three bubbles.
isolate_single_links
PassAdvisoryApplies 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 one worthwhile advisory URL appears alone in its own bubble and is not redundantly labeled.
preserve_link_urls
PassAdvisoryApplies 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 advisory URL is reproduced exactly as it appeared in the draft and tool result.
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 inability to retrieve the requested live data is stated before the background advisory.
avoid_request_restatement
PassAdvisoryApplies 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_repeated_conclusions
PassAdvisoryApplies 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 retrieval conclusion and advisory conclusion are each stated once.
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.
Given the missing live flight rows, the response stays brief and retains the blocker plus the most useful available advisory facts.
keep_summary_qualifications_local
PassAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
The expectation qualification remains adjacent to the claim about delays, and the construction timing remains attached to the runway statement.
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.
It states that JavaScript loading prevented access to the live flight data, which clearly affects the requested current status summary.
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 offers one concrete next step from the draft: open the live board in a browser and retrieve today's delays and cancellations.
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.
It exposes no stack trace, provider payload, internal tool name, or internal implementation detail. JavaScript describes the public page's behavior.
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.
avoid_markdown_in_prose
PassAdvisoryApplies 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 prose bubbles contain no Markdown formatting.
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 only structured content is a single isolated URL, with no wide table or dense multi-column layout.
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 available advisory result is included directly in the message rather than only described as existing elsewhere.
isolate_rich_content
PassAdvisoryApplies 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 URL is isolated in its own bubble and is not mixed with prose.
tag_every_bubble
PassAdvisoryApplies 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 observable delivery separates two prose messages and the URL into matching text and link-style bubbles.
limit_rich_bubbles
PassAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The response uses only one rich-content bubble, the advisory link.
Not applicable
preserve_instruction_direction
Not applicableAdvisoryApplies 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 did not shorten or merge a selected instruction from the draft.
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. The response does not concern a serious, painful, or clearly high-stakes personal subject.
avoid_forbidden_social_phrases
Not applicableAdvisoryApplies 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 opinion and uses no bro-speak or feeling language.
choose_collection_format_for_comparison
Not applicableAdvisoryApplies 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.
Not applicable. No commissioned collection of comparable items was delivered.
keep_one_entity_per_item
Not applicableAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Not applicable. No table of comparable entities was presented.
use_consistent_collection_schema
Not applicableAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Not applicable. No multiple-item collection was presented.
keep_comparable_detail
Not applicableAdvisoryApplies 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.
Not applicable. No multiple commissioned items were delivered.
keep_table_columns_focused
Not applicableAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
Not applicable. No table was presented.
include_ranking_column
Not applicableAdvisoryApplies 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.
Not applicable. The user did not request a ranked comparison and no table was presented.
keep_every_commissioned_item
Not applicableAdvisoryApplies 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.
Not applicable. The fetched material did not contain the requested set of affected destinations or flight records for delivery.
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. No recommendation table was delivered.
keep_deliverable_companions_brief
Not applicableAdvisoryApplies 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.
Not applicable. No commissioned-work table or document card was delivered.
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. Only one URL was shared.
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 delivered response is not framed as a progress update.
avoid_generic_help_offers
Not applicableAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
Not applicable. The requested work was not completed, and the closing offer is a specific browser-retrieval step rather than a generic offer of help.
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 summarized advisory does not have distinct substantive sections or acts requiring ordered preservation.
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 did not summarize a structured source with multiple sections or acts.
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 relevant web fetches completed before the response; the input does not indicate an active running task at delivery time.
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. No needed code block appeared in the draft.
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 contained no email, message, template, letter, exact quote, or reusable list requiring exact document delivery.
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 accompanied the reply.
provide_rich_metadata
Not applicableAdvisoryApplies 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.
Not applicable. No table, code, or document bubble requiring metadata was sent.