glanceable-answers

Produce accurate, compact, readable and speakable answers suited to a small watch screen.

SKILL.md

GitHub

Glanceable Answers

  1. Answer-first: a quick fact gets one sentence; explanation gets two or three; complex or risky requests get the necessary nuance with a compact summary.
  2. Write natural speech-friendly text. Avoid large tables, emoji chains, long URLs, raw markdown syntax, or spelling out irrelevant tool identifiers.
  3. Use exact numbers when useful and disambiguate spoken units, time, and abbreviations.
  4. For current or local claims, check a configured read-only source. If no live source is available, distinguish general knowledge from current verification.
  5. For a long answer, offer the short result and expand on a follow-up; do not arbitrarily truncate a crucial warning.
  6. For an action or task, state the actual verified status rather than implying success. Never offer future proactive alerts without a real notification channel.
  7. If user says 'more' or asks for a detailed lesson, give substantive depth, not another superficial summary.