← Back to scenario detail
Response style analysis
Applied 48 · Passed 28 · Failed 20 · Not applicable 20
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
What Chrome releases or platform updates were published on https://developer.chrome.com/blog/ in the past 14 days? Summarize the most important developer-facing changes.
Hark's responses
Nothing dropped in the past 14 days. The blog hasn't updated since June 23.
Main theme across recent posts: Chrome pushing hard on agent-readiness. WebMCP, DevTools for agents, Lighthouse agentic audits.
### Recent Chrome posts · Chrome for Developers blog
| Date | Post | What it changes |
|---|---|---|
| Jun 22 | [Agent-ready toolkit](https://developer.chrome.com/blog/agent-ready-toolkit) | New Lighthouse "Agentic browsing" category plus DevTools for agents, to audit and fix how well a site works for AI agents |
| Jun 18 | [Third-party tools for DevTools for agents](https://developer.chrome.com/blog/devtools-for-agents-3p-tools) | Frameworks and apps can expose their own runtime context to AI coding assistants |
| Jun 17 | [What's new in WebGPU (Chrome 149-150)](https://developer.chrome.com/blog/new-in-webgpu-149-150) | Immediates support, stricter validation for transient attachments |
| Jun 9 | [WebMCP origin trial](https://developer.chrome.com/blog/ai-webmcp-origin-trial) | Sites can declare structured tools so agents complete tasks accurately |
| Jun 3 | [Chrome 150 beta](https://developer.chrome.com/blog/chrome-150-beta) and [seamless PWA origin migration](https://developer.chrome.com/blog/seamless-pwa-origin-migration) | Chrome 150 lets a PWA move to a new same-site origin without losing installs |
| Jun 2 | [New in Chrome 149](https://developer.chrome.com/blog/new-in-chrome-149) and [DevTools 149](https://developer.chrome.com/blog/new-in-devtools-149) | CSS gap decorations, WebSocket disconnect for bfcache eligibility, Intl.Locale variants; DevTools for agents goes stable, WebMCP debugging |
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.
It preserves the main conclusion and item summaries, but drops the exact Aug 28 to Sep 11 window, the feed link, and the qualification that the newest posts were about three months old.
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.
Dates are reduced to month and day, omitting 2026, and the exact 14-day window is omitted. This reduces factual precision.
prefer_specific_details
FailAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
Specific dates were available, but the response says only “the past 14 days” and “June 23,” and the table omits the year.
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 recreated as a Markdown table rather than delivered as a correctly 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.
Most terminology is precise, but “Nothing dropped” and “pushing hard” are colloquial rather than plain, neutral wording.
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.
The thematic opinion uses swagger-like phrasing, “Chrome pushing hard,” alongside the colloquial “Nothing dropped.”
keep_one_entity_per_item
FailAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
The Jun 3 row combines Chrome 150 beta with PWA migration, and the Jun 2 row combines Chrome 149 with DevTools 149.
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.
Although each companion is short, two prose sentences precede the table rather than at most one framing sentence.
group_related_links
FailAdvisoryApplies 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.
The related URLs are embedded in a Markdown table rather than grouped in one links bubble.
match_detail_to_request
FailAdvisoryApplies 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.
After answering that there were no posts in the requested period, it adds a six-row table of older posts outside that period.
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 provides a summary but not in one document bubble; it uses prose plus a Markdown table.
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.
It follows the requested developer-facing focus, but does not use the required document-bubble delivery for a summary.
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.
The summary is reasonably short, but it is not delivered in one document bubble as required.
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 source's item order is retained, but the summary is not formatted as short numbered lines and combines distinct items.
use_summary_numbered_lines
FailAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
The structured-source summary uses a Markdown table rather than numbered lines inside a document bubble.
keep_narrow_screens_readable
FailAdvisoryApplies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The table has only three columns, but several cells contain long text and two linked posts, making it unnecessarily dense on narrow screens.
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 presented as Markdown in an assistant message rather than as an isolated, correctly tagged table bubble.
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.
Two prose bubbles precede the table, exceeding the allowed single short companion sentence.
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.
The observed assistant messages do not expose matching text and table bubble tags, and the table is represented as Markdown.
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 a visible heading and pipe rows, but lacks a proper table-bubble title field and the required Excel Spreadsheet subtitle.
Pass
follow_explicit_style_instructions
PassAdvisoryApplies 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 response directly summarizes the developer-facing changes and keeps the requested focus concise.
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 conclusion, theme, features, and links all derive from the draft and fetched feed.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first sentence gives the result that nothing was published in the period.
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 brief, direct sentences.
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 explanations are concise and do not belabor 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.
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 unsuitable 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.
There are two compact prose bubbles before the rich content, with the second carrying a distinct thematic takeaway.
keep_one_thought_per_bubble
PassAdvisoryApplies 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 states the publication result; the second states the theme.
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.
Both prose bubbles are well 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.
The prose is capitalized and each sentence ends with a period.
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 two plain-prose bubbles do not contain headers, lists, Markdown, emoji, or dash punctuation.
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.
The outcome, thematic takeaway, and detailed item table are not duplicated verbatim across bubbles.
choose_collection_format_for_comparison
PassAdvisoryApplies 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 posts are organized in one table with common date, post, and change fields.
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 row uses the same Date, Post, and What it changes columns.
keep_comparable_detail
PassAdvisoryApplies 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 table retains the item-specific facts supplied in the draft, including the combined-row details.
keep_table_columns_focused
PassAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The columns focus on publication date, post identity, and developer-facing effect.
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 response retains all eight recent posts included in the draft, though four are paired into two rows.
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 post destinations use the exact canonical URLs present in the draft.
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 no-publications answer appears before the older-post context and table.
avoid_routine_tool_narration
PassAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
It does not narrate the fetch, verification process, or other routine tool use.
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 no-publications conclusion is stated once; the next bubble gives a distinct theme.
avoid_generic_help_offers
PassAdvisoryApplies 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.
preserve_summary_order
PassAdvisoryApplies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
The posts appear in the same reverse-chronological order as the feed and draft.
keep_summary_qualifications_local
PassAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Feature qualifications, such as same-site origin and transient-attachment validation, remain beside the claims they modify.
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 plain-prose bubbles contain no Markdown. The Markdown appears in the separate table message.
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 publication result and detailed summaries are included directly in the response.
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-content message is used.
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 response does not shorten or merge an instruction telling the user what to do.
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.
ask_only_material_questions
Not applicableAdvisoryApplies 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 response asks no questions.
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 subject is not serious, painful, or high stakes.
use_hark_first_person
Not applicableAdvisoryApplies 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.
Not applicable. The response does not refer to Hark, its process, or its instructions.
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 point the user to another bubble or saved location as a substitute for the answer.
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.
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 table contains factual posts, not 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 response shares multiple URLs, not exactly one.
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 unnecessarily restate the user's request.
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 does not provide a progress update.
state_blocker_and_impact
Not applicableAdvisoryApplies 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.
Not applicable. The response reports no blocker or inability to complete the task.
present_partial_result_before_blocker_detail
Not applicableAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
Not applicable. There is no blocker paired with a partial result.
give_one_concrete_next_step
Not applicableAdvisoryApplies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
Not applicable. No user action is required before Hark can continue.
avoid_internal_error_details
Not applicableAdvisoryApplies 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.
Not applicable. The response reports no error or blocker.
avoid_repeated_apology
Not applicableAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
Not applicable. The response contains no apology or failure language.
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 tool had completed before the response; the input did not indicate an ongoing task.
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 appears 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 does not contain an email, template, exact quote, or other reusable document requiring byte-exact 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 rides with the reply.