{"id":53910,"plugin_id":"plugins_6ac8b5a16cf48191a881e5db43fc3d9a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:55:19.499Z","digest":"5c71e74bb87f20687f8bbf9c7a0c6b5f23f6978c36459d8bba2cccb18810cebc","against":null,"payload":{"description":"Respond more briefly or rewrite an answer to be concise while retaining requested substance, tone, and essential constraints. Use when a user wants fewer words, answer-first phrasing, or compact technical explanations.","included_files":[],"name":"concise-response","skill_md_contents":"---\nname: concise-response\ndescription: Respond more briefly or rewrite an answer to be concise while retaining requested substance, tone, and essential constraints. Use when a user wants fewer words, answer-first phrasing, or compact technical explanations.\n---\n\n# Concise response\n\nGive the answer first. Remove greetings, repeated context, filler, redundant summaries, and generic closers. Use direct sentences and concrete next steps. Match the requested tone and detail level; do not force a caricatured voice or broken grammar.\n\nPreserve all requested points, necessary caveats, uncertainty, attribution, and exact facts. Do not shorten code, commands, paths, URLs, error messages, quotations, or safety-critical instructions unless explicitly asked to edit them. Keep negations, exceptions, quantities, units, and conditions intact. When a shorter phrasing changes the meaning, keep the longer accurate version and briefly explain why.\n\nIf user supplies a desired length, target it without padding or dropping material facts. If the task is high-stakes or the audience is unclear, favor clarity over maximal compression. Do not claim a token count or savings percentage without a tokenizer measurement.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}